RoboSystems
Browse guides

Connect Claude, ChatGPT or any MCP client

Add RoboSystems to Claude, ChatGPT, Claude Code, Cursor or VS Code with one address. Sign in, choose a graph, and start asking.

RoboSystems is a remote MCP server. There is nothing to install: you give your AI client one address, sign in to RoboSystems, and choose the graph the client may work on. From then on the client can read that graph, and act on it within your role.

https://api.robosystems.ai/v1/mcp

The first time a tool runs, the client opens RoboSystems in your browser. You sign in, choose a graph and approve. What that screen asks, and how to change the graph later, is in Sign-in and graph access.

You need a RoboSystems account and a graph to connect: your own, a RoboLedger graph, or the SEC filings. See Graphs, tiers and credits.

Claude

claude.ai and Claude Desktop: Customize → Connectors → Add → Add custom connector, and paste the address. Claude detects the sign-in on its own, so leave the OAuth client fields blank.

On a Team or Enterprise plan, an organization owner adds the connector first, under the organization's connector settings. Each member then connects it and signs in to RoboSystems with their own account.

To read SEC filings with no address to paste, add RoboSystems SEC from Claude's connector directory instead. You still need a RoboSystems account with an SEC filings subscription; see Analyze SEC filings.

Claude Code: add the server, then run /mcp, pick robosystems and sign in.

claude mcp add --transport http robosystems https://api.robosystems.ai/v1/mcp

Claude Code can also install the RoboSystems plugin for Claude Code, which adds the same server plus four skills: finding its way around a graph, analyzing SEC filings, closing the month on RoboLedger, and building a board pack from a closed period. See Skills and the RoboSystems plugin.

claude plugin marketplace add RoboFinSystems/robosystems-plugin
claude plugin install robosystems@robosystems

ChatGPT

Open Plugins, then Add → Create custom MCP server. Paste the address under Connection, leave Authentication on OAuth, accept the warning about custom servers and choose Create as a plugin. Custom MCP servers aren't available on every ChatGPT plan; if the menu item is missing, turn on developer mode in ChatGPT's settings, and on a business workspace an admin may need to allow it. A connection added this way serves every tool of the graph you choose, RoboLedger included.

To read SEC filings with no address to paste, install RoboSystems from ChatGPT's plugin directory instead. That listing reaches the SEC filings only, and it is not the Claude Code plugin above. You still need a RoboSystems account with an SEC filings subscription.

Cursor, VS Code and other clients

Add the address to the client's MCP configuration. The editor opens the sign-in the first time it connects. In Cursor, the entry goes under mcpServers:

"robosystems": { "url": "https://api.robosystems.ai/v1/mcp" }

VS Code's mcp.json lists servers under servers and needs the transport type:

{
  "servers": {
    "robosystems": { "type": "http", "url": "https://api.robosystems.ai/v1/mcp" }
  }
}

Any client that supports remote MCP servers over HTTP with OAuth sign-in works the same way. For a client that only runs local servers, use the stdio bridge, which forwards to the same server with an API key.

More than one graph

One connection is one graph. The address above lets you choose the graph when you sign in, so to switch, disconnect in your client and sign in again.

To keep several graphs connected at once, give each its own connection with the graph's own address. In the app, open MCP, choose the graph, and copy its connector. The address has the graph in it:

https://api.robosystems.ai/v1/graphs/{graph_id}/mcp

When you sign in through a graph's own address, that graph is already selected. Subgraphs connect the same way, with the subgraph's id in the address. The public SEC filings are sec:

https://api.robosystems.ai/v1/graphs/sec/mcp

Scripts, CI and clients that can't sign in

A graph's own address also accepts an API key in the X-API-Key header, so a script or CI job can connect without a browser. The app's MCP page generates a key scoped to that graph. The general address above takes a sign-in only and rejects keys.

claude mcp add --transport http robosystems-kg123 \
  https://api.robosystems.ai/v1/graphs/kg123/mcp \
  --header "X-API-Key: <your key>"

"robosystems-kg123": {
  "url": "https://api.robosystems.ai/v1/graphs/kg123/mcp",
  "headers": { "X-API-Key": "<your key>" }
}

A key never goes in the address. For how keys and their scopes work, see Authentication and API keys.

Which address do I use?

AddressWhat it reachesConnects with
https://api.robosystems.ai/v1/mcpAny graph or shared repository you can use, chosen when you sign in, with every tool that graph runsSign-in only
https://api.robosystems.ai/v1/graphs/{graph_id}/mcpThat one graph or subgraph, already selected. Use one per graph to keep several connected. sec is the SEC filingsSign-in or an API key
https://api.robosystems.ai/v1/mcp/roboledgerRoboLedger only: your own graphs running RoboLedger, with the ledger and close tools but not subgraph, backup or other administration tools. The app's MCP page shows it when you have a RoboLedger graphSign-in only
RoboSystems SEC in Claude's directory, RoboSystems in ChatGPT'sThe SEC filings only, with nothing to pasteSign-in, and an SEC filings subscription

When in doubt, use the first one.

Try asking

Once connected, start by letting the client orient itself:

  • "Which graph are you connected to, and what's in it?"
  • "What can you do on this graph?"
  • "Show me the schema, then a few example queries."

Go deeper