Get started

MCP client setup

Configure your coding agent to talk to the Gittensory MCP. Pick stdio for local agents, remote for cloud agents.

Generate config

These commands print config only. They do not mutate your local client files.

gittensory-mcp init-client --print codex
gittensory-mcp init-client --print claude
gittensory-mcp init-client --print cursor
gittensory-mcp init-client --print mcp

bash

--print mcp uses the same JSON snippet as Claude Desktop and Cursor for other stdio MCP hosts that expect the mcpServers shape.

Codex (OpenAI)

~/.codex/config.toml

[mcp_servers.gittensory]
command = "npx"
args = ["-y", "@jsonbored/gittensory-mcp@latest", "--stdio"]

Claude Desktop

claude_desktop_config.json

{
      "mcpServers": {
    "gittensory": {
      "command": "npx",
      "args": ["-y", "@jsonbored/gittensory-mcp@latest", "--stdio"]
    }
  }
}

Cursor

.cursor/mcp.json

{
      "mcpServers": {
    "gittensory": {
      "command": "npx",
      "args": ["-y", "@jsonbored/gittensory-mcp@latest", "--stdio"]
    }
  }
}

Remote MCP

The Worker also exposes a remote MCP endpoint. Use this when your agent runs in the cloud or you don't want a local Node process.

https://gittensory-api.aethereal.dev/mcp

http

Local --stdio is the default recommendation. It keeps auth + analysis on your machine and is the easiest path to log into with GitHub Device Flow.

← PreviousQuickstart Next →Miner workflow