RoboGNSS Docs
Markdown Ask Claude Ask ChatGPT
On this page
On this page

Connect an AI agent to RoboGNSS

RoboGNSS has an MCP server, so any AI assistant that supports the Model Context Protocol can read your base stations, hand out rover credentials, and test a rover login the way field hardware would. This page covers creating a key, connecting the assistants we know work today, and what to do when a call fails. For what agents can do with a caster and why some actions stay in the dashboard, read the announcement post.

The essentials, if you already know MCP:

1. Create an API key

  1. Sign in at app.robognss.com and open Settings.
  2. Under API keys, name the key for where it will live (laptop-claude, shop-pc-cursor) and click Create key.
  3. Copy the key now. It starts with rgk_ and is shown exactly once. Treat it like a password: it can see and operate your base stations.
  4. Revoke it any time on the same page. Anything using it stops immediately.

An account can hold up to 10 keys at a time; revoke one to make room for another. Keys are created only by you, signed in — a key cannot create or revoke keys.

2. What a key can do

The tool list is short on purpose. A leaked key can misconfigure an account; it must not be able to destroy one or start a feed to another caster in your name.

Read

Act

Dashboard only, by design

A key cannot set up, change, or enable forwarding to Onocoy or any other caster; delete a base station; apply a PPP result to a base's declared position; or manage API keys. Those need you, signed in.

3. Connect your agent

Claude Code (terminal)

claude mcp add --transport http robognss https://robognss.com/api/mcp \
  --header "Authorization: Bearer rgk_YOUR_KEY"

Then ask: "list my base stations and tell me which are healthy".

Or add it to a project's .mcp.json and keep the key in an environment variable:

{
  "mcpServers": {
    "robognss": {
      "type": "http",
      "url": "https://robognss.com/api/mcp",
      "headers": { "Authorization": "Bearer ${ROBOGNSS_API_KEY}" }
    }
  }
}

Cursor

Settings → MCP → Add server:

{
  "mcpServers": {
    "robognss": {
      "url": "https://robognss.com/api/mcp",
      "headers": { "Authorization": "Bearer ${env:ROBOGNSS_API_KEY}" }
    }
  }
}

VS Code with Copilot

Run MCP: Add Server from the Command Palette and pick HTTP — give it https://robognss.com/api/mcp, then add the Authorization header to the entry it creates. Or write .vscode/mcp.json yourself:

{
  "servers": {
    "robognss": {
      "type": "http",
      "url": "https://robognss.com/api/mcp",
      "headers": { "Authorization": "Bearer ${input:robognss_key}" }
    }
  },
  "inputs": [
    {
      "type": "promptString",
      "id": "robognss_key",
      "description": "RoboGNSS API key",
      "password": true
    }
  ]
}

The inputs block keeps the key out of the file — VS Code asks for it once and stores it for you. Click Start above the server entry, then open Copilot Chat in Agent mode; the RoboGNSS tools appear in its tools list.

Any other MCP client

Zed, Windsurf, and Codex CLI take the same shape: a remote HTTP MCP server at https://robognss.com/api/mcp with an Authorization: Bearer rgk_YOUR_KEY header, wherever that client keeps its MCP settings.

Claude Desktop — through a local bridge, for now

The Connectors screen expects a sign-in flow rather than an API key, so run a small local bridge (mcp-remote, needs Node) that presents the key for you. It runs on the same machine as the app. Add this to claude_desktop_config.json:

{
  "mcpServers": {
    "robognss": {
      "command": "npx",
      "args": [
        "-y", "mcp-remote", "https://robognss.com/api/mcp",
        "--header", "Authorization: Bearer ${ROBOGNSS_API_KEY}"
      ],
      "env": { "ROBOGNSS_API_KEY": "rgk_YOUR_KEY" }
    }
  }
}

The bridge is only needed while the connector screen insists on a sign-in flow; a key-based connector would replace it.

claude.ai and ChatGPT — not yet

The browser apps connect to remote servers directly, so a bridge running on your own machine is not something they can reach, and their connector screens accept only a sign-in flow — not an API key. ChatGPT's is OpenAI's rule, not ours. Connecting either would need a sign-in flow we have not built; until then, use one of the clients above.

4. Things to try

Troubleshooting