MCP Server
Connect MCP-compatible AI clients to GitMyABI.
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/mcpfor production, orhttps://api.staging.gitmyabi.com/mcpfor staging only. - An MCP-compatible client (VS Code, Cursor, Kiro, Claude Code, Codex, …).
IDE setup
The sections below show how to add GitMyABI as an HTTP MCP server in common IDE clients. 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.
- Open your VS Code MCP server configuration or MCP extension settings.
- Add a new HTTP MCP server named
gitmyabi. - Use the production MCP URL shown below.
- Add your GitMyABI API key in the
x-api-keyheader. - 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.
- Open Cursor settings.
- Go to MCP or MCP servers.
- Add a new server named
gitmyabi. - Choose HTTP transport if prompted.
- Paste the config below or enter the same values manually.
- 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.
- Open Kiro MCP settings.
- Add a new MCP server named
gitmyabi. - Use the production MCP URL shown below.
- Add your API key in the
x-api-keyheader. - 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_MEwith 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.
Projects
list_projects— List all projects owned by the authenticated user.get_project— Get project details by ID.create_project— Create a new project from a granted GitHub repo.update_project_settings— Update project settings.rebuild_project— Trigger a rebuild and get a stream URL for live updates.get_github_installations— List GitHub App installations and accessible repos.
Builds
list_builds— List builds for a project.get_build— Get build details by ID.get_build_status— Get current build status (lightweight check).get_build_logs— Get build logs.get_build_artifacts— List build artifacts.cancel_build— Cancel a running build.get_build_resource_tiers— List available build resource tiers.watch_build— Get an SSE stream URL to watch a build in real time.create_sse_api_key— Create a scoped API key valid only for the SSE streaming endpoint.
ABIs
get_project_abis— Get all ABIs for a project.get_build_abis— Get ABIs for a specific build.
Teams
list_teams— List all teams the authenticated user belongs to.get_team— Get team details by ID.
npm packages
get_npm_package_info— Get full npm package metadata from the registry, including private packages.check_npm_package_public— Check whether an npm package is public.get_project_npm_packages— Get all npm packages for a project with detailed registry metadata.
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.
Related
- Build with AI overview
Where GitMyABI fits into AI-assisted contract integration workflows.
- Skills
Reusable agent instructions for using GitMyABI correctly.
- Agent task recipes
Copyable, task-specific prompts for AI agents working with GitMyABI.
- For AI agents
When AI agents should and should not use GitMyABI, with required inputs and expected outputs.
- CLI overview
What the gma CLI does and when to use it.
- Generated contract bindings
TypeScript packages produced from contract ABIs for typed integration.