Add a custom MCP connector

Connect any HTTP, SSE or STDIO MCP server with the right authentication.

1 min read Updated October 19, 2026

Connect any MCP server - one from a vendor that isn't in the store, an open-source server, or one your team built.

Before you begin

You need the server's URL (for hosted servers) or its launch command (for STDIO servers), and to know how it authenticates. The server's README usually lists both.

Add the connector

Open Tools → Installed → MCP Connector and create a new connector.
Fill in the basics:
- Name - for example My MCP Connector.
- Description (Markdown supported) - what it does. The AI reads this, so be specific.
- Icon - an optional image URL.
Choose the Server Type:

Server Type	Use when	You enter
HTTP	The server is hosted at a URL (most modern servers)	Server URL, e.g. `https://example.com/mcp`
SSE (Server-Sent Events)	Older hosted servers that use SSE	Server URL
STDIO	The server runs as a command	Command, e.g. `npx -y @modelcontextprotocol/server-example`, plus optional Environment Variables (JSON)

Choose the Authentication Type:

Authentication Type	What to provide
None	Nothing
API Key	The key
Bearer Token	The token, sent as `Authorization: Bearer ...`
OAuth	Optional OAuth Client Config (JSON) if the server requires your own client. Then click Connect with {name} to sign in

Need anything else? Open Advanced options to add Custom HTTP headers or an Auth Config (JSON).
Save, then click Test connection.

Example: a hosted server with a token

text

Name:                Acme Docs
Server Type:         HTTP
Server URL:          https://mcp.acme.dev/mcp
Authentication Type: Bearer Token
Bearer Token:        acme_pat_...

Troubleshooting

Connection test failed - check the URL (including the /mcp path), the auth type and the token.
No tools appear - the server connected but exposes no tools for your account. Check its permissions or scopes.
More help in Tools & connectors not working.

Was this article helpful?