slideforge-dev MCP API

openapi: 3.2.0
info:
  title: SlideForge MCP API
  description: 'Agent-first PowerPoint generation. Send structured slide intents (a `form` plus typed fields) or a brief; get back a real, editable `.pptx`. The draw path is deterministic — no model renders your slide, so supplied numbers and text come out verbatim. Every response carries `status`, `fidelity` and `warnings` so an automated caller can tell whether the output is usable. $0.05 per slide; an unusable slide is not billed. Authenticate with a SlideForge API key (`Authorization: Bearer sf_live_…` or `X-API-Key`) — new accounts include 60 free slides, no credit card: https://slideforge.dev/sign-up'
  version: 5.356.0
servers:
- url: https://api.slideforge.dev
security:
- bearerAuth: []
- apiKeyAuth: []
tags:
- name: MCP
paths:
  /v1/tools/{tool_name}:
    post:
      tags:
      - MCP
      summary: Rest Tool Dispatch
      description: 'REST alias over the MCP tool dispatch — same tools, same handlers, API-key auth.


        Exists so the local stdio MCP wrapper (smartdatabrokers/slideforge-mcp) forwards as a

        plain REST client, not an MCP proxy: the wrapper bakes the tool schemas in locally and

        POSTs each call''s `arguments` object here. Body shape == the MCP tool''s inputSchema.

        Returns the tool-result envelope (MCP content blocks). Cost events + wallet accounting

        flow exactly as the /mcp/ tools/call path — this reuses the same dispatch.'
      operationId: rest_tool_dispatch_v1_tools__tool_name__post
      parameters:
      - name: tool_name
        in: path
        required: true
        schema:
          type: string
          title: Tool Name
      responses:
        '200':
          description: Successful Response
          content:
            application/json:
              schema: {}
        '422':
          description: Validation Error
          content:
            application/json:
              schema:
                $ref: '#/components/schemas/HTTPValidationError'
  /_widget_debug:
    post:
      tags:
      - MCP
      summary: Widget Debug Ping
      description: 'No-auth debug ping for live ChatGPT widget diagnostics.


        Iframe runtime POSTs JSON state here; we log it. No auth on purpose —

        log-only, no side effects. Temporary debugging surface; remove after

        the ChatGPT widget render is stable.'
      operationId: widget_debug_ping__widget_debug_post
      responses:
        '200':
          description: Successful Response
          content:
            application/json:
              schema: {}
  /mcp/canonical/:
    post:
      tags:
      - MCP
      summary: Mcp Endpoint
      description: MCP Streamable HTTP endpoint — handles JSON-RPC 2.0 messages.
      operationId: mcp_endpoint_mcp_canonical__post
      responses:
        '200':
          description: Successful Response
          content:
            application/json:
              schema: {}
  /mcp/canonical:
    post:
      tags:
      - MCP
      summary: Mcp Endpoint
      description: MCP Streamable HTTP endpoint — handles JSON-RPC 2.0 messages.
      operationId: mcp_endpoint_mcp_canonical_post
      responses:
        '200':
          description: Successful Response
          content:
            application/json:
              schema: {}
  /mcp-connectors/:
    post:
      tags:
      - MCP
      summary: Mcp Endpoint
      description: MCP Streamable HTTP endpoint — handles JSON-RPC 2.0 messages.
      operationId: mcp_endpoint_mcp_connectors__post
      responses:
        '200':
          description: Successful Response
          content:
            application/json:
              schema: {}
  /mcp-connectors:
    post:
      tags:
      - MCP
      summary: Mcp Endpoint
      description: MCP Streamable HTTP endpoint — handles JSON-RPC 2.0 messages.
      operationId: mcp_endpoint_mcp_connectors_post
      responses:
        '200':
          description: Successful Response
          content:
            application/json:
              schema: {}
  /mcp/copilot/:
    post:
      tags:
      - MCP
      summary: Mcp Endpoint
      description: MCP Streamable HTTP endpoint — handles JSON-RPC 2.0 messages.
      operationId: mcp_endpoint_mcp_copilot__post
      responses:
        '200':
          description: Successful Response
          content:
            application/json:
              schema: {}
  /mcp/copilot:
    post:
      tags:
      - MCP
      summary: Mcp Endpoint
      description: MCP Streamable HTTP endpoint — handles JSON-RPC 2.0 messages.
      operationId: mcp_endpoint_mcp_copilot_post
      responses:
        '200':
          description: Successful Response
          content:
            application/json:
              schema: {}
  /mcp/openai/:
    post:
      tags:
      - MCP
      summary: Mcp Endpoint
      description: MCP Streamable HTTP endpoint — handles JSON-RPC 2.0 messages.
      operationId: mcp_endpoint_mcp_openai__post
      responses:
        '200':
          description: Successful Response
          content:
            application/json:
              schema: {}
  /mcp/openai:
    post:
      tags:
      - MCP
      summary: Mcp Endpoint
      description: MCP Streamable HTTP endpoint — handles JSON-RPC 2.0 messages.
      operationId: mcp_endpoint_mcp_openai_post
      responses:
        '200':
          description: Successful Response
          content:
            application/json:
              schema: {}
  /mcp:
    post:
      tags:
      - MCP
      summary: Mcp Endpoint
      description: MCP Streamable HTTP endpoint — handles JSON-RPC 2.0 messages.
      operationId: mcp_endpoint_mcp_post
      responses:
        '200':
          description: Successful Response
          content:
            application/json:
              schema: {}
  /mcp/:
    post:
      tags:
      - MCP
      summary: Mcp Endpoint
      description: MCP Streamable HTTP endpoint — handles JSON-RPC 2.0 messages.
      operationId: mcp_endpoint_mcp__post
      responses:
        '200':
          description: Successful Response
          content:
            application/json:
              schema: {}
components:
  schemas:
    HTTPValidationError:
      properties:
        detail:
          items:
            $ref: '#/components/schemas/ValidationError'
          type: array
          title: Detail
      type: object
      title: HTTPValidationError
    ValidationError:
      properties:
        loc:
          items:
            anyOf:
            - type: string
            - type: integer
          type: array
          title: Location
        msg:
          type: string
          title: Message
        type:
          type: string
          title: Error Type
      type: object
      required:
      - loc
      - msg
      - type
      title: ValidationError
  securitySchemes:
    bearerAuth:
      type: http
      scheme: bearer
      description: 'SlideForge API key: `Authorization: Bearer sf_live_…`. Create one at https://slideforge.dev/console/keys'
    apiKeyAuth:
      type: apiKey
      in: header
      name: X-API-Key
      description: Same key, header form — for clients that cannot set Authorization.