openapi: 3.1.0
info:
  title: TinyCommand MCP Server 9 articles Drive your Tiny Command workspace from Claude Desktop, Cur API
  version: '2026-10-19'
  description: 'GENERATED FROM DOCUMENTATION by API Evangelist on 2026-10-19: 3 operation(s) read from 2 public documentation page(s) (each operation
    names its page in x-source). This is not the provider''s published contract; TinyCommand has published no machine-readable contract that the
    pipeline could find. Engine: local.'
  x-evidence-tiers:
    code-example: 5
    documentation: 16
    pages-with-code: 6
    pages-read: 8
  x-generated-from: documentation
  x-provenance: generated
  x-authored-by: API Evangelist
  x-generated: '2026-10-19'
  x-generator: generate-contract-from-docs.py
  x-engine: local
  x-sources:
  - https://tinycommand.com/docs/mcp/authentication
  - https://tinycommand.com/docs/mcp/getting-started
  x-docs-section: mcp
servers:
- url: https://mcp.tinycommand.com
paths:
  /.well-known/oauth-protected-resource:
    get:
      operationId: get_well_known_oauth_protected_resource
      tags:
      - API
      summary: GET /.well-known/oauth-protected-resource returns Protected Resource Metadata.
      x-source: https://tinycommand.com/docs/mcp/authentication
      responses:
        '200':
          description: Success (status as documented)
      x-evidence:
        kind: documentation
  /v1:
    post:
      operationId: post_v1
      tags:
      - Api
      summary: POST /v1
      x-source: https://tinycommand.com/docs/mcp/authentication
      responses:
        '201':
          description: Success (status as documented)
      x-evidence:
        kind: code-example
        language: http
        snippet: " POST /v1 HTTP/1.1\nHost: mcp.tinycommand.com\nAuthorization: Bearer tcm_live_aB3xK9mPqRv7...\nMCP-Protocol-Version: 2025-06-18\n\
          \ Copy \n The MCP-Protocol-Version header is required on every request after initialization; the host sets it automatically. The server\
          \ validates the key, resolves your identity and workspace, and runs each tool as you, applying the same per-asset permissions you have\
          \ in the w"
  /v1/health:
    get:
      operationId: get_v1_health
      tags:
      - Health
      summary: GET /v1/health
      x-source: https://tinycommand.com/docs/mcp/getting-started
      responses:
        '200':
          description: Success (status as documented)
      x-evidence:
        kind: code-example
        language: curl
        snippet: "curl https://mcp.tinycommand.com/v1/health\n Copy \n { \"status\": \"ok\", \"protocol_version\": \"2025-06-18\", \"build\":\
          \ \"...\" }\n Copy \n Tip If your host shows the Tiny Command tools but calls fail with an auth error, regenerate the key; the secret\
          \ is only shown once and a mistyped paste is the most common cause. \n Next steps \n Authentication & scopes : choose the right permissions\
          \ for each key. \n Tool ref"
security:
- bearer: []
components:
  securitySchemes:
    bearer:
      type: http
      scheme: bearer
tags:
- name: API
- name: Api
- name: Health