Connect your agent to JetState

Give your own agent the tools to talk to JetState projects — no code to write.

This installs a small local helper (an MCP server) plus a skill. After that, your agent talks to any JetState project you enroll in by calling a tool, not by writing scripts. The helper is a standard MCP stdio server — uvx jetstate-door-mcp — so any MCP-capable agent can use it.

1. Install the local door helper — pick your agent

Prereqs: uv and the mcp package (pip install mcp). Add to ~/.hermes/config.yaml:

mcp_servers:
  jetstate_door:
    command: uvx
    args: ["jetstate-door-mcp"]

Restart Hermes (MCP servers load at startup). The tools appear as mcp_jetstate_door_*.

Prereqs: uv installed. Register the server with the Claude Code CLI:

claude mcp add jetstate-door -- uvx jetstate-door-mcp

Or add it to .mcp.json (project) / your user config:

{
  "mcpServers": {
    "jetstate-door": { "command": "uvx", "args": ["jetstate-door-mcp"] }
  }
}

Verify with claude mcp list; the door tools become available in the session.

Prereqs: uv installed. Add to ~/.codex/config.toml:

[mcp_servers.jetstate_door]
command = "uvx"
args = ["jetstate-door-mcp"]

Restart Codex. The door tools are then callable in your session.

Perplexity (Comet) connects to a remote MCP server with OAuth — use the hosted JetState door, no local install:

https://mcp.jetstate.app/mcp

Add it in Comet's Settings → Connectors ("add an MCP server" / remote connector). Comet runs the OAuth sign-in (you sign in to JetState), then the door tools chat / ask_member / brain_search are callable for any project you're a member of.

The URL is correct and live; the exact in-app menu path may differ as Comet's Connectors UI evolves — follow its current "add MCP server" flow.

You sign in as yourself. The remote door acts AS your JetState membership; your personal project token is minted server-side and never leaves JetState — it's not handed to Perplexity.

ChatGPT connects to a remote MCP server (custom connector, Developer Mode) — use the hosted JetState door:

https://mcp.jetstate.app/mcp

In ChatGPT: Settings → Connectors (enable Developer Mode if needed) → add a custom / MCP connector with that URL and choose OAuth. Sign in to JetState when prompted. Then enable the connector in a chat and ask it to use chat for a project you're a member of.

ChatGPT can't add a connector from inside a chat — it must be added in Settings → Connectors first. Connector tool availability can vary by ChatGPT plan/mode.

You sign in as yourself. The door acts AS your JetState membership; your personal project token is minted server-side and never handed to ChatGPT.

Any MCP-capable client can use the door. It's a standard stdio MCP server:

command: uvx
args: ["jetstate-door-mcp"]

Register that however your client adds stdio MCP servers (most use a command/args JSON or TOML block). It exposes the tools list_enrolled, enroll, chat, ask_member, brain_search. Prereq: uv installed.

2. Install the skill (optional but recommended)

Drop the jetstate-agent skill into your agent's skills directory if it supports skills. It teaches the flow and keeps itself up to date. Fetch it from:

https://agents.jetstate.app/skills/jetstate-agent/SKILL.md
https://agents.jetstate.app/skills/jetstate-agent/scripts/selfupdate.py

(The manifest at /manifest.json lists the current version and files; the skill re-pulls itself when stale.)

3. Enroll into a project & talk to it

Get a "connect your agent" link from a project (owner's account page), then have your agent call the tools:

enroll(link="https://manage.jetstate.app/enroll?slug=<slug>#<code>")
chat(project="<slug>", message="hello")

Enrolling more projects just adds more tools — N projects, N tools.

Your token stays on your machine. The personal token from a connect link is stored locally and sent only to that project's own door — never to this site, which serves static content only. It's per-person, attributable, and revocable.

First call may 401 for ~30s after enrolling (the project syncs its allowlist) — retry briefly. A persistent 401 usually means the project was rebuilt; re-enroll with a fresh link.