MCP Server

GitMyABI provides one general MCP (Model Context Protocol) server for AI tools and MCP-compatible clients. Connect any MCP client with a GitMyABI API key to give your agent access to projects, builds, ABIs, and generated TypeScript bindings.

Requirements

• A GitMyABI API key (prefixed gma_sk_).
• The MCP endpoint URL: https://api.gitmyabi.com/mcp for production, or https://api.staging.gitmyabi.com/mcp for staging only.
• An MCP-compatible client (VS Code, Cursor, Kiro, Claude Code, Codex, …).

Quick install

Click a button below to open your editor and add the GitMyABI MCP server. Replace the placeholder API key with your own gma_sk_ key after installation.

IDE setup (manual)

If the quick-install buttons above did not work, or you prefer to configure the server manually, follow the steps below. In every config block, replace gma_sk_REPLACE_ME with your own GitMyABI API key.

VS Code

VS Code MCP setup depends on the MCP configuration support available in your VS Code version or the MCP extension you use. Add GitMyABI as an HTTP MCP server with the production endpoint and x-api-key header.

1. Open your VS Code MCP server configuration or MCP extension settings.
2. Add a new HTTP MCP server named gitmyabi.
3. Use the production MCP URL shown below.
4. Add your GitMyABI API key in the x-api-key header.
5. Save the config and reload the MCP client if required.

{
  "name": "gitmyabi",
  "type": "http",
  "url": "https://api.gitmyabi.com/mcp",
  "headers": {
    "x-api-key": "gma_sk_REPLACE_ME"
  }
}

Cursor

Add GitMyABI as an HTTP MCP server in Cursor's MCP settings. Use the MCP endpoint URL and pass your API key through the x-api-key header.

1. Open Cursor settings.
2. Go to MCP or MCP servers.
3. Add a new server named gitmyabi.
4. Choose HTTP transport if prompted.
5. Paste the config below or enter the same values manually.
6. Reload Cursor or restart the agent session if required.

{
  "type": "http",
  "url": "https://api.gitmyabi.com/mcp",
  "headers": {
    "x-api-key": "gma_sk_REPLACE_ME"
  }
}

Kiro

Add GitMyABI as an MCP server in Kiro using the production MCP URL and x-api-key header.

1. Open Kiro MCP settings.
2. Add a new MCP server named gitmyabi.
3. Use the production MCP URL shown below.
4. Add your API key in the x-api-key header.
5. Keep the server enabled.

{
  "url": "https://api.gitmyabi.com/mcp",
  "headers": {
    "x-api-key": "gma_sk_REPLACE_ME"
  },
  "disabled": false,
  "autoApprove": []
}

Agent / CLI setup

Claude Code and Codex are coding agents and CLI-based tools, not IDEs. Their exact GitMyABI MCP setup commands are not yet confirmed. If your client supports HTTP MCP server config, use the manual config in the next section.

Claude Code

Exact Claude Code setup command pending confirmation. Until then, use the manual MCP HTTP config below if your Claude Code setup supports HTTP MCP servers.

Codex

Exact Codex setup command pending confirmation. Until then, use the manual MCP HTTP config below if your Codex setup supports HTTP MCP servers.

Manual configuration

If your MCP client is not listed above, or you prefer a generic config, use the HTTP MCP server config below. Replace gma_sk_REPLACE_ME with your own GitMyABI API key.

{
  "type": "http",
  "url": "https://api.gitmyabi.com/mcp",
  "headers": {
    "x-api-key": "gma_sk_REPLACE_ME"
  }
}

For staging, swap the URL with https://api.staging.gitmyabi.com/mcp. The endpoint speaks JSON-RPC 2.0 over HTTP at POST /mcp, with a companion SSE stream at GET /mcp/sse.

The recommended auth header is x-api-key. The server also accepts Authorization: Bearer <key> as an alternative.

Security

• Replace gma_sk_REPLACE_ME with your own GitMyABI API key.
• Do not commit API keys to source control.
• Treat copied MCP configs as sensitive — they contain your API key.
• If your client stores MCP config in a local file, make sure that file is not checked into a repository.
• The logged-in GitMyABI app may later provide a safer setup flow.

Available tools

Once connected, the MCP server exposes tools for projects, builds, ABIs, teams, and npm packages. Tool calls act on behalf of the user that owns the API key.

For real-time build updates, prefer the SSE flow: call create_sse_api_key to mint a scoped key, then connect to the stream_url returned by rebuild_project or watch_build.