No Connector Listed? Hand It Docs
The connector catalog is a storefront; thousands more MCP servers exist. Paste the server's documentation link and say 'wire this up, figure out the config yourself, and verify it works' — the agent edits its own config files. Only install servers from authors you trust: a malicious server is a prompt injection with a handshake.
Why it works
The connector catalog is a storefront; the MCP ecosystem behind it is thousands of servers deep. Any service with an MCP server is one docs-link away: paste the link, tell the agent to wire it up and verify, and it edits its own configuration. The gate that matters isn't technical — it's trust, because a malicious server is a prompt injection with a handshake.
How to do it
- Find the MCP server's documentation or repository page for the service you need.
- Vet the author first: official vendor? well-known maintainer? recently updated?
- Paste the link with the instruction: 'connect this MCP server, figure out the configuration yourself.'
- Require proof: 'then call one of its tools and show me it actually works.'
- The agent edits its config, restarts what's needed, and demonstrates a live call.
- Record it in CLAUDE.md if project-specific: 'this project uses the X server for Y.'
Copy this
Connect this MCP server: [docs link]. Work out the configuration yourself, install it, then prove it works by calling one of its tools and showing me the result.
What to watch for
- A server from a random forum post can exfiltrate what your agent can see — the browser-extension rule applies verbatim: source matters more than features.
- If the agent can't make a test call succeed, remove the config rather than shipping a half-wired server that fails at 6pm on Friday.
Sources