CoreStory MCP Protocol API

The mcp_protocol API from CoreStory — 3 operation(s) for mcp_protocol.

Operations 4

GET /mcp/ MCP SSE stream #
GET /mcp/{org} MCP SSE stream (per-org) #
POST /mcp/{org} MCP JSON-RPC endpoint (per-org) #
POST /mcp MCP JSON-RPC endpoint #

Work with this as data

Every API here is available over the APIs.io API and to AI agents over MCP.

MCP server

One button, every client — Claude, Cursor, VS Code and the rest.

https://apis.io/mcp

Tools for apis

7 MCP tools reach this
  • find_apisBrowse and filter every API in the catalog.
  • get_api_artifactsOne API's artifacts, grouped by type.
  • get_openapiThe primary OpenAPI for this API.
  • find_similar_apisAPIs that look like this one.
  • apis_io_searchSTART HERE — APIs, providers and tags for one query, each with its total.
  • resolveTurn a domain, URL or GitHub org into the provider it belongs to.
  • find_cohortsEvery scored population of providers in the catalog.
All 92 tools →

Call it yourself

curl for this page
This API
curl "https://apis.io/api/v1/apis/corestory-mcp-protocol-api"
All apis
curl "https://apis.io/api/v1/apis?limit=25"

Discovery needs no key. Ratings and market analysis are Pro.

Get an API key

Free tier, no form to fill in. Signing in shares your email address with us — we store it to create your key and to recognise you if you sign in with another provider. See our Privacy Policy and Terms.

A second provider on the same verified email joins the account you already have.

OpenAPI Specification

corestory-mcp-protocol-api-openapi.yml Raw ↑
openapi: 3.2.0
info:
  title: Crowdbotics API Documentation MCP Protocol API
  description: '# CoreStory API Overview


    The CoreStory API provides programmatic access to structured insights derived from software source code.'
  version: 1.26.2
servers:
- url: /
  description: Current server
security:
- BearerAuth: []
tags:
- name: MCP Protocol
paths:
  /mcp/:
    get:
      tags:
      - MCP Protocol
      summary: MCP SSE stream
      description: 'MCP SSE (Server-Sent Events) Stream Endpoint


        Opens an SSE stream for server-to-client communication.

        MCP Spec Requirement: GET /mcp MUST return either:

        - text/event-stream (SSE) for streaming server notifications, OR

        - HTTP 405 Method Not Allowed


        This implementation returns SSE for spec compliance.'
      operationId: mcp_sse_stream
      responses:
        '200':
          description: Successful Response
          content:
            application/json:
              schema: {}
        default:
          description: Error
          content:
            application/json:
              schema:
                $ref: '#/components/schemas/ErrorSchema'
  /mcp/{org}:
    get:
      tags:
      - MCP Protocol
      summary: MCP SSE stream (per-org)
      description: 'Per-org SSE stream — the ``GET`` counterpart of ``POST /mcp/{org}``.


        The org segment pins the organization for the JSON-RPC ``POST``; the GET

        stream itself only carries server notifications, so it behaves identically

        to the bare ``GET /mcp`` stream.'
      operationId: mcp_sse_stream_for_org
      parameters:
      - name: org
        in: path
        required: true
        schema:
          type: string
          title: Org
      responses:
        '200':
          description: Successful Response
          content:
            application/json:
              schema: {}
        default:
          description: Error
          content:
            application/json:
              schema:
                $ref: '#/components/schemas/ErrorSchema'
    post:
      tags:
      - MCP Protocol
      summary: MCP JSON-RPC endpoint (per-org)
      description: 'Per-org MCP JSON-RPC endpoint.


        The ``{org}`` path segment (a Clerk org id or slug) pins which organization a

        Clerk OAuth/session request acts under, taking precedence over the

        ``X-Corestory-Org`` header and the token''s ``org_id``. Non-membership is a 403

        authorization decision inside ``resolve_mcp_auth``, which the MCP surface

        surfaces as a JSON-RPC error over HTTP 200 (not a literal HTTP 403). On the

        ``csk_`` API-key path the org is fixed by the key, so the segment is ignored

        there.'
      operationId: mcp_jsonrpc_for_org
      parameters:
      - name: org
        in: path
        required: true
        schema:
          type: string
          title: Org
      responses:
        '200':
          description: Successful Response
          content:
            application/json:
              schema: {}
        default:
          description: Error
          content:
            application/json:
              schema:
                $ref: '#/components/schemas/ErrorSchema'
  /mcp:
    post:
      tags:
      - MCP Protocol
      summary: MCP JSON-RPC endpoint
      description: 'Bare MCP JSON-RPC endpoint.


        The acting organization is resolved from the request: an ``X-Corestory-Org``

        header, a session token''s ``org_id``, or membership-based auto-resolution.

        Use ``POST /mcp/{org}`` to pin it via the URL instead.'
      operationId: mcp_jsonrpc
      responses:
        '200':
          description: Successful Response
          content:
            application/json:
              schema: {}
        default:
          description: Error
          content:
            application/json:
              schema:
                $ref: '#/components/schemas/ErrorSchema'
components:
  schemas:
    ErrorBody:
      properties:
        message:
          type: string
          title: Message
        type:
          type: string
          title: Type
        details:
          additionalProperties: true
          type: object
          title: Details
          description: Optional extra context for the error.
      type: object
      required:
      - message
      - type
      title: ErrorBody
    ErrorSchema:
      properties:
        error:
          $ref: '#/components/schemas/ErrorBody'
      type: object
      required:
      - error
      title: ErrorSchema
  securitySchemes:
    BearerAuth:
      type: http
      scheme: bearer
      bearerFormat: JWT
      description: Enter the Bearer token from Clerk authentication
x-tagGroups:
- name: Ingest Your Codebase
  tags:
  - vector_store
  - projects
  - pre_ingestion
  - reingestion
- name: Generate Code Intelligence
  tags:
  - documents
  - document_generation
  - document_formatters
  - prd
  - prd_version
  - tech_spec
  - quality_metrics
  - sample_projects
- name: Query Your Codebase
  tags:
  - conversations
  - workflows
  - discovery
  - context
  - artifacts
- name: Manage and Inspect Intelligence
  tags:
  - api_debugging
  - events
  - version
  - files
  - cache
  - token_tracking
- name: Authenticate and Manage Access
  tags:
  - clerk_authentication
  - github_webhooks
  - github_integration
  - organizations
  - api_key_management
  - mcp_token_management
  - user
- name: (Advanced) Prompt Tuning
  tags:
  - prompts
- name: MCP Protocol
  tags:
  - mcp_protocol
- name: Administration
  tags:
  - admin