Skip to main content
Connect an integration MCP to give your agent one website’s tools. The steps match connecting the Pomerado MCP, with the integration named.

​
Get the setup for your client

1

Open the integration

On the Dashboard, open the integration’s page and its Connect panel. From code, call GET /v1/connect with client and integration_id.
2

Copy the snippet

The answer holds the MCP’s name, its mcp_url and a snippet: the command to run or the config to paste for that client.
3

Sign in

With OAuth, the default, your client opens sign-in itself and the snippet holds no secret.
client is claude_code, codex, cursor, vscode, claude_desktop, or any for a generic client’s JSON config. Client-specific steps are in Client setup.

​
Use an API key instead

Pass auth=api_key for a snippet that sends an API key from the POMERADO_API_KEY environment variable. Claude Desktop takes OAuth only. An API key bound to one integration reaches only that integration: it finds and runs its tools and follows their jobs, and nothing else. See API keys.

​
Wait until it’s ready

An integration’s status says whether its MCP is ready to connect. While it reads setting_up, or failed while Pomerado retries, the setup call answers mcp_not_ready; ask again later. Its tools still run through the Pomerado MCP and REST in the meantime.
  • Use the exact URL the setup gives. A website’s public and private integrations have different URLs.
  • A public, ready integration also has a keyless_mcp_url, its URL with /keyless added, which works without signing in and lists only public read-only tools that need no login. See Try without a key.
  • A disabled or not_hosted integration has no MCP of its own; its setup answers not_found.