# How to get your MCP server into Perplexity

Perplexity has no submission queue. Companies can propose a connector, and Perplexity gets in touch if it wants to build it with you. In the meantime, anyone on a paid plan can add your remote server by URL, so publish clear instructions for that.

## Proposing a connector

Perplexity's Plugins marketplace takes proposals from companies through a form at [pplx.ai/connector-form-submission](https://pplx.ai/connector-form-submission). Questions go to connectors@perplexity.ai ([Perplexity](https://www.perplexity.ai/help-center/en/articles/2026092501-submit-a-connector-proposal)).

- **Who it's for:** someone representing a company that wants a connector for its product.
- **What you get:** an approved connector appears as a plugin with one connector. Plugins with several parts aren't proposed this way.
- **No promises:** Perplexity reviews proposals on customer value, technical feasibility, security and its own product priorities, and contacts you only if there's a fit. There's no published timeline.

The help article asks for:

- Your company name and website
- The product or service to connect
- A short description of the connector
- The customer problem it solves
- Links to your API, developer and security documentation
- A contact for partnership and technical questions

The form itself goes much further: 68 questions in seven sections, 51 of them required ([MCP Tower](https://mcptower.com/blog/submit-connector-to-perplexity)). Have these ready before you open it:

- Where you store data, and your security certifications
- A contact for security incidents, and your policy for retiring old versions
- How sign-in works: dynamic client registration or a fixed client, and the scopes you ask for
- A tagline of up to 80 characters, with no marketing superlatives
- Optionally, example prompts with the answers you expect, to help them test

If you email connectors@perplexity.ai with questions first, include your company name, a short description of the connector and links to your technical documentation, so it reaches the right team.

## Without a listing

Users on Pro, Max and Enterprise plans can add any remote server themselves ([Perplexity](https://www.perplexity.ai/help-center/en/articles/13915507-adding-custom-remote-connectors)):

1. Open Plugins, then Add custom, then Add MCP connector, and choose Remote.
2. Enter your server's HTTPS address.
3. Choose how it signs in: none, an API key, or OAuth. For OAuth, Perplexity looks for your metadata at `/.well-known/oauth-authorization-server`.

On Enterprise, an admin has to allow custom connectors first, in Organization settings under Connectors. Local servers only work in Perplexity's Mac app ([Perplexity](https://www.perplexity.ai/help-center/en/articles/11502712-local-and-remote-mcps-for-perplexity)).

Since November 6, 2026, users can also install a plugin from a public GitHub repository with a `plugin.json`, or upload one as a ZIP ([Perplexity](https://www.perplexity.ai/help-center/en/articles/2026100802-create-or-upload-a-custom-plugin)). That's a second way in: put a plugin in a public repo and link to it from your docs.

So the practical route for most servers is a page in your docs titled "Use with Perplexity", with these steps, your server's address and screenshots.

Checkers to run before you submit, and companies that will submit for you, are in the [overview](https://submitmcp.com/guides).
