> ## Documentation Index
> Fetch the complete documentation index at: https://docs.nasiko.com/llms.txt
> Use this file to discover all available pages before exploring further.

# MCP JSON-RPC gateway

> Agent-facing MCP gateway. Generic JSON-RPC 2.0 `tools/list` and `tools/call`; request and response bodies are protocol-defined, so they're documented as free-form objects.

Authorization:
1. Missing, unknown, or revoked bearer token → `401`.
2. `tools/list`, `initialize`, and `ping` are allowed with the agent's identity alone.
3. `tools/call` without a `traceparent` for a live flow → `403`, except for a local coding agent bound with `nasiko connect`, whose calls run as its owner.
4. `tools/call` from an agent that isn't part of the flow → `403`.
5. If identity can't be checked, the call is refused with `403`.



## OpenAPI

````yaml /api-reference/openapi.json post /api/mcp
openapi: 3.1.0
info:
  title: Nasiko API
  description: >-
    HTTP API for the Nasiko OpenRuntime: agents, coding harnesses, TokenOps,
    routing, MCP, and secrets. Spec is generated from annotated routes; some
    surfaces are documented on the hand-written pages alongside this file.
  license:
    name: ''
  version: 0.1.0
servers:
  - url: https://free.app.nasiko.com
    description: Nasiko Cloud Free
  - url: https://{workspace}.app.nasiko.com
    description: Nasiko Cloud paid workspace
    variables:
      workspace:
        default: your-workspace
        description: >-
          Your workspace's subdomain, as shown in the connect command on the
          dashboard's Nasiko CLI page
security:
  - bearer_auth: []
tags:
  - name: secrets
    description: Encrypted per-user agent secrets
  - name: catalog
    description: >-
      Agent catalog: registration, discovery, versions, per-agent secrets, and
      source import
  - name: agents
    description: >-
      Agent lifecycle: deployments, LLM routing config, update/rollback,
      upload-and-deploy
  - name: orchestrator
    description: >-
      A2A dispatch: routing-engine/ReAct orchestrator and direct agent chat,
      plus routing stats
  - name: users
    description: >-
      User management: CRUD, roles, credentials, accessible agents
      (superuser-only)
  - name: usage
    description: Per-user token usage and cost reporting
  - name: observability
    description: Sessions, traces, spans, agent logs, and FinOps reporting
  - name: llm-router
    description: LLM routing presets, provider/model catalog, and tier→model registry
  - name: context-selection
    description: >-
      Per-user chat-history selection preferences: strategy, PACMS budget tier,
      the on/off switch, a dry-run preview, and settings-change history
  - name: coding-agents
    description: >-
      The progress local clients report while they bring in the caller's coding
      agents
  - name: settings
    description: >-
      Workspace-wide settings, including the Optimization tiers a user's PACMS
      budget level resolves against
  - name: mcp
    description: >-
      MCP gateway: agent-facing JSON-RPC tool calls, connector
      registration/upload/sharing, credentials & OAuth, and per-agent tool
      permissions
paths:
  /api/mcp:
    post:
      tags:
        - mcp
      summary: MCP JSON-RPC gateway
      description: >-
        Agent-facing MCP gateway. Generic JSON-RPC 2.0 `tools/list` and
        `tools/call`; request and response bodies are protocol-defined, so
        they're documented as free-form objects.


        Authorization:

        1. Missing, unknown, or revoked bearer token → `401`.

        2. `tools/list`, `initialize`, and `ping` are allowed with the agent's
        identity alone.

        3. `tools/call` without a `traceparent` for a live flow → `403`, except
        for a local coding agent bound with `nasiko connect`, whose calls run as
        its owner.

        4. `tools/call` from an agent that isn't part of the flow → `403`.

        5. If identity can't be checked, the call is refused with `403`.
      operationId: mcp_gateway
      parameters:
        - name: Authorization
          in: header
          description: >-
            `Bearer <MCP_GATEWAY_TOKEN>` — the per-agent gateway credential
            injected into the container env at deploy time
          required: true
          schema:
            type: string
        - name: traceparent
          in: header
          description: >-
            W3C trace context naming the flow this call belongs to. Required for
            `tools/call`, except for a local coding agent bound with `nasiko
            connect`, whose calls run as its owner.
          required: false
          schema:
            type:
              - string
              - 'null'
        - name: MCP-Protocol-Version
          in: header
          description: >-
            Negotiated MCP protocol version; an unsupported value is rejected
            with 400 on implemented methods
          required: false
          schema:
            type:
              - string
              - 'null'
      requestBody:
        description: 'JSON-RPC 2.0 request: `tools/list` or `tools/call`'
        content:
          application/json:
            schema:
              type: object
        required: true
      responses:
        '200':
          description: JSON-RPC 2.0 response (result or error object)
          content:
            application/json:
              schema:
                type: object
        '202':
          description: Notification accepted (no `id` in request); empty object body
          content:
            application/json:
              schema:
                type: object
        '400':
          description: >-
            Unsupported or undecodable `MCP-Protocol-Version` on a method this
            gateway implements
        '401':
          description: Missing/unknown/revoked gateway token
        '403':
          description: >-
            `tools/call` outside a live flow the agent takes part in (except a
            local coding agent bound with `nasiko connect`, whose calls run as
            its owner), or identity couldn't be checked.
        '413':
          description: Request body over the configured `MCP_GATEWAY_MAX_BODY_BYTES` limit
components:
  securitySchemes:
    bearer_auth:
      type: http
      scheme: bearer
      bearerFormat: JWT
      description: >-
        Session JWT. After `nasiko auth login`, print it with `jq -r
        '.clusters[.active].token' ~/.nasiko/config.json`. API keys aren't
        supported.

````

This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.