Connect your AI agent to Kosmonaut

If you manage a space on Kosmonaut, you can now point your AI assistant straight at it. Ask it to fix a typo in your Serbian copy, add a perk, reorder a gallery, or draft next week's event — and it works on your real space, signed in as you.

It runs on the Model Context Protocol (MCP), the standard most assistants now speak for connecting to outside tools. You add one address and sign in through your browser. There are no API keys to copy and nothing to paste into a config file that you wouldn't want to share.

The address

https://www.kosmonaut.rs/api/mcp

That's the whole configuration. The first time your assistant uses it, a browser window opens, you sign in with the Kosmonaut account you already have, and you approve read and write access once. Your assistant keeps the token and refreshes it on its own.

Before you start

Sign in to kosmonaut.rs once in a browser. The server matches your login to a Kosmonaut user. An account that has never opened the site has no record to match.

Adding it to your assistant

Claude Code

claude mcp add --transport http --scope user \
  kosmonaut https://www.kosmonaut.rs/api/mcp

Then run /mcp and choose Authenticate. Leave off --scope user to add it to the current project only.

Claude, desktop and web

Settings → Connectors → Add custom connector. Paste the address, then press Connect to sign in. Custom connectors need a paid Claude plan.

ChatGPT

Settings → Connectors → Advanced → switch on Developer mode. Create a connector with the address above and OAuth as the sign-in method. Web only, on Plus, Pro, Business, Enterprise or Edu.

Cursor

Add this to ~/.cursor/mcp.json, or to .cursor/mcp.json for a single project:

{
  "mcpServers": {
    "kosmonaut": { "url": "https://www.kosmonaut.rs/api/mcp" }
  }
}

Then open Settings → MCP and press the sign-in button on the Kosmonaut row.

Codex CLI

codex mcp add kosmonaut --url https://www.kosmonaut.rs/api/mcp
codex mcp login kosmonaut

The same thing written into ~/.codex/config.toml:

[mcp_servers.kosmonaut]
url = "https://www.kosmonaut.rs/api/mcp"

Gemini CLI

gemini mcp add --transport http \
  kosmonaut https://www.kosmonaut.rs/api/mcp

Or in ~/.gemini/settings.json:

{
  "mcpServers": {
    "kosmonaut": { "httpUrl": "https://www.kosmonaut.rs/api/mcp" }
  }
}

VS Code, with Copilot in agent mode

code --add-mcp '{"name":"kosmonaut","type":"http","url":"https://www.kosmonaut.rs/api/mcp"}'

Anything else

An assistant that only speaks the older stdio transport can reach the server through the mcp-remote bridge, which runs the same browser sign-in:

{
  "mcpServers": {
    "kosmonaut": {
      "command": "npx",
      "args": ["-y", "mcp-remote", "https://www.kosmonaut.rs/api/mcp"]
    }
  }
}

What you can ask for

Your assistant can read your space and its locations, and change the things you would change yourself in the admin:

• Copy and translations — titles, descriptions, every language at once, with a report of what's still missing
• Page layouts — your space hub and each location page, section by section
• Perks, work areas and galleries — add, reorder, relabel, remove
• Articles and events — status, slug, schedule, cover, byline

It can do exactly what your own account can do, and no more. A staff member limited to one location stays limited to that location.

What to keep in mind

Every change is live. There is no staging step: a copy edit lands on the public site immediately. Page layouts are the exception — those go to a draft, and reach visitors only when published.

Public pages can lag up to ten minutes behind a change, because they're cached. The preview link your assistant gets back with every read shows the new version straight away.

Every change is attributed to you and recorded in the activity log, along with which assistant made it. If a token ever needs revoking, it's yours alone.

If it doesn't connect

A refusal that never opens a browser. Check the address ends in /api/mcp with no trailing slash, and that your assistant is set to HTTP rather than SSE.

Sign-in works, but every request is refused. Your account doesn't have access to the agent surface yet. Get in touch and we'll open it.

A change that doesn't show up. If it's a page layout, it's sitting in a draft waiting to be published. Otherwise give the cache ten minutes, or open the preview link.

---

Questions, or access for your team: get in touch and we'll set you up.