Add the Jenks MCP server to your client

Choose remote or local

• Remote — https://jenksguo.xyz/mcp (Streamable HTTP, JSON-RPC 2.0). Nothing to install. Use it when your client supports remote MCP servers.
• Local — the jenks CLI runs an MCP server on stdio with jenks mcp. It forwards calls to the live site. Use it when your client only supports local (stdio) servers.

Both expose the same public tools: get_brief, list_experience, get_entry, list_lenses, search_jenks, get_document and ask_jenks. See the MCP tools reference.

To install the CLI first:

curl -fsSL https://jenksguo.xyz/downloads/install.sh | sh
jenks --version

Claude Code

Remote:

claude mcp add --transport http jenks https://jenksguo.xyz/mcp

Local:

claude mcp add jenks -- jenks mcp

Check with /mcp inside Claude Code.

Claude Desktop

Edit claude_desktop_config.json and restart Claude Desktop. For the local server:

{
  "mcpServers": {
    "jenks": { "command": "jenks", "args": ["mcp"] }
  }
}

If your version supports remote servers, add https://jenksguo.xyz/mcp as a custom connector in the app's settings instead.

Cursor

Add to ~/.cursor/mcp.json (or the project's .cursor/mcp.json). Remote:

{
  "mcpServers": {
    "jenks": { "url": "https://jenksguo.xyz/mcp" }
  }
}

Local:

{
  "mcpServers": {
    "jenks": { "command": "jenks", "args": ["mcp"] }
  }
}

ChatGPT

Where your ChatGPT plan and client support custom connectors (developer mode), create a connector with the server URL https://jenksguo.xyz/mcp. No authentication is needed for the public tools. If connectors are not available, use the Open in ChatGPT button on https://jenksguo.xyz/agents — it starts a chat that reads the public files instead.

Any other client

Point it at the remote URL, or run jenks mcp as a stdio command. A GET request to https://jenksguo.xyz/mcp returns a discovery document with the protocol version, the tool names and example JSON-RPC calls:

curl -s https://jenksguo.xyz/mcp

Admin variant (Jenks only)

The admin server adds the admin_* tools (read, validate, write, AI-edit, deploy status, promote). It needs the personal admin token, stored in the Keychain as agent-env:JENKSGUO_ADMIN_TOKEN.

Remote, with a header:

claude mcp add --transport http jenks-admin https://jenksguo.xyz/mcp/admin \
  --header "Authorization: Bearer $JENKSGUO_ADMIN_TOKEN"

Local, with the token in the environment:

export JENKSGUO_ADMIN_TOKEN="$(security find-generic-password -s agent-env:JENKSGUO_ADMIN_TOKEN -w)"
jenks mcp --admin

In a JSON config, pass the token through env rather than writing it into the file where possible. Never share a config file that contains the token.

Troubleshooting

• Tools do not appear: restart the client; check jenks --version is on your PATH.
• 429 from ask_jenks: the assistant is rate-limited; wait a minute.
• 401 on /mcp/admin: the token is missing, wrong or rotated.