Synal
MCP API docs Sign in
Contact lookups default to email only. Send channel=phone to the REST unlock endpoint for an explicit phone lookup, and poll email_unlocked or phone_unlocked for the requested channel. One contact uses one monthly unlock, even when both channels are requested. This allowance is shared with investor email unlocks in the app. Existing contact access is preserved.

Model Context Protocol

Synal MCP server

Connect Claude, or any MCP client, to your Synal account and work the funding feed in plain language: browse rounds, dig into companies and contacts, and unlock contact details without leaving your assistant. It runs on the same data, permissions, and settings as the app.

Connect your assistant

Three steps: grab your key, add the server to your client, then ask it something to confirm it's working.

01

Get your API key

Copy it from the API key page after signing in. It's how your assistant authenticates as you — keep it private, since anyone with it can act on your account.

02

Add the server to your client

Pick whichever you use — the steps below cover Claude Desktop and Claude Code; anything else follows the same pattern.

Claude Desktop

  1. Open Settings → Developer → Edit Config.
  2. Paste the block below into the config file, replacing YOUR_API_KEY with the key from step 1.
  3. Save the file, then fully quit and reopen Claude Desktop.
{
  "mcpServers": {
    "synal": {
      "type": "http",
      "url": "https://mcp.synal.to/mcp",
      "headers": {
        "Authorization": "Bearer YOUR_API_KEY"
      }
    }
  }
}

Claude Code

  1. Open a terminal, in or outside a project — this is a user-level connection.
  2. Run the command below, replacing YOUR_API_KEY with the key from step 1.
claude mcp add --transport http synal https://mcp.synal.to/mcp \
  --header "Authorization: Bearer YOUR_API_KEY"

Other clients

  1. Open its MCP or “connectors” settings.
  2. Add a server with transport Streamable HTTP, URL https://mcp.synal.to/mcp, and header Authorization: Bearer YOUR_API_KEY.
  3. Save, then restart or reload the client.
03

Confirm it's connected

Ask it something like “What funding rounds closed this month?” If it comes back with live results, you're set. If it says it has no way to do that, double-check you fully restarted the client after saving the config.

Troubleshooting

  • Tools don't show up. The client needs a full restart, not just a new chat — quit it completely and reopen.
  • Unauthorized / connection rejected. Check the key was copied in full with no extra spaces, and that it hasn't been regenerated on the API key page since.
  • Still stuck? Re-check the JSON or command against the block above — a missing comma or quote is the usual culprit.

Endpoint

A single Streamable HTTP endpoint. Point your MCP client here and authenticate with your API key as a bearer token. 

https://mcp.synal.to/mcp

What you can do

Everything you'd normally click through in Synal, your assistant can fetch and reason over — no dashboards, no exports. A few of the things people ask:

Browse funding events

Scan the latest rounds — filtered, summarized, and ranked however you ask.

“What funding rounds closed this month over $10M?”

Dig into a company or round

Pull the full picture on any event — the company, the raise, and everyone attached to it.

“Tell me everything about the Northwind Labs round.”

Find the right contacts

See who's on a deal and let your assistant zero in on the person you actually need.

“Who should I reach out to at that company?”

Unlock contact details

Reveal a contact’s email on demand. Request phone numbers separately through the app or REST API.

“Unlock the CFO’s email.”

How it works

Synal speaks MCP, the open standard AI assistants use to reach real tools and data. The whole loop:

  1. 01

    You connect

    Add this endpoint to your assistant once, using your personal API key. That's the only setup.

  2. 02

    You ask in plain language

    Your assistant recognizes a funding question and quietly calls the right tool on this server.

  3. 03

    Synal answers

    Live results come straight from your account — same data, permissions and settings.

Your account stays yours

Every request runs under your own API key over an encrypted connection, and the server keeps nothing between requests. Your assistant only ever sees what your Synal account already lets you see.

Tools

You never call these directly — you just ask, and your assistant picks the right one. The full set, with the arguments each accepts:

list_funding_events

Browse funding events, newest first, with pagination.

Arguments

page?, per_page? (1–100, default 50).

get_funding_event

Everything about one event — its company and contacts included.

Arguments

id.

list_contacts

The contacts on an event. Email and phone stay hidden until unlocked.

Arguments

funding_event_id.

unlock_contact

Reveal a contact’s email. Phone lookup requires an explicit channel=phone request through the REST API or the app.

Arguments

contact_id, wait? (default true), timeout_seconds? (default 30).

get_contact_unlock_status

Check on an unlock in progress.

Arguments

contact_id.

Good to know

  • Requires the yearly plan. The connection uses your API key, which is a yearly-plan feature with unlimited unlocks.
  • Same data you already see. The connection acts as you; it can't reach anything your Synal account couldn't already access.
  • Rotate your key any time. Manage or regenerate it from the API key page — regenerating instantly cuts off the old one.