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
gittensory-mcp init-client --print vscodebash--print mcp uses the same JSON snippet as Claude Desktop and Cursor for other stdio MCP hosts that expect the mcpServers shape. Every generated snippet assumes gittensory-mcp is on your PATH (install it globally first, per Quickstart) — pass --command /absolute/path/to/gittensory-mcp if your client doesn't inherit your shell PATH.
Codex (OpenAI)
[mcp_servers.gittensory]
command = "gittensory-mcp"
args = ["--stdio"]Claude Desktop
{
"mcpServers": {
"gittensory": {
"command": "gittensory-mcp",
"args": ["--stdio"]
}
}
}Cursor
{
"mcpServers": {
"gittensory": {
"command": "gittensory-mcp",
"args": ["--stdio"]
}
}
}VS Code
VS Code's native MCP support uses a servers map with an explicit transport type instead of the mcpServers shape the other JSON hosts use:
{
"servers": {
"gittensory": {
"type": "stdio",
"command": "gittensory-mcp",
"args": ["--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/mcphttp--stdio is the default recommendation. It keeps auth + analysis on your machine and is the easiest path to log into with GitHub Device Flow.