Generate MCP Server
AI agents are becoming primary consumers of APIs, and they reach them through the Model Context Protocol (MCP). MCP is the open standard that lets clients like Claude and Cursor discover what your API can do and call it directly. Theneo turns the API spec you already maintain into a ready-to-run MCP server, so your endpoints become structured tools an agent can use, with no extra code to write or keep in sync.
Your OpenAPI spec is all Theneo needs. Every server is generated from the spec you already maintain, so your agent tools stay in sync with your API.
How it works
1
Configure
Open the MCP settings, choose the operations to expose, and set the transport and authentication your server needs.
2
Generate
Theneo builds a ready-to-run server that presents each selected operation as a structured, well-described tool.
3
Connect
Any MCP-compatible client connects to the server and can discover, understand, and call your API in real time.
Accessing MCP settings
Open the MCP configuration page directly at editor.theneo.io/mcp.
Configuration
Base URL override
Specify a custom API base URL for your MCP server (for example https://api.example.com). Leave it empty to use the base URL already defined in your OpenAPI spec.
Transport method
Choose how your MCP server communicates with clients:
STDIO
Standard input and output. Best for local development and CLI-based integrations.
HTTP
Standard HTTP transport. Recommended for server-to-server and web deployments.
Server-Sent Events (SSE)
Real-time, one-directional streaming from server to client. Ideal for live updates.
Choosing which operations to expose
The API operations section lists every endpoint from your spec, each with its HTTP method, path, and a short description.
- Use the checkboxes to include or exclude individual operations.
- Use Deselect All to clear everything, then reselect just what you need.
Only the operations you select are exposed through the generated server, so you can ship a focused, intentional set of tools rather than your entire surface area.
Authentication and security
Configure the authentication your MCP server requires so only authorized clients can connect. Security schemes are detected automatically from your OpenAPI spec. For each scheme, define the environment variable name the server uses to resolve the credential at runtime.
Credentials are resolved from environment variables in your own runtime, so secrets are not baked into the generated server.
Advanced settings
Request timeout (ms)
The maximum time the server waits for a response before timing out. Defaults to 30,000 ms (30 seconds). Adjust it to match your API's expected response times.
Pagination hints
Adds pagination support for list operations, helping AI clients understand how to page through results.
Generating the server
Once configured, click Generate MCP server in the bottom-right corner. Theneo processes your configuration and produces a ready-to-use server based on your spec and chosen options.
- Not sure which transport to use? STDIO is best for local testing; HTTP or SSE suit production.
- Set every required environment variable in your runtime before starting the server, to avoid authentication failures.
- Return to editor.theneo.io/mcp anytime to regenerate with new settings or a different selection of operations.
MCP server generation may need to be enabled for your workspace or project. Contact us at hello@theneo.io and we'll switch it on.
On this page
- Generate MCP Server