How Good It Can Get

How Good It Can Get Clarity OS MCP API

The Clarity OS MCP API from How Good It Can Get — 1 operation(s) for clarity os mcp.

Documentation GitHub OpenAPI

Operations 1

POST /mcp Call the Clarity OS MCP server #

Specifications

⚙

OpenAPI

https://artifacts.apis.io/howgooditcanget-com/openapi/howgooditcanget-com-clarity-os-mcp-api-openapi.yml

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/howgooditcanget-com:howgooditcanget-com-clarity-os-mcp-api"

All apis

curl "https://apis.io/api/v1/apis?limit=25"

Calls without X-API-Key need no key. Calls with it need a paid plan — get a key.

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.

GitHub Google LinkedIn

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

OpenAPI Specification

openapi: 3.2.0
info:
  title: How Good It Can Get™ Clarity OS Clarity OS MCP API
  version: 1.0.0
  description: Public interface for How Good It Can Get™ Clarity OS™, a governed, provider-independent, nonclinical clarity system. Ordinary Clarity OS execution is available without payment. Protected resources, premium archives, licensed assets, and bulk knowledge products remain separately entitlement- or payment-governed.
  license:
    name: Proprietary
    identifier: LicenseRef-Proprietary
servers:
- url: https://ai.howgooditcanget.com
tags:
- name: Clarity OS MCP
paths:
  /mcp:
    post:
      operationId: callClarityOsMcp
      summary: Call the Clarity OS MCP server
      description: Accepts MCP JSON-RPC 2.0 requests, including initialize, tools/list, and tools/call. Ordinary clarity_os execution is available without payment.
      security: []
      tags:
      - Clarity OS MCP
      requestBody:
        required: true
        content:
          application/json:
            schema:
              type: object
              additionalProperties: true
              required:
              - jsonrpc
              - method
              properties:
                jsonrpc:
                  type: string
                  const: '2.0'
                id:
                  oneOf:
                  - type: integer
                  - type: string
                  - type: 'null'
                method:
                  type: string
                  enum:
                  - initialize
                  - tools/list
                  - tools/call
                  - resources/list
                  - resources/read
                  - prompts/list
                  - prompts/get
                params:
                  type: object
                  additionalProperties: true
            examples:
              listTools:
                summary: List available MCP tools
                value:
                  jsonrpc: '2.0'
                  id: 1
                  method: tools/list
                  params: {}
              callClarityOs:
                summary: Request governed clarity support
                value:
                  jsonrpc: '2.0'
                  id: 2
                  method: tools/call
                  params:
                    name: clarity_os
                    arguments:
                      user_text: I keep replaying a difficult conversation and cannot tell whether I am solving anything or just looping.
                      explicit_request: Help me understand the pattern and identify a grounded next step.
      responses:
        '200':
          description: MCP JSON-RPC result or protocol-level error.
        '400':
          description: Malformed HTTP or JSON request.
components:
  securitySchemes:
    x402Payment:
      type: apiKey
      in: header
      name: PAYMENT-SIGNATURE
      description: Canonical x402 V2 payment signature for separately governed paid resources.
    x402LegacyPayment:
      type: apiKey
      in: header
      name: X-Payment
      description: Legacy x402 compatibility header. New integrations should use PAYMENT-SIGNATURE.