Claude

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

ChatGPT

In ChatGPT settings, open Apps or Connectors and create a custom connection named YouSpot with URL https://youspot.com/mcp and OAuth authentication. Complete browser consent, then select YouSpot in the conversation. Custom connections may require developer mode, an eligible plan, or workspace administrator approval. Installing YouSpot in Codex or your terminal does not connect ChatGPT web.

Codex

In the desktop app, open Plugins, MCPs, Add, then choose Streamable HTTP. Enter youspot as the name and https://youspot.com/mcp as the URL. Save and complete sign-in when prompted. You do not need a bearer-token environment variable for OAuth. Restart the app through its restart control to reload the tools.

An agent with terminal access can configure Codex for you. It should reuse an existing matching connection rather than overwrite it. To add a missing connection:

codex mcp add youspot --url https://youspot.com/mcp

Current Codex versions start browser sign-in during this command. If sign-in is still needed, run codex mcp login youspot. Do not repeat login after it already succeeded. The desktop app, CLI, and IDE extension must load the updated configuration; the IDE has its own restart control. An enabled/OAuth entry in codex mcp list does not prove the current chat has loaded the tools.

Claude Code

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

Cursor

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

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

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 and writes the replies back. The client downloads and runs the package; keep the token in its secret settings, not in chat.

{
  "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.

Configuration, sign-in, loaded tools, and a working tool call are separate steps. After connecting, ask the assistant:

Check the YouSpot tools available in this conversation.
Use Check connections (list_integrations) to verify my account access.
Tell me which call succeeded, what sources are connected,
and 3 things you can help me do with the tools you actually have.

A successful response from that tool verifies this conversation can use YouSpot. Reading the public tool list, completing OAuth, or calling the endpoint from a terminal does not. If tools are still absent after a restart, inspect the client's MCP connection error rather than repeating sign-in or starting more tasks. Local hook errors such as "No such file or directory" need the failing command identified separately; signing in again does not repair them.

Other chat apps need support for remote MCP and OAuth, and may require administrator approval. YouSpot cannot install tools into a host that does not support connectors or bypass its consent controls. Connected sources, approved scopes, available data, and credits determine which workflows can run.

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.

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 \
  -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 \
  -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":{}}}'

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 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"}}}'

https://youspot.com/mcp is the recommended endpoint and tracks the latest available implementation, currently v1. Use https://youspot.com/mcp/v1 only when you want to pin v1. Both are supported, neither is deprecated, and existing connections can keep their current URL. If another major version is introduced, /mcp will follow it while the versioned endpoint stays pinned. URL versions are separate from the MCP protocol version negotiated during initialization.

Official entries point back at this domain: 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; and YouSpot MCP on mcp.so. Use the recommended URL above for a new connection; existing entries using /mcp/v1 remain supported.