The AnyAPI MCP server is a local stdio-type MCP (Model Context Protocol) server used to proxy access to the AnyAPI hosting service. It aggregates hundreds of scraping and data APIs behind a single gateway, so users can call them with just one key, billed per request in US dollars, returning normalized schemas, and with automatic failover capabilities.
In terms of use, this server is aimed at scenarios requiring access to scraping and data APIs such as social media, search results, Google Maps, e-commerce, and web data, and is suitable for connecting these data capabilities to AI clients or agents via the MCP protocol.
Main capabilities include: accessing hundreds of APIs through one key; billing per request in US dollars; returning normalized JSON schemas; automatic failover; failed calls are not charged. The server provides ten tools, which are read in real time from the hosting server rather than declared in this package, so catalog or schema changes take effect without a release of this package. Four of these catalog tools (search_apis, list_apis, get_api, quote_api) can be used without a key, allowing you to find APIs, read input schemas, and get call quotes; run_api and the account tools return 401 when there is no key. The hosting server also responds to initialize and tools/list without credentials, so clients can connect and see these ten tools without an account. The same catalog is also exposed via REST: GET https://api.getanyapi.com/catalog and GET https://api.getanyapi.com/catalog/search。
Usage: can be run via npx, with no need to clone and build; can also be run via Docker, likewise with no need to clone and build. Keys can be obtained at https://getanyapi.com/dashboard/keys . Agents can mint a free trial key themselves, with no dashboard and no email required. The key is optional, but its scope must be clear: a keyless installation can look up APIs, read input schemas, and get call quotes, but run_api and the account tools require a key. npm run check requires no network and no API key. To manually drive the built server against production, refer to the repository instructions.
Use cases: suitable for clients that only support launching local MCP servers via stdio. If the client supports remote Streamable HTTP, it can point directly to https://api.getanyapi.com/mcp，跳过本包。
Limitations: this package is a local stdio proxy and is not suitable for clients that directly use remote Streamable HTTP; without a key, run_api and the account tools cannot be called; billing is per request in US dollars, and failed calls are not charged. Other specific features, pricing details, platform support, etc. are not yet provided.
