Connect Gitxen to your AI

Gitxen runs a remote MCP server so Claude Code, Cursor, VS Code Copilot, Codex, Zed and any Model Context Protocol client can read your code, search repos, and manage issues and pull requests — using your own access token. Nothing is installed; it's one URL.

MCP endpoint

https://gitxen.com/api/mcp

Access token

Create one under Settings → Access tokens with repo:read (add repo:write to open issues/PRs). Pasting it here only fills the examples below — it never leaves your browser.

Claude Code

Run this in your terminal (or add it to a project's .mcp.json).

claude mcp add --transport http gitxen https://gitxen.com/api/mcp \
  --header "Authorization: Bearer akp_YOUR_TOKEN"

Cursor · Windsurf · Claude Desktop

Add to mcp.json (Cursor: ~/.cursor/mcp.json or .cursor/mcp.json in the repo).

{
  "mcpServers": {
    "gitxen": {
      "url": "https://gitxen.com/api/mcp",
      "headers": {
        "Authorization": "Bearer akp_YOUR_TOKEN"
      }
    }
  }
}

VS Code (Copilot)

Add to .vscode/mcp.json in your workspace, then Start the server.

{
  "servers": {
    "gitxen": {
      "type": "http",
      "url": "https://gitxen.com/api/mcp",
      "headers": {
        "Authorization": "Bearer akp_YOUR_TOKEN"
      }
    }
  }
}

Tools your AI gets

Every call is scoped to what your token can see — private repos stay private, and writes need the repo:write scope.

whoami— who your token belongs to

list_repos— repositories you can access

get_repo— repository metadata

list_files— browse a directory at a ref

read_file— read a file's contents

search_code— search code in a repo

list_branches— a repo's branches

list_commits— recent commits

get_commit— a commit's files + diff

list_issues— issues in a repo

get_issue— one issue + comments

create_issue— open an issue (repo:write)

comment_issue— comment on an issue (repo:write)

list_pull_requests— pull requests

get_pull_request— one pull request