Connect Perplexity to WordPress, with boundaries.
Connect an eligible Perplexity plan to a self-hosted WordPress site through a custom remote MCP connector.
Connection profile
Perplexity
Open Settings, choose Connectors, and add the public WPPilot endpoint as a custom remote connector.
Connection sequence
A clean Perplexity setup in six steps.
Use the configuration generated by your own WordPress site. It contains the endpoint shape and selected authentication route appropriate to the installed WPPilot instance.
- 01
Install the foundation
Activate WPPilot Free on a supported WordPress and PHP version, then open its Connect screen.
- 02
Choose the client
Select Perplexity; WPPilot presents the supported connection methods and client-specific guidance.
- 03
Choose authentication
Perplexity can use the native remote OAuth route. A dedicated Application Password is another listed option where supported.
- 04
Add the generated config
Open Settings, choose Connectors, and add the public WPPilot endpoint as a custom remote connector.
- 05
Authorize deliberately
Use a dedicated WordPress identity with the smallest role and WPPilot safety profile the workflow needs.
- 06
Verify read-only
Discover tools, inspect one schema, read a non-sensitive object, and review the result before enabling writes.
Authentication detail
Direct remote OAuth is supported.
Perplexity is in WPPilot's native OAuth client group. It can complete a browser-based authorization against the remote MCP endpoint through its supported flow.
Connection methods in the registry
- OAuth 2.1
- Access token
Perplexity specifics: Custom remote connectors are added under Settings, then Connectors. The current WPPilot registry requires a public HTTPS site and lists Pro, Max, or Enterprise as eligible plans.
Do not copy a generic secret from a public guide. Generate the connection on your site, keep credentials out of source control, and revoke unused credentials in WordPress.
First useful test
Ask Perplexity for evidence, not broad authority.
A short read-only exercise proves the endpoint, credentials, tool discovery, schema lookup, permissions, and response path without changing the site.
- Report the active WPPilot safety profile
- List the abilities currently available to this credential
- Inspect the schema for one read-only content ability
- Read one non-sensitive page or post
- Name the WordPress object and fields used in the answer
- Do not write, publish, delete, or invoke developer tools
- Report any connection or permission error exactly
Perplexity WordPress MCP FAQ
The setup questions that matter.
Connection behavior reflects the current WPPilot client registry reviewed August 24, 2026. Client releases can change; use the generated in-product guidance.
Can Perplexity connect to WordPress through MCP?
Yes. WPPilot includes a Perplexity-specific connection path. Open Settings, choose Connectors, and add the public WPPilot endpoint as a custom remote connector. Custom remote connectors are added under Settings, then Connectors. The current WPPilot registry requires a public HTTPS site and lists Pro, Max, or Enterprise as eligible plans.
Which authentication methods are available for Perplexity?
OAuth 2.1 and Access token are represented in the current WPPilot client registry. The Connect screen generates the path and configuration that match the selected method.
Does connecting Perplexity give it full WordPress access?
No. The dedicated WordPress user's capabilities, WPPilot safety profile, enabled abilities, rate limits, and critical confirmations are enforced on the site.
Can Perplexity use WPPilot Pro integrations?
Yes, when WPPilot Free is active, the Pro licence is active, the relevant companion plugin is present, integration health is usable, and the live ability is permitted.
What should the first test be?
Use staging or Read Only. Ask the client to discover abilities, inspect one ability schema, read a non-sensitive page, and explain exactly which site evidence it used. Do not begin with a broad write.
Compare another client
The WordPress policy stays the same.
Choose a different work surface without rebuilding the permission model on your site.
Native OAuth
Claude Code
Connect Claude Code to WordPress for terminal-based planning, development, content, and site operations through WPPilot.
Open guide →Native OAuth
Claude Desktop
Bring controlled WordPress context and actions into Claude Desktop conversations.
Open guide →Native OAuth
Claude on the web
Connect claude.ai to a public WordPress MCP endpoint using browser-based authorization.
Open guide →Native OAuth
ChatGPT
Connect ChatGPT Plus or another eligible ChatGPT plan to a self-hosted WordPress site through WPPilot's public HTTPS MCP endpoint.
Open guide →Native OAuth
Mistral Le Chat
Connect Mistral Le Chat to a public self-hosted WordPress MCP endpoint with OAuth or a dedicated access token.
Open guide →Native OAuth
Codex CLI
Give Codex typed WordPress abilities for repository-aware and site-aware implementation work.
Open guide →Your site · your policy · your AI client
Put Perplexity to work on WordPress, carefully.
Start with WPPilot Free, a dedicated credential, Read Only, and one inspectable task. Add authority only when the workflow and recovery path are proven.