Integration boundary

MCP for tools. A versioned model API for agents.

GitGecko exposes two real integration surfaces: a Streamable HTTP MCP gateway for installed tools and an authenticated model API for Chat Completions, Responses, and Anthropic Messages. The dashboard and repository-management APIs remain separate control-plane surfaces.

MCP gateway

Compose exposes MCP at the loopback gateway http://127.0.0.1:3141/mcp. The gateway advertises installed tools and maps mutating behavior into MCP annotations. A public host route requires an authenticated ingress you operate; it is not included in the default Compose topology.

{
  "transport": "streamable-http",
  "endpoint": "http://127.0.0.1:3141/mcp"
}

Versioned model API

After gitgecko login, send the device token to the same cloud origin. The edge accepts the standard Anthropic x-api-key header and normalizes it to the platform bearer contract; OpenAI-compatible clients use Authorization: Bearer directly.

POST /v1/chat/completions
POST /v1/responses
POST /v1/messages
GET  /v1/models

Authorization: Bearer <device-token>
// Anthropic SDKs may send: x-api-key: <device-token>

Hosted model aliases and monthly credits are resolved server-side. Provider hosts, private model IDs, and credentials never cross the public response boundary.

Read the roadmap for additional control-plane surfaces