Answer engine, Hosted, public HTTPS
Perplexity WordPress MCP. A custom remote connector.
A Perplexity WordPress MCP connector pairs web research with authorized reads from your site. Check your account's connector availability and organization policy before setup. This guide uses an HTTPS endpoint reachable from Perplexity; Enterprise PrivateLink is a separate documented network route and has not been tested with GoBuildWP here.
Checked against Perplexity's documentation on 29 September 2026, entries from GoBuildWP Free 1.18.6
MCP Server URL https://your-site.com/wp-json/mcp/wppilot-oauth
Authentication OAuth
Transport Streamable HTTP- Availability
- Check account and organization controls
- Transport
- Streamable HTTP (SSE also offered)
- Auth options
- OAuth, API key or none
First task
A first question that uses both halves
Ask for research that needs the web and your site together. Everything WordPress-side is a read.
Use my WordPress connector for my own site and the
web for everything else. Change nothing on my site.
Find my page about pricing (wppilot/search-content)
and read it (wppilot/get-content). Then compare it
with how three competitors present pricing, and list
what my page is missing.Setup
Add WordPress to Perplexity
Everything here is on Perplexity's side except the sign-in, which happens on your WordPress site.
Open Connectors
Open Settings from your account and go to Connectors. GoBuildWP's walkthrough reaches it from the profile picture at the bottom left.
Add a custom connector
Paste the MCP server URL (HTTPS is required), add a description, choose OAuth for authentication and Streamable HTTP for transport. An icon is optional.
Acknowledge and add
Perplexity asks you to confirm you understand the risk of a custom connector. Tick it and add the connector.
Authenticate from the card
The connector appears under Connectors. Click its card to start authentication, sign in on your WordPress site, and it becomes enabled.
Share it, or not, on Enterprise
Enterprise administrators can share a connector with the organization and decide whether members may add their own. Keep a WordPress connector private until someone has checked what its user can do.
Verify the connection before allowing changes
Select Read Only explicitly; the default is Production Safe. Use a dedicated identity with manage_options on a single site, or superadmin on multisite. Match the named tool call, site URL and returned record ID against WordPress.
Use the gobuildwp-your-site-com MCP server in Perplexity. Do not change anything.
1. Report the active GoBuildWP safety profile.
2. List the abilities this connection can see.
3. Call wppilot/get-site-settings and report the site URL and locale.
4. Call wppilot/list-content for the five newest pages,
then wppilot/get-content on one of them.
5. Name every ability you called and each WordPress ID you read.These setup instructions are not a recorded live-client test. Keep credentials out of repositories, logs and shared files.
Inside Perplexity
Research on the web, facts from your own site
The reason to connect Perplexity to WordPress is the comparison: it can search the web for what competitors or documentation say, then read your pages through GoBuildWP and tell you where they fall short. The reads come from your site as the connected user. GoBuildWP connections run as an administrator, so drafts and private pages are readable unless you narrow the abilities this connection may call.
A connector that is added but not authenticated does nothing; the card is where authentication starts and where it is re-run after a revoke. The menu on the card edits or removes the connector, which is the way to change its URL or authentication, since both are fixed at creation.
Perplexity's Mac app can also run local MCP servers through a helper it installs. That is a separate feature from remote connectors, and not the route this guide uses; a remote connector needs nothing on your machine.
Signs it worked
- The connector card shows it enabled
- Sign-in happened on your own WordPress domain
- An answer cites a page it read through wppilot/get-content
- The WordPress user cannot edit anything you did not intend
Troubleshooting
Perplexity errors and their causes
| Symptom | Cause and fix |
|---|---|
| The form rejects the URL | Use a valid HTTPS endpoint reachable from Perplexity for this direct setup. Enterprise organizations can separately arrange AWS PrivateLink through Perplexity; that route is untested with GoBuildWP here. Inspect the actual error before changing access controls. |
| No option to add a custom connector | Check current account entitlement and workspace policy. Enterprise administrators control member-added connectors, disabled by default according to the current setup documentation; a missing button alone does not prove a plan restriction. |
| The connector is added but answers ignore your site | It has not been authenticated, or it is not enabled for the query. Click the card to authenticate. |
| API key authentication is refused | Switch to OAuth. How Perplexity sends an API key was not confirmed, and GoBuildWP expects Authorization: Bearer. |
| Answers include drafts you did not want shared | The connected account is an administrator and can read drafts; a lower WordPress role cannot connect to GoBuildWP. Ask for published content only, and if drafts must stay out, connect with an access token limited to abilities you have checked, and keep unpublished material off this site. |
Connect screen
The Perplexity entries GoBuildWP writes
GoBuildWP's steps name the server, paste the OAuth URL and complete sign-in. Its token steps use the canonical URL with what GoBuildWP calls the bearer-token option; Perplexity's form labels that choice API Key, and how Perplexity places the key in the request was not confirmed for this guide. OAuth is the route to use unless you have a reason not to.
| OAuth 2.1 | Choose OAuth in the connector form. Perplexity starts authentication when you first click the connector's card. |
|---|---|
| Access token | The API Key option in the form. Unconfirmed whether Perplexity sends it as a Bearer header; test with a read before relying on it. |
Endpoints on your site: /wp-json/mcp/wppilot-oauth for OAuth, /wp-json/mcp/wppilot for tokens and passwords. Through the optional GoBuildWP Cloud instead, every client uses https://app.gobuildwp.com/mcp with the server name gobuildwp, and a personal Cloud token is read from GOBUILDWP_TOKEN where the client supports environment variables.
MCP Server URL https://your-site.com/wp-json/mcp/wppilot
Authentication API Key
Key wpp_YOUR-ACCESS-TOKENFAQ
Perplexity questions
Which Perplexity plans can add a WordPress MCP connector?
Confirm availability in your current account and workspace. The retrieved remote-connector setup page describes organization controls but does not establish every plan's entitlement. Enterprise member-added connectors require administrator enablement; this guide does not promise access on a named plan.
Does Perplexity need my WordPress password?
No. With OAuth you sign in on your own site and Perplexity receives a grant it can refresh, which you can revoke from Connected Apps in WordPress.
Can Perplexity edit my WordPress site?
Only through abilities the connected user and the GoBuildWP safety profile allow. On Read Only, it can research and read your pages but every write is refused.
Is the Perplexity Mac app's local MCP the same thing?
No. Local MCP on the Mac runs servers on your computer through a helper. A remote connector, which this guide sets up, is called from Perplexity's servers.
Related
Other hosted clients
- Manus: an agent that carries out the plan, not just the research
- Mistral Le Chat: connectors with per-function approvals
- Claude on the web: custom connectors on every plan
Perplexity documentation read on 29 September 2026
Research the web, read your own site.
Add the connector, keep it to reads with a Read Only profile or token, and let Perplexity compare before anyone edits.