MCP

Autobound works as a connector in Claude, ChatGPT, Cursor, Claude Code and any tool that supports the Model Context Protocol (MCP). Ask for signals in plain language. No API key to manage: you sign in with your Autobound account.

Server address

https://mcp.autobound.ai/mcp

1. Add Autobound to your tool

Claude (claude.ai, Claude Desktop, Claude mobile)

Open Settings → Connectors.
Click Add custom connector.
Name it Autobound, paste the server address, click Add.

ChatGPT

Open Settings → Connectors (developer mode on).
Click Create, name it Autobound, paste the server address.
Authentication: OAuth. Leave client ID and secret empty.

Cursor
Add to ~/.cursor/mcp.json, then click Login next to the server in Cursor settings:

{ "mcpServers": { "autobound": { "url": "https://mcp.autobound.ai/mcp" } } }

Claude Code

claude mcp add --transport http autobound https://mcp.autobound.ai/mcp

Then run /mcp inside Claude Code and press Enter on autobound to sign in.

2. Sign in to authorize

When your tool connects, an Autobound sign-in window opens. Log in, pick a workspace if you belong to more than one, and click Allow. The tool uses that workspace and its credits. You can disconnect it at any time from Integrations & MCP in the portal: https://signalapi.autobound.ai/integrations

3. Try it

Free first prompt:

What signal types do you have, and what does each one cover?

Then one that uses credits:

Which fintech companies announced layoffs in the last 30 days?

What the connector can do

25 tools: search companies and contacts by signal, look up a company or contact, list signal types and filters, buyer-intent topics, contacts and companies, email verification, monitoring pool, account and credit info. Every call is metered in credits exactly like the REST API. Tools that read data are marked read-only; nothing the connector does can change your account, keys, team or billing.

Scripts and agents that cannot sign in

Send an API key instead. Create one at https://signalapi.autobound.ai/keys and send it on every request:

Authorization: Bearer YOUR_API_KEY

Anyone with the key can spend your workspace's credits. Treat it like a password.

Privacy

What Autobound collects, uses, shares and keeps when a tool is connected: https://signalapi.autobound.ai/privacy/integrations

Troubleshooting

You see	What it means	Do this
"Sign in to Autobound to connect this tool"	The tool has no credential yet	Let the tool open the sign-in window, then click Allow
"API key not recognized"	The key was revoked or mistyped	Create a new key, or remove the header to sign in instead
"Your Autobound connection expired or was disconnected. Sign in again."	The connection was disconnected in the portal, or unused for 30 days	Reconnect from your tool
"This AI tool sent an invalid return address"	The tool's OAuth redirect is not https or localhost	Update the tool, then connect again
Workspace out of credits	Paid lookups are blocked	A workspace owner adds credits at https://signalapi.autobound.ai/billing

Moving from the old address

The old address https://mcp.autobound.ai/sse with an x-api-key header keeps working until December 1, 2026. After that it returns a short message pointing here. Switch now: replace the address with https://mcp.autobound.ai/mcp and drop the header.

Support: [email protected]