Connect an AI agent to Seerstone

Seerstone speaks the Model Context Protocol, so an AI assistant you already use can read your organization's properties, deals, and market data on your behalf. You do not need a Seerstone sign-in to read this page, but you do need one to connect.

The endpoint

One URL, every client. This page documents the endpoint served by api.seerstone.co. Connecting also depends on that deployment's sign-in configuration being in place, so treat a first-time failure as a setup question rather than a mistake in these steps.

https://api.seerstone.co/mcp

What happens when you connect

  1. Add the endpoint below to your client. Every client uses the same URL.
  2. Your browser opens and asks you to sign in to your Seerstone account.
  3. Pick the organization you want the agent to read, then click Allow.
  4. The agent can now read that organization's properties, deals, and market data. It cannot write anything.
  5. A connection is tied to the one organization you picked. To use a different one, remove the connection and add it again.

Per-client setup

Claude Desktop

Not verified

Not connected end to end yet. These steps follow the vendor's documented setup for a remote MCP server, but we have not run them against this endpoint.

  1. Open Settings (Ctrl+Comma, or File → Settings).
  2. Open Connectors, then Add custom connector.
  3. Paste the remote MCP server URL and click Add.
  4. Sign in when prompted, pick your organization on the consent screen, and click Allow.

Remote MCP server URL

https://api.seerstone.co/mcp

Claude Code

Verified

Connected end to end against this endpoint: sign-in, consent, and a successful tool call.

  1. Run this in your terminal, not inside a claude session.
  2. Start a new Claude Code session, run /mcp, choose seerstone, then Authenticate.
  3. Your browser opens. Sign in when prompted, pick your organization on the consent screen, and click Allow.

Command

claude mcp add --transport http seerstone https://api.seerstone.co/mcp

Claude.ai

Not verified

Not connected end to end yet. These steps follow the vendor's documented setup for a remote MCP server, but we have not run them against this endpoint.

  1. On Pro, Max, or Free: Customize → Connectors → Add custom connector.
  2. On Team or Enterprise: an Owner adds it first under Organization settings → Connectors → Add → Custom (Web).
  3. Paste the remote MCP server URL and click Add.
  4. Sign in when prompted, pick your organization on the consent screen, and click Allow.

Remote MCP server URL

https://api.seerstone.co/mcp

ChatGPT

Not verified

Not connected end to end yet. These steps follow the vendor's documented setup for a remote MCP server, but we have not run them against this endpoint.

  1. Settings → Security and login → turn on Developer mode.
  2. Open Settings → Plugins (or chatgpt.com/plugins).
  3. Select the plus button, paste the MCP server URL including the /mcp path, and choose OAuth authentication.
  4. Sign in when prompted, pick your organization on the consent screen, and click Allow.

MCP server URL

https://api.seerstone.co/mcp

Cursor

Not verified

Not connected end to end yet. These steps follow the vendor's documented setup for a remote MCP server, but we have not run them against this endpoint.

  1. Add this to .cursor/mcp.json in the project, or ~/.cursor/mcp.json for every project.
  2. Save the file and restart Cursor.
  3. When Cursor asks to authenticate the seerstone server, sign in when prompted, pick your organization on the consent screen, and click Allow.

mcp.json

{
  "mcpServers": {
    "seerstone": {
      "url": "https://api.seerstone.co/mcp"
    }
  }
}

VS Code

Not verified

Not connected end to end yet. These steps follow the vendor's documented setup for a remote MCP server, but we have not run them against this endpoint.

  1. Add this to .vscode/mcp.json in the workspace, or run MCP: Open User Configuration for a user-level file.
  2. The top-level key is servers, not mcpServers.
  3. When prompted, trust and start the server. Sign in when prompted, pick your organization on the consent screen, and click Allow.

mcp.json

{
  "servers": {
    "seerstone": {
      "type": "http",
      "url": "https://api.seerstone.co/mcp"
    }
  }
}

If the connection is refused

401 — sign in again

Your client has no valid sign-in, or the one it had expired or was revoked.

Reconnect the server in your client and sign in again when the browser opens.

403 — missing permission

You are signed in, but the permission to read your organization's portfolio was never granted. Connections made before the permission existed look like this.

Remove the Seerstone connection in your client, add it again, and click Allow on the consent screen so the new permission is included.

403 — no organization

Your Seerstone account is not a member of any organization, so the consent screen had no organization to attach the connection to.

Ask a Seerstone admin to add you to an organization, then reconnect.