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

# The MCP endpoint (streamable HTTP, JSON only)

> MCP over JSON-RPC: ``initialize``, ``ping``, ``tools/list``,
``tools/call``, ``resources/list``, ``resources/read``,
``prompts/list``. The cases and the tool registry as a partner's
orchestrator sees them - reads, previews and proposals; approvals and
executions stay in the inbox with the people the policy names.



## OpenAPI

````yaml /setup/internal-openapi.json post /v1/process/mcp
openapi: 3.1.0
info:
  title: n:lead Scheduling Bridge — Internal API
  version: 0.4.0
  description: >-
    Internal API of the n:lead scheduling bridge: the process endpoints that
    drive the day-ahead pipeline (aggregate, publish the open position, submit
    schedules, generate forecasts, orchestrate), the operator console endpoints,
    and the read-only operator-app endpoints under /v1/mobile. The process and
    console endpoints require the process API key, /v1/mobile a device key of
    the mobile scope; not for customer use.
servers:
  - url: https://{host}
    description: Deployed service
    variables:
      host:
        default: api.energy.nlead.ch
        description: >-
          The service hostname - n:lead provides it (see the Base URL on the API
          introduction page)
  - url: http://localhost:8000
    description: Local development
security: []
paths:
  /v1/process/mcp:
    post:
      summary: The MCP endpoint (streamable HTTP, JSON only)
      description: |-
        MCP over JSON-RPC: ``initialize``, ``ping``, ``tools/list``,
        ``tools/call``, ``resources/list``, ``resources/read``,
        ``prompts/list``. The cases and the tool registry as a partner's
        orchestrator sees them - reads, previews and proposals; approvals and
        executions stay in the inbox with the people the policy names.
      operationId: mcp_post_v1_process_mcp_post
      responses:
        '200':
          description: Successful Response
          content:
            application/json:
              schema: {}
      security:
        - APIKeyHeader: []
        - HTTPBearer: []
components:
  securitySchemes:
    APIKeyHeader:
      type: apiKey
      in: header
      name: X-API-Key
    HTTPBearer:
      type: http
      description: OIDC access token (Auth0 M2M)
      scheme: bearer

````

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