Actions to MCP

Paste an OpenAPI 3.0 or 3.1 schema and download a Cloudflare Worker MCP server. Writes off by default, secret-path or API-key auth. Tested with MCP Inspector.

View on pages.devTry this MCPSponsored

Documentation

Your schema stays in your browser. Nothing is uploaded. We count generated downloads anonymously (no schema, no IP).

Useful if you're moving a custom GPT Action's schema to MCP.

On Plus or higher and only need it for yourself? ChatGPT Sites may be simpler: it can host an MCP server as a plugin and keep secrets, like an API key, in its settings. (OpenAI Help)

Tested with MCP Inspector.

We haven't tested connecting it in ChatGPT developer mode yet.

How to use it

  1. 1 Paste an OpenAPI 3.0 or 3.1 schema, or upload a local JSON or YAML file. This page never fetches a schema from a URL.
  2. 2 Review the operations (GET/HEAD are ticked; writes need an explicit opt-in), edit the server URL if needed, and pick auth: none with the path gate, or an API key held as a Worker secret. Keep the default secret URL path, or choose the header gate if your client can send custom headers. OAuth 2.1 template in the paid pack ($29).
  3. 3 Download the ZIP. The endpoint is https://<your-worker>.workers.dev/mcp/<MCP_PATH_TOKEN>. That URL is the secret. On your machine run npm i, wrangler secret put MCP_PATH_TOKEN, then wrangler deploy.

Known limitations

  • Swagger 2.0 rejected
  • Non-JSON bodies, external $refs, TRACE, and webhooks/callbacks skipped
  • Cookie params dropped
  • One global auth mode (none or API key)
  • deepObject/explode not modeled
  • No OAuth 2.1 server in the free generator
  • Write operations off by default; opt in per operation
  • HTTPS upstream only

Not affiliated with or endorsed by OpenAI or Anthropic.