Simple, transparent pricing

FlashMCP is a universal MCP gateway that turns any REST API into an MCP server your LLM can use. Just point your MCP client (Claude Desktop, Claude Code, Cursor, VS Code, etc.) at a FlashMCP URL and your AI gets callable tools for every API endpoint. No code, no servers, no Docker - just a URL. FlashMCP includes the world's largest MCP catalog with over 100,000 APIs ready to use in one click.

After signing up, add balance to your account via Stripe Checkout ($5, $10, or $25). Each credit equals one API request ($0.001). Credits never expire - use them whenever you want. When your balance reaches zero, tool calls are paused until you top up. Your API keys, configuration, and history stay intact.

Only actual tool calls (API requests to upstream services) count. Each tools/call that goes through the FlashMCP gateway costs 1 credit - regardless of HTTP method (GET, POST, PUT, PATCH, DELETE). MCP protocol messages like initialize, tools/list, and ping are always free.

No. One flat rate: $1 per 1,000 requests, regardless of which API you're calling. Stripe, GitHub, Twilio, your own internal APIs, any of the 100,000+ APIs in the catalog - all the same price. No per-API surcharges, no tiers, no surprises.

Tool calls are paused and return a 402 status. Your LLM will see a friendly "balance exhausted" message. Simply add more credits from your dashboard to resume instantly. Your API keys, configuration, and usage history are preserved - nothing is lost.

Any MCP client that supports Streamable HTTP transport works with FlashMCP. This includes Claude Desktop, Claude Code, Cursor, Windsurf, VS Code (with Copilot), and any custom client built with the MCP SDK. Configuration is a single URL - see the configuration docs for step-by-step guides per client.

FlashMCP has an intelligent multi-phase discovery engine. It checks a continuously-updated catalog of 100,000+ APIs, then falls back to industry-standard protocols (RFC 8631 Link headers, RFC 9727 well-known endpoints) to locate specs automatically. For APIs where auto-discovery isn't enough, you can provide your own spec with the ?spec= parameter - either a relative path or a full URL.

Absolutely. FlashMCP works with any REST API that has an OpenAPI spec - public, private, or internal. If auto-discovery doesn't find your spec, use ?spec=/path/to/openapi.json to point FlashMCP directly at it. You can even provide a spec hosted on a completely different domain (GitHub, docs subdomain, etc.) using a full URL.

FlashMCP is fully stateless - it doesn't store your API responses, request payloads, or credentials. Your auth headers (Bearer tokens, API keys, custom headers) are forwarded directly to the upstream API and never logged. All traffic is encrypted via HTTPS. Payments are processed by Stripe and we never see your card details.

For high-volume usage (over 1M requests/month), we offer custom volume discounts, dedicated support, and SLAs. Contact our sales team to discuss pricing tailored to your needs.