Browse documentation
← API reference

API descriptions

Call the remote MCP server

POST /mcp

Send one JSON-RPC message. Initialize, discovery and the tool list work signed out; the first tool call challenges for a sign-in. Connected apps use OAuth access tokens bound to this resource. Personal tokens, agent tokens and check-only keys retain their API rights. The server returns JSON without sessions or SSE. Protocol errors use JSON-RPC; authentication and rate-limit errors use problem JSON. Supported protocol versions are 2026-07-28, 2025-11-25 and 2025-06-18. A browser origin must match this server; cookies are not used.

Example request

curl --request POST 'https://commitscale.com/mcp' \
  --header 'Content-Type: application/json' \
  --data '{}'

Example values illustrate the format. Use your own credentials and identifiers.

Request body

application/json

Responses

200 A JSON-RPC result or error.

application/json

{
  "id": 1,
  "jsonrpc": "2.0",
  "result": {
    "tools": []
  }
}

202 A notification was accepted.

RateLimit and RateLimit-Policy describe the request rate. Follow Retry-After when a response asks you to wait.

Problem responses

Errors use application/problem+json. Act on the stable code, and follow next when present. See the problem format.

unauthenticated401

The request carried no credentials.

Use this operation's sign-in method. Bearer credentials use Authorization: Bearer <token>; browser credentials use the session cookie.

invalid_token401

The token is unknown, expired, or revoked, its agent was revoked, or an OAuth token was used outside its MCP resource.

Stop using it. Sign in again, or ask the owner to create a replacement agent key.

forbidden403

The caller may not do this: only people may, only owners may, or the agent was not given this repository or write access.

Stop. Retrying will not help. Ask the owner for the access, or leave the step to a person.

quota_exceeded429

With 429, the caller used its requests for the minute. With 422, a count limit was reached.

With 429, wait Retry-After seconds and retry. With 422, remove one first.

internal500

The server failed, and logged why.

Retry after Retry-After seconds. A write is safe to retry with the same idempotency key.