Turn your API into a server AI agents can call
Publish any proxy as an MCP server so Claude, Cursor and other agents can use it as a tool. And chat your way there — APIblaze's agents draft your spec, authz rules and MCP catalogue from real traffic.
- npx apiblaze apichat — any spec becomes a proxy, an MCP server and a chat
- One command publishes an MCP server at {project}-{tenant}.mcp.apiblaze.com
- Chat to author OpenAPI specs, authorization rules & MCP tools
- Specs generated from real captured traffic — no hand-writing YAML
you › expose search + order lookup as tools
MCP catalogue
search_products (q, limit)
get_order (order_id)
/publish
✓ live → acme-acmecorp.mcp.apiblaze.com/1.0.0/prod
Claude & Cursor can now call your API.
From raw traffic to AI-ready, in a conversation
MCP server export
Pick the routes that become tools, name them, and publish an MCP server agents can call — no custom code.
apichat
Point at any OpenAPI spec and chat with the API — every answer shows the real call it made. No login needed.
Chat-driven config
Three agents — OpenAPI, authorization and MCP — draft your configuration in plain English.
Specs from traffic
APIblaze watches real requests and proposes an OpenAPI spec, so you never hand-write YAML again.
Open a PR
Push the generated OpenAPI spec straight back to your GitHub repo as a pull request.
Always in sync
Your MCP catalogue and docs track the routes your API actually serves, not a stale spec.
Try it in 30 seconds
No signup required. Claim it to your account whenever you’re ready.