OpenAny MCP

OpenAny MCP

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

Endpoint: https://mcp.openany.si

Transport: Streamable HTTP, not legacy SSE.

Operator: Alephant AI LLC.

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

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

Configuration

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

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

This block uses the lightweight endpoint. The client setupexamples remain in place, including files that point athttps://mcp.openany.si/mcp.

Tools

https://mcp.openany.si is the lightweight server. https://mcp.openany.si/mcp-lite is the same server. It exposes four tools. openany_overview reports live catalog counts. search_apis finds168+ models and 3,200+ APIs. Execution is pay per call, no monthly fee, withone API key.

• openany_overview: Return the current data API count, AI model count, APIs grouped by category, and models grouped by modality. No arguments, and it does not call the paid gateway.
• 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 bytikhub (1,009), anyapi (337), justoneapi (301), scrapecreators (193), andqcc (170). The list is in TOOLS.md.

Optional lightweight endpoint

When enabled and routed by the deployment, https://mcp.openany.si andhttps://mcp.openany.si/mcp-lite use the same Streamable HTTP transport and expose four tools:openany_overview, search_apis, get_api and run_api. One search covers the current modelcatalog 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 liveGET /v1/models response and are omitted when that response does not providethem. Pay per call, no monthly fee, one API key.

The implementation enables this interface by default; operators can disableit with MCP_LITE_ENABLED=false. Public deployment availability is a separatecheck. openany_overview, search_apis and get_api read metadata; run_api forwards a businessrequest and may incur charges, requiring the caller's gateway credentials andspending authorization. Configure one endpoint, not both, unless your workflowexplicitly needs both catalogs. See the lightweight guide.The manual examples continue to use /mcp. The registry descriptor uses the recommended root URL.

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. It also does not collect a key with MCP form elicitation. URL elicitation is not offered, because OpenAny has no elicitation completion page. Create a key at https://openany.si/dashboard?page=api-keys and store it in the client's secure secret or connector settings. A run_api call with no key is rejected locally (openany_mcp_credentials_missing) and does not reach the gateway. A key the gateway rejects keeps its code, including the live openany_key_invalid and openany_authentication_invalid, plus the expired and revoked siblings. Never ask the user to paste the key into chat. A raw Authorization value with no scheme is sent as Bearer <key>. An unexpanded placeholder such as ${OPENANY_API_KEY} is rejected locally as openany_mcp_credentials_placeholder.
• Confirmed authentication header:Authorization: Bearer <OPENANY_API_KEY>. Supply an OpenAny API key throughOPENANY_API_KEY; the examples use this confirmed header format.

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

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

Client setup

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

The Hermes row is a manual mcp_servers example for the full /mcp endpoint.The installable plugin is plugins/openany. Itsdefault is https://mcp.openany.si, because Hermes 0.23.0 stopstools/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 pluginserver. The owner-run session, the CoinGecko tool result, request420decad-3a6b-46f8-acff-53966bbd8b1c, tool cost 0, and 807 microUSD of modelcalls are recorded in docs/hermes-e2e.md.

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

The requested Claude Code command expands the environment variable beforeinvoking its CLI. The resulting header can be visible to local processinspection and may be stored in personal client configuration. Do not run itwith shell tracing or commit the generated configuration. The Pi/OpenClaw CLIalternatives in annotations are alternatives, not additional commands to runas 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 matchingclient 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 and sendsAuthorization: Bearer ${OPENANY_API_KEY}. The key is the sensitive settingOPENANY_API_KEY. Gemini CLI asks for it during install and stores it outsidethis repository. GEMINI.md is the extension context file.

Cursor

.mcp.json is the root file cursor.directory reads for an MCPserver. .cursor-plugin/plugin.json is theCursor plugin manifest. It declares OPENANY_API_KEY as a required stringvariable and sets mcpServers to .mcp.json. The header in that file isAuthorization: Bearer ${OPENANY_API_KEY}. Cursor fills the placeholder fromthe plugin setting. The file does not contain a key.

A manual merge into ~/.cursor/mcp.json is a different syntax. Useexamples/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.jsonand change the header to Bearer ${env:OPENANY_API_KEY}.

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

OpenClaw

plugins/openclaw/openany/SKILL.md is anOpenClaw skill. Its front matter requires OPENANY_API_KEY and sets thehomepage to https://openany.si. The skill tells the agent to addhttps://mcp.openany.si under mcp.servers in~/.openclaw/openclaw.json with transport set to streamable-http, thento call search_apis, get_api, confirm the returned price, and only thenrun_api. See the skill README.

examples/openclaw.json remains the manual examplefor the full /mcp URL.

Which URL the install files use

The Gemini CLI extension, the Cursor .mcp.json plugin, and the OpenClawskill use https://mcp.openany.si. Public tools/list on that URLreturns openany_overview, search_apis, get_api, and run_api in a single page and does notsend nextCursor. The full https://mcp.openany.si/mcp URL returns one toolper API, 50 tools per page, with nextCursor until the last page.

That split matters for these clients. Cursor staff wrote in July 2026 andagain in September 2026 that the desktop MCP client registers only the firsttools/list page and does not follow nextCursor. Gemini CLI shortens atool name longer than 63 characters. The first page of /mcp is 50 toolsand is not the search, inspect, and run workflow. The recommended URL keeps thatworkflow on four short names. The manual examples still use /mcp.server.json uses https://mcp.openany.si.

Discovery for this choice was an unauthenticated tools/list. It was not anauthenticated 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 alonedoes not prove authentication, balance access or successful execution.
3. Before a live call, review the current price, parameters and total spendinglimit, and obtain explicit approval. Configure the key privately.
4. Confirm the result of the authorized tools/call, its gateway status andavailable usage or billing record. Do not equate HTTP 200 with businesssuccess. 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 MCPregistry's 2025-12-11 schema.Its required Authorization header describes the confirmed authenticated-callconfiguration, not a credential requirement for public tools/list.

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

Development

The existing Go server implementation, configuration, migrations and tests arepreserved. See development and operator notes,the lightweight connection guide andexisting verification records. The optional lightweightinterface 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.