Docs / YouSpot MCP server

YouSpot MCP server

Connect Claude, ChatGPT, Cursor or Claude Code to https://youspot.com/mcp/v1 and let an agent read and write your own CRM.

YouSpot runs a Model Context Protocol server at https://youspot.com/mcp/v1. Transport is streamable HTTP; auth is OAuth 2.1, so a client that speaks MCP can connect with no key pasted anywhere.

Connect a client

Claude

Settings, Connectors, Add custom connector, then paste https://youspot.com/mcp/v1. Claude registers itself and opens the consent screen.

ChatGPT

Settings, Connectors, Create, then paste https://youspot.com/mcp/v1 and choose OAuth. ChatGPT registers dynamically the same way.

Claude Code

claude mcp add --transport http youspot https://youspot.com/mcp/v1

Cursor

Add this to ~/.cursor/mcp.json:

{
  "mcpServers": {
    "youspot": {
      "url": "https://youspot.com/mcp/v1"
    }
  }
}

A client that only speaks stdio

Some clients still launch a local process and talk to it on stdin and stdout, and cannot reach a remote server at all. @youspot/mcp is that process: it forwards each JSON-RPC message to /mcp/v1 and writes the replies back. Nothing to install, and nothing to configure beyond the token.

{
  "mcpServers": {
    "youspot": {
      "command": "npx",
      "args": ["-y", "@youspot/mcp"],
      "env": { "YOUSPOT_TOKEN": "..." }
    }
  }
}

If your client speaks streamable HTTP, use the URL above instead. One less moving part.

What the tools do

Family	What it covers
Brain graph	Search, read and write the objects in your graph: people, companies, notes, files.
Attention	What needs you today: unanswered threads, stale follow-ups, upcoming meetings.
LinkedIn	Query your imported connections and the companies behind them.
Gmail	Read threads, draft and send mail from a connected mailbox.
Google Calendar	Read events for context on who you are about to meet.
HubSpot	Read and sync contacts and companies with a connected portal.
Company research	Research a company and file the result as an object.
Prospecting	Find people and companies that match a description.
Files and imports	Import a file and read what was extracted from it.
Domains	Value and suggest domain names.
Slack, X/Twitter, Obsidian	Read from the other sources a member has connected.

What it is not

This is not a public web search and not a shared directory. Every tool call is scoped to the signed-in member, so an agent asking "who do I know at Acme" gets that person's network and nobody else's.

Calling it directly

The server is plain JSON-RPC over HTTP POST. initialize, ping and tools/list answer without a credential, so you can handshake and read the tool list before anyone has signed in:

curl -X POST https://youspot.com/mcp/v1 \
  -H "Content-Type: application/json" \
  -d '{"jsonrpc":"2.0","id":1,"method":"tools/list"}'

Every tools/call needs an OAuth access token or a member API token, because every tool reads one person's own CRM. See Authentication or the machine walkthrough at auth.md.

curl -X POST https://youspot.com/mcp/v1 \
  -H "Authorization: Bearer $YOUSPOT_TOKEN" \
  -H "Content-Type: application/json" \
  -d '{"jsonrpc":"2.0","id":1,"method":"tools/call","params":{"name":"get_connections_summary","arguments":{}}}'

Try it without an account

A third server at https://youspot.com/mcp/sandbox runs the same read tools against a demo account whose contacts, companies and interactions are generated. No credential, no signup, no credits. Every tool that writes is refused there, and the answers are shaped exactly like the answers a real account gives. The same server answers as /mcp/v1 under the sandbox mount, and GET https://youspot.com/sandbox describes that mount and says whether the demo account is seeded.

curl -X POST https://youspot.com/mcp/sandbox \
  -H "Content-Type: application/json" \
  -d '{"jsonrpc":"2.0","id":1,"method":"tools/call","params":{"name":"search_graph_objects","arguments":{"query":"Meridian"}}}'

Machine descriptions

Document	What it holds
Server card	The endpoint, the transport, the protocol versions and every tool. Built from the live tool table, so it cannot claim one that does not exist. `GET /mcp/v1` returns the same document.
auth.md	Discover, register, consent, exchange, call, revoke. In that order, with runnable requests.
api-catalog	RFC 9727 linkset pointing at the card, the docs and the OAuth metadata.

https://youspot.com/mcp still answers for every client that already has it, so nothing that is connected today has to change. /mcp/v1 is the URL every discovery document advertises.

Where this server is listed

Every entry is published by us and points back at this domain, which is what makes them verifiable rather than merely present: com.youspot/youspot in the official Model Context Protocol registry, under a namespace verified by a DNS record on youspot.com; youspot/youspot-mcp on Smithery, which connects to /mcp/v1 over OAuth; and YouSpot MCP on mcp.so, whose tool list is fetched live from /mcp/v1 rather than typed in by hand.