Connect Signado to Claude Code and Codex

Use this guide to connect your existing Signado workspace to Claude Code or Codex. The connection uses OAuth in your browser, so there are no API keys to create or paste into a config file.

Before you start

• You need a Signado account.
• You need access to the workspace you want the assistant to use.
• The remote endpoint is https://mcp.signado.io/mcp.

Claude Code

Run this command:

claude mcp add --transport http signado https://mcp.signado.io/mcp

Then authenticate:

1. In Claude Code, run /mcp.
2. Choose signado.
3. Click Authenticate.
4. Sign in with your Signado account in the browser.
5. Choose the workspace to connect.
6. Approve the connection.

Codex

Run both commands:

codex mcp add signado --url https://mcp.signado.io/mcp
codex mcp login signado

The login command opens a browser approval flow. Sign in with your Signado account, choose the workspace, and approve the connection.

Codex 0.138.0 sends the OAuth resource parameter natively. If your Codex build cannot complete OAuth, add the resource fallback to ~/.codex/config.toml:

[mcp_servers.signado]
url = "https://mcp.signado.io/mcp"
oauth_resource = "https://mcp.signado.io/mcp"

Very old Codex builds may also need this top-level setting:

experimental_use_rmcp_client = true

Workspace selector

The browser approval flow includes a workspace selector. Choose the workspace you want Claude Code or Codex to use. MCP can only access that selected workspace, and the same app permissions apply to every tool call.

If you choose the wrong workspace, disconnect signado in the client and run the login flow again.

Verify the connection

After approval, the client should list 15 tools:

• ping
• list_warm_leads
• get_warm_lead_detail
• export_leads
• preview_source
• add_source
• remove_source
• find_email
• qualify
• catchup_source
• run_source_once
• cancel_source_run
• draft_message
• list_templates
• save_template

Ask the assistant to call ping. A successful reply confirms that OAuth, workspace selection, and the remote endpoint are working.

Where results appear

• Warm leads appear on /warm-leads.
• Found emails write back to the lead rows on /warm-leads.
• AI drafts from draft_message land in Campaigns at /campaigns.
• Discovery source changes appear in Settings under Discovery Sources.
• Credits show in each paid tool response as credits_charged, balance_after, and session_spend_total. Full usage history is in Settings -> Usage.

Nothing important lives only in the chat. If a session ends, saved results remain in the app.

Credit costs

The MCP connection uses the same credit pool and the same rates as the app:

Action	Cost
Read warm leads	0 credits
Export leads	0 credits
List or save templates	0 credits
Preview a source	1 credit
Add or remove a source	0 credits for the action
New warm lead discovered by an active source	3 credits
Find an email	5 credits per contact
Draft an AI message	7 credits per contact