generated: '2026-08-13'
method: derived
source: openapi/_original/openapi.json + mcp/convertkit-mcp.yml + https://developers.kit.com/mcp/kit-mcp
note: 'Kit''s OpenAPI declares no operationIds on any of its 72 operations, so REST operations are bound
  here by METHOD + path — the only stable identifiers the spec actually publishes. The Kit MCP (app.kit.com/mcp)
  is OAuth-gated, so its tool names could not be introspected; Kit''s own documentation states the server
  is a one-to-one mapping of the v4 API surface ("every endpoint in the API reference is exposed as an
  MCP tool"). That claim is recorded as the binding with confidence: medium, per-capability, rather than
  inventing tool names.'
surfaces:
  openapi:
    files: 14
    source: openapi/_original/openapi.json
    operations: 72
    operation_ids_declared: 0
    gated: false
  graphql:
    endpoint: null
    artifact: graphql/convertkit-schema.graphql
    gated: null
    note: Kit publishes no GraphQL endpoint. The graphql/ artifact in this repo is an API Evangelist conceptual
      schema over the REST API, not a Kit surface — it is excluded from this crosswalk.
  mcp:
  - name: Kit MCP
    url: https://app.kit.com/mcp
    auth: oauth
    tools_list_gated: true
    note: 401 Bearer token required on anonymous tools/list (probed 2026-08-13).
  - name: Kit Developer Docs MCP
    url: https://developers.kit.com/mcp
    auth: none
    tools_list_gated: false
    tools: 3
    note: Anonymous tools/list returned 200 with 3 tools and full inputSchemas — saved to mcp/convertkit-docs-mcp-tools.json.
crosswalk:
- tool: null
  tool_family: Accounts
  category: Accounts
  server: Kit MCP (https://app.kit.com/mcp)
  rest:
  - GET /v4/account
  - GET /v4/account/colors
  - PUT /v4/account/colors
  - GET /v4/account/creator_profile
  - GET /v4/account/email_stats
  - GET /v4/account/growth_stats
  specs:
  - convertkit-accounts-api-openapi.yml
  binding: rest
  confidence: medium
  note: 6 REST operation(s) under the Accounts capability. Kit documents the MCP server as a 1:1 projection
    of the v4 API, so each of these is expected to have a backing tool; the tool NAMES are not published
    machine-readably and are deliberately left null rather than guessed. Each operation's parameters +
    requestBody in the linked spec is the real input contract.
- tool: null
  tool_family: Broadcasts
  category: Broadcasts
  server: Kit MCP (https://app.kit.com/mcp)
  rest:
  - GET /v4/broadcasts
  - POST /v4/broadcasts
  - GET /v4/broadcasts/stats
  - GET /v4/broadcasts/{broadcast_id}/clicks
  - GET /v4/broadcasts/{broadcast_id}/stats
  - DELETE /v4/broadcasts/{id}
  - GET /v4/broadcasts/{id}
  - PUT /v4/broadcasts/{id}
  specs:
  - convertkit-broadcasts-api-openapi.yml
  binding: rest
  confidence: medium
  note: 8 REST operation(s) under the Broadcasts capability. Kit documents the MCP server as a 1:1 projection
    of the v4 API, so each of these is expected to have a backing tool; the tool NAMES are not published
    machine-readably and are deliberately left null rather than guessed. Each operation's parameters +
    requestBody in the linked spec is the real input contract.
- tool: null
  tool_family: Custom Fields
  category: Custom Fields
  server: Kit MCP (https://app.kit.com/mcp)
  rest:
  - POST /v4/bulk/custom_fields
  - POST /v4/bulk/custom_fields/subscribers
  - GET /v4/custom_fields
  - POST /v4/custom_fields
  - DELETE /v4/custom_fields/{id}
  - PUT /v4/custom_fields/{id}
  specs:
  - convertkit-custom-fields-api-openapi.yml
  binding: rest
  confidence: medium
  note: 6 REST operation(s) under the Custom Fields capability. Kit documents the MCP server as a 1:1
    projection of the v4 API, so each of these is expected to have a backing tool; the tool NAMES are
    not published machine-readably and are deliberately left null rather than guessed. Each operation's
    parameters + requestBody in the linked spec is the real input contract.
- tool: null
  tool_family: Forms
  category: Forms
  server: Kit MCP (https://app.kit.com/mcp)
  rest:
  - POST /v4/bulk/forms/subscribers
  - GET /v4/forms
  - GET /v4/forms/{form_id}/subscribers
  - POST /v4/forms/{form_id}/subscribers
  - POST /v4/forms/{form_id}/subscribers/{id}
  specs:
  - convertkit-forms-api-openapi.yml
  binding: rest
  confidence: medium
  note: 5 REST operation(s) under the Forms capability. Kit documents the MCP server as a 1:1 projection
    of the v4 API, so each of these is expected to have a backing tool; the tool NAMES are not published
    machine-readably and are deliberately left null rather than guessed. Each operation's parameters +
    requestBody in the linked spec is the real input contract.
- tool: null
  tool_family: Subscribers
  category: Subscribers
  server: Kit MCP (https://app.kit.com/mcp)
  rest:
  - POST /v4/bulk/subscribers
  - GET /v4/subscribers
  - POST /v4/subscribers
  - POST /v4/subscribers/filter
  - GET /v4/subscribers/{id}
  - PUT /v4/subscribers/{id}
  - POST /v4/subscribers/{id}/unsubscribe
  - GET /v4/subscribers/{subscriber_id}/stats
  - GET /v4/subscribers/{subscriber_id}/tags
  specs:
  - convertkit-subscribers-api-openapi.yml
  binding: rest
  confidence: medium
  note: 9 REST operation(s) under the Subscribers capability. Kit documents the MCP server as a 1:1 projection
    of the v4 API, so each of these is expected to have a backing tool; the tool NAMES are not published
    machine-readably and are deliberately left null rather than guessed. Each operation's parameters +
    requestBody in the linked spec is the real input contract.
- tool: null
  tool_family: Tags
  category: Tags
  server: Kit MCP (https://app.kit.com/mcp)
  rest:
  - POST /v4/bulk/tags
  - DELETE /v4/bulk/tags/subscribers
  - POST /v4/bulk/tags/subscribers
  - GET /v4/tags
  - POST /v4/tags
  - PUT /v4/tags/{id}
  - DELETE /v4/tags/{tag_id}/subscribers
  - GET /v4/tags/{tag_id}/subscribers
  - POST /v4/tags/{tag_id}/subscribers
  - DELETE /v4/tags/{tag_id}/subscribers/{id}
  - POST /v4/tags/{tag_id}/subscribers/{id}
  specs:
  - convertkit-tags-api-openapi.yml
  binding: rest
  confidence: medium
  note: 11 REST operation(s) under the Tags capability. Kit documents the MCP server as a 1:1 projection
    of the v4 API, so each of these is expected to have a backing tool; the tool NAMES are not published
    machine-readably and are deliberately left null rather than guessed. Each operation's parameters +
    requestBody in the linked spec is the real input contract.
- tool: null
  tool_family: Email Templates
  category: Email Templates
  server: Kit MCP (https://app.kit.com/mcp)
  rest:
  - GET /v4/email_templates
  specs:
  - convertkit-email-templates-api-openapi.yml
  binding: rest
  confidence: medium
  note: 1 REST operation(s) under the Email Templates capability. Kit documents the MCP server as a 1:1
    projection of the v4 API, so each of these is expected to have a backing tool; the tool NAMES are
    not published machine-readably and are deliberately left null rather than guessed. Each operation's
    parameters + requestBody in the linked spec is the real input contract.
- tool: null
  tool_family: Posts
  category: Posts
  server: Kit MCP (https://app.kit.com/mcp)
  rest:
  - GET /v4/posts
  - GET /v4/posts/{id}
  specs:
  - convertkit-posts-api-openapi.yml
  binding: rest
  confidence: medium
  note: 2 REST operation(s) under the Posts capability. Kit documents the MCP server as a 1:1 projection
    of the v4 API, so each of these is expected to have a backing tool; the tool NAMES are not published
    machine-readably and are deliberately left null rather than guessed. Each operation's parameters +
    requestBody in the linked spec is the real input contract.
- tool: null
  tool_family: Purchases
  category: Purchases
  server: Kit MCP (https://app.kit.com/mcp)
  rest:
  - GET /v4/purchases
  - POST /v4/purchases
  - GET /v4/purchases/{id}
  specs:
  - convertkit-purchases-api-openapi.yml
  binding: rest
  confidence: medium
  note: 3 REST operation(s) under the Purchases capability. Kit documents the MCP server as a 1:1 projection
    of the v4 API, so each of these is expected to have a backing tool; the tool NAMES are not published
    machine-readably and are deliberately left null rather than guessed. Each operation's parameters +
    requestBody in the linked spec is the real input contract.
- tool: null
  tool_family: Segments
  category: Segments
  server: Kit MCP (https://app.kit.com/mcp)
  rest:
  - GET /v4/segments
  specs:
  - convertkit-segments-api-openapi.yml
  binding: rest
  confidence: medium
  note: 1 REST operation(s) under the Segments capability. Kit documents the MCP server as a 1:1 projection
    of the v4 API, so each of these is expected to have a backing tool; the tool NAMES are not published
    machine-readably and are deliberately left null rather than guessed. Each operation's parameters +
    requestBody in the linked spec is the real input contract.
- tool: null
  tool_family: Sequences
  category: Sequences
  server: Kit MCP (https://app.kit.com/mcp)
  rest:
  - GET /v4/sequences
  - POST /v4/sequences
  - DELETE /v4/sequences/{id}
  - GET /v4/sequences/{id}
  - PUT /v4/sequences/{id}
  - GET /v4/sequences/{sequence_id}/subscribers
  - POST /v4/sequences/{sequence_id}/subscribers
  - POST /v4/sequences/{sequence_id}/subscribers/{id}
  specs:
  - convertkit-sequences-api-openapi.yml
  binding: rest
  confidence: medium
  note: 8 REST operation(s) under the Sequences capability. Kit documents the MCP server as a 1:1 projection
    of the v4 API, so each of these is expected to have a backing tool; the tool NAMES are not published
    machine-readably and are deliberately left null rather than guessed. Each operation's parameters +
    requestBody in the linked spec is the real input contract.
- tool: null
  tool_family: Sequence Emails
  category: Sequence Emails
  server: Kit MCP (https://app.kit.com/mcp)
  rest:
  - GET /v4/sequences/{sequence_id}/emails
  - POST /v4/sequences/{sequence_id}/emails
  - DELETE /v4/sequences/{sequence_id}/emails/{id}
  - GET /v4/sequences/{sequence_id}/emails/{id}
  - PUT /v4/sequences/{sequence_id}/emails/{id}
  specs:
  - convertkit-sequence-emails-api-openapi.yml
  binding: rest
  confidence: medium
  note: 5 REST operation(s) under the Sequence Emails capability. Kit documents the MCP server as a 1:1
    projection of the v4 API, so each of these is expected to have a backing tool; the tool NAMES are
    not published machine-readably and are deliberately left null rather than guessed. Each operation's
    parameters + requestBody in the linked spec is the real input contract.
- tool: null
  tool_family: Snippets
  category: Snippets
  server: Kit MCP (https://app.kit.com/mcp)
  rest:
  - GET /v4/snippets
  - POST /v4/snippets
  - GET /v4/snippets/{id}
  - PUT /v4/snippets/{id}
  specs:
  - convertkit-snippets-api-openapi.yml
  binding: rest
  confidence: medium
  note: 4 REST operation(s) under the Snippets capability. Kit documents the MCP server as a 1:1 projection
    of the v4 API, so each of these is expected to have a backing tool; the tool NAMES are not published
    machine-readably and are deliberately left null rather than guessed. Each operation's parameters +
    requestBody in the linked spec is the real input contract.
- tool: null
  tool_family: Webhooks
  category: Webhooks
  server: Kit MCP (https://app.kit.com/mcp)
  rest:
  - GET /v4/webhooks
  - POST /v4/webhooks
  - DELETE /v4/webhooks/{id}
  specs:
  - convertkit-webhooks-api-openapi.yml
  binding: rest
  confidence: medium
  note: 3 REST operation(s) under the Webhooks capability. Kit documents the MCP server as a 1:1 projection
    of the v4 API, so each of these is expected to have a backing tool; the tool NAMES are not published
    machine-readably and are deliberately left null rather than guessed. Each operation's parameters +
    requestBody in the linked spec is the real input contract.
mcp_only:
- tool: search_kit_developer_documentation
  server: Kit Developer Docs MCP (https://developers.kit.com/mcp)
  reason: Documentation-plane tool. Operates on published docs content, not on Kit account data — there
    is no REST equivalent in the v4 API.
  description: Full-text search over the Kit developer documentation knowledge base.
  read_only: true
  input_schema: mcp/convertkit-docs-mcp-tools.json
- tool: query_docs_filesystem_kit_developer_documentation
  server: Kit Developer Docs MCP (https://developers.kit.com/mcp)
  reason: Documentation-plane tool. Operates on published docs content, not on Kit account data — there
    is no REST equivalent in the v4 API.
  description: Read-only rg/grep/cat over a virtualized filesystem of the Kit docs pages and OpenAPI specs.
  read_only: true
  input_schema: mcp/convertkit-docs-mcp-tools.json
- tool: submit_feedback
  server: Kit Developer Docs MCP (https://developers.kit.com/mcp)
  reason: Documentation-plane tool. Operates on published docs content, not on Kit account data — there
    is no REST equivalent in the v4 API.
  description: Report an incorrect/outdated/confusing documentation page to the Kit docs team.
  read_only: false
  input_schema: mcp/convertkit-docs-mcp-tools.json
rest_only:
- capability: (none identified)
  reason: Kit states the MCP server covers the whole v4 surface. Because tools/list is gated, no REST
    operation can be positively shown to lack a tool — recorded as unknown rather than zero.
  operations: []
coverage:
  rest_operations_total: 72
  rest_operation_ids_declared: 0
  rest_capabilities: 14
  mcp_tools_named: 3
  mcp_tools_named_and_bound: 0
  mcp_only: 3
  mcp_tools_gated_unnamed: unknown (Kit MCP tools/list requires OAuth)
  note: Named-tool coverage is 3/3 for the anonymous docs server and 0 named for the gated account server.