OpenAny

npx add-mcp 'https://mcp.openany.si/mcp'

OpenAny MCP

OpenAny (https://openany.si) is the marketplace for agents: one key for 168+ AI models and 3,200+ APIs. No subscriptions, no per-provider signups. Pay per call, no monthly fee. This repo is OpenAny's remote MCP server (Streamable HTTP).

Endpoint: https://mcp.openany.si/mcp

Transport: Streamable HTTP, not legacy SSE.

Operator: Alephant AI LLC.

Pricing: Pay per call, no subscription. Check the current resource price and billing unit before approving a paid call.

OpenAny provides model access and callable APIs under one API key, pay per call, no monthly fee. The supplied catalog snapshot is approximately 168+ models, 3,201 APIs and 3,220 MCP tools. These are approximate, changing catalog figures supplied for this documentation, not independently verified live counts or a guarantee that every model is exposed as an MCP tool. Use the current tools/list response and tool schemas to determine MCP availability. The separate model API base URL is https://api.openany.si/v1.

Configuration

Add this remote server in a client that accepts a top-level mcpServers object. The header is the confirmed authentication header, Authorization: Bearer <OPENANY_API_KEY>. ${OPENANY_API_KEY} is the environment placeholder for that key. Do not hardcode a key. Use one API key. Executing an API is pay per call, no monthly fee. tools/list is public and does not need a key.

{
  "mcpServers": {
    "openany": {
      "url": "https://mcp.openany.si/mcp-lite",
      "headers": {
        "Authorization": "Bearer ${OPENANY_API_KEY}"
      }
    }
  }
}

This block uses the lightweight endpoint. The client setup examples remain in place, including files that point at https://mcp.openany.si/mcp.

Tools

https://mcp.openany.si/mcp-lite exposes three tools. search_apis finds 168+ models and 3,200+ APIs. Execution is pay per call, no monthly fee, with one API key.

• search_apis: Find OpenAny models and APIs by keywords and optional kind (api, model, or all; default all), provider, category, data_platform, data_product or capability.
• get_api: Read one model or API selected from search_apis.
• run_api: Execute one selected OpenAny API, or send one selected model to chat completions, with the caller's current credentials.

https://mcp.openany.si/mcp exposes 3,268 tools across 45 providers, led by tikhub (1,009), anyapi (337), justoneapi (301), scrapecreators (193), and qcc (170). The list is in TOOLS.md.

Optional lightweight endpoint

When enabled and routed by the deployment, https://mcp.openany.si/mcp-lite uses the same Streamable HTTP transport and exposes just three tools: search_apis, get_api and run_api. One search covers the current model catalog and the API catalog. get_api reads the selected model or API. run_api executes an API through the gateway, or posts a model call to /v1/chat/completions on the model API origin, using the caller's key. Model ids, modalities, context length and pricing are taken from the live GET /v1/models response and are omitted when that response does not provide them. Pay per call, no monthly fee, one API key.

The implementation enables this interface by default; operators can disable it with MCP_LITE_ENABLED=false. Public deployment availability is a separate check. search_apis and get_api read metadata; run_api forwards a business request and may incur charges, requiring the caller's gateway credentials and spending authorization. Configure one endpoint, not both, unless your workflow explicitly needs both catalogs. See the lightweight guide. The examples and registry descriptor in this repository continue to use /mcp.

Authentication

• tools/list is public; discovery does not require an OpenAny API key.
• Resource execution through tools/call requires an OpenAny API key. The gateway remains responsible for authentication, billing and execution.
• No OAuth: this server does not implement an OAuth sign-in flow.
• Confirmed authentication header: Authorization: Bearer <OPENANY_API_KEY>. Supply an OpenAny API key through OPENANY_API_KEY; the examples use this confirmed header format.

The header format is confirmed by the maintainer for this documentation update. This is separate from validating a particular account, client version or business request. No new authenticated live call was performed during this update; see the verification record for test scope.

Provide the key through OPENANY_API_KEY in the client's private environment or secret settings. Never hardcode a key in the repository, paste it into an agent prompt, or include it in a URL, screenshot, log or support message. Ensure the client process can read that environment variable; a desktop app does not necessarily inherit a terminal's environment.

Client setup

Merge the appropriate snippet into existing settings rather than replacing unrelated servers. The files below contain environment references, not real keys. Every example uses the confirmed Bearer header format; none is a claim of an end-to-end paid test of every client.

Client	Example	Destination
Claude Code	claude-code.sh	Run from a private shell with OPENANY_API_KEY available
Cursor	cursor.mcp.json	~/.cursor/mcp.json
Codex	codex.config.toml	~/.codex/config.toml
Pi	pi.mcp.json	~/.pi/agent/mcp.json or .pi/mcp.json
Hermes	hermes.config.yaml	~/.hermes/config.yaml
OpenClaw	openclaw.json	~/.openclaw/openclaw.json, under mcp.servers
Other clients	generic.md	Client-specific remote MCP settings

The Hermes row is a manual mcp_servers example for the full /mcp endpoint. The installable plugin is plugins/openany. Its default is https://mcp.openany.si/mcp-lite, because Hermes 0.23.0 stops tools/list after 50 pages and the full endpoint is truncated at 2500 tools. A same-name openany server in config.yaml makes Hermes skip the plugin server. The owner-run session, the CoinGecko tool result, request 420decad-3a6b-46f8-acff-53966bbd8b1c, tool cost 0, and 807 microUSD of model calls are recorded in docs/hermes-e2e.md.

JSON does not support comments. The JSON examples use a top-level $comment annotation for the warning and CLI notes; only the mcpServers or mcp block is connection configuration. If your client rejects annotation fields, copy that configuration block without $comment, retaining the warning separately.

The requested Claude Code command expands the environment variable before invoking its CLI. The resulting header can be visible to local process inspection and may be stored in personal client configuration. Do not run it with shell tracing or commit the generated configuration. The Pi/OpenClaw CLI alternatives in annotations are alternatives, not additional commands to run as a batch. OpenClaw's CLI alternative sets the endpoint and transport only; the environment-backed header still needs to be merged from the JSON example.

Client reference documentation: Claude Code, Cursor, Codex, Pi, Hermes, OpenClaw. Client versions and configuration support can change; consult the matching client documentation if a field or command is rejected.

Gemini CLI

Install this repository as a Gemini CLI extension:

gemini extensions install https://github.com/openanysi/openany-mcp

gemini-extension.json names the extension openany. It connects with httpUrl to https://mcp.openany.si/mcp-lite and sends Authorization: Bearer ${OPENANY_API_KEY}. The key is the sensitive setting OPENANY_API_KEY. Gemini CLI asks for it during install and stores it outside this repository. GEMINI.md is the extension context file.

Cursor

.mcp.json is the root file cursor.directory reads for an MCP server. .cursor-plugin/plugin.json is the Cursor plugin manifest. It declares OPENANY_API_KEY as a required string variable and sets mcpServers to .mcp.json. The header in that file is Authorization: Bearer ${OPENANY_API_KEY}. Cursor fills the placeholder from the plugin setting. The file does not contain a key.

A manual merge into ~/.cursor/mcp.json is a different syntax. Use examples/cursor.mcp.json, which expands ${env:OPENANY_API_KEY} and still points at https://mcp.openany.si/mcp. To use the lite URL outside the plugin, copy the server block from .mcp.json and change the header to Bearer ${env:OPENANY_API_KEY}.

There is no root mcp.json. Cursor's plugin loader reads .mcp.json before mcp.json when both exist, so the manifest points at the one file.

OpenClaw

plugins/openclaw/openany/SKILL.md is an OpenClaw skill. Its front matter requires OPENANY_API_KEY and sets the homepage to https://openany.si. The skill tells the agent to add https://mcp.openany.si/mcp-lite under mcp.servers in ~/.openclaw/openclaw.json with transport set to streamable-http, then to call search_apis, get_api, confirm the returned price, and only then run_api. See the skill README.

examples/openclaw.json remains the manual example for the full /mcp URL.

Which URL the install files use

The Gemini CLI extension, the Cursor .mcp.json plugin, and the OpenClaw skill use https://mcp.openany.si/mcp-lite. Public tools/list on that URL returns search_apis, get_api, and run_api in a single page and does not send nextCursor. The full https://mcp.openany.si/mcp URL returns one tool per API, 50 tools per page, with nextCursor until the last page.

That split matters for these clients. Cursor staff wrote in July 2026 and again in September 2026 that the desktop MCP client registers only the first tools/list page and does not follow nextCursor. Gemini CLI shortens a tool name longer than 63 characters. The first page of /mcp is 50 tools and is not the search, inspect, and run workflow. The lite URL keeps that workflow on three short names. The manual examples and server.json still use /mcp.

Discovery for this choice was an unauthenticated tools/list. It was not an authenticated tools/call.

Verify without accidentally spending

1. Connect to the full endpoint URL using Streamable HTTP.
2. List tools and inspect the intended tool's current schema. Discovery alone does not prove authentication, balance access or successful execution.
3. Before a live call, review the current price, parameters and total spending limit, and obtain explicit approval. Configure the key privately.
4. Confirm the result of the authorized tools/call, its gateway status and available usage or billing record. Do not equate HTTP 200 with business success. Never repeat an uncertain paid request automatically.

No new authenticated live tools/call was performed during this documentation update.

Registry metadata

server.json is the descriptor for the official MCP registry's 2025-12-11 schema. Its required Authorization header describes the confirmed authenticated-call configuration, not a credential requirement for public tools/list.

The registry description is limited to 100 characters, so its wording is shorter than the full description above. Version 0.1.0 is published on the official MCP Registry as si.openany/openany. Local setup does not run mcp-publisher publish.

Development

The existing Go server implementation, configuration, migrations and tests are preserved. See development and operator notes, the lightweight connection guide and existing verification records. The optional lightweight interface is separate from the full /mcp endpoint documented here.

Links

• OpenAny
• Agent instructions
• Documentation
• Document index
• Model API base URL
• Agent instruction snippets

License

MIT. Copyright (c) 2026 Alephant AI LLC.