Schema-aware API tools
AI clients can list endpoints, inspect parameters and request bodies, read component schemas, and call approved operations.
OpenAPI / Swagger / hosted MCP
Paste an OpenAPI 3.x specification or Swagger documentation URL. DataMCP exposes MCP tools for endpoint discovery and approved API calls, hosts the endpoint, and injects upstream authentication.
tools/call → productionPOLICY CHECKEDDirect answer
Use datamcp when you already have an OpenAPI 3.x specification or Swagger documentation and want a ready remote MCP endpoint rather than generated server code that your team must deploy and maintain.
The production path
OpenAPI already describes an API's paths, parameters, request bodies, and response schemas. MCP describes tools an AI client can discover and call. DataMCP maps the existing contract into MCP tools and forwards each approved call to the original API.
There is no generated repository to maintain and no transport service to deploy. Update the source specification, resync the connection, and keep the MCP toolset aligned with the API.
DataMCP also accepts documentation pages when the raw schema URL is hard to find. Paste a Swagger UI or Redoc URL and the platform will attempt to extract the embedded specification automatically. See the OpenAPI connection documentation for supported authentication and access modes.
Using Python? FastAPI publishes an OpenAPI schema by default. Follow the FastAPI MCP server tutorial to verify /openapi.json, proxy paths, authentication, and link policy.
Using TypeScript? NestJS can publish an OpenAPI document through @nestjs/swagger. The NestJS MCP server guide compares runtime OpenAPI conversion with a native NestJS MCP module.
What you get
AI clients can list endpoints, inspect parameters and request bodies, read component schemas, and call approved operations.
Connect Claude, ChatGPT, Cursor, VS Code, or another remote MCP client without deploying generated code.
Store an API key, Bearer token, or Basic credential and attach it server-side to upstream requests.
Expose GET and HEAD operations while blocking methods that create, update, or delete resources.
Let AI list available API operations and inspect an endpoint before calling it.
Authenticate the MCP client with a DataMCP API key or OAuth flow while keeping the upstream API credential on the connection.
Source to controlled MCP link
Connect the source once. DataMCP handles discovery, hosted transport, client authentication, and link policy.
Read the setup guideUse a raw OpenAPI JSON or YAML file, Swagger UI, or Redoc documentation page.
Add upstream authentication and choose whether the MCP link is read-only or has full API access.
Copy the hosted MCP URL into the client. The OpenAPI discovery and call tools are available immediately.
Build or use datamcp
See what stays on your engineering backlog when the MCP runtime and control layer are managed for you.
Source files to review and deploy
Regenerate, test, and redeploy
Implement secret storage and forwarding
Build method filtering
Build or configure logging
Frequently asked questions
Clear answers about architecture, access, credentials, and supported clients.
DataMCP reads an OpenAPI 3.x specification and exposes four MCP tools for discovering endpoints, inspecting operation details, reading component schemas, and calling an approved endpoint. DataMCP then translates call_endpoint requests into requests to the original REST API.
Yes. You can provide a raw OpenAPI JSON or YAML URL, or a documentation page such as Swagger UI or Redoc. DataMCP detects and extracts the embedded specification when available.
Configure an API key, Bearer token, or HTTP Basic credential on the connection. API keys can be sent in a header, query parameter, or cookie, and optional custom headers can be added. DataMCP injects the configured values into upstream calls, so they do not have to be placed in the AI client's MCP configuration.
Yes. A read-only MCP link allows GET and HEAD operations while blocking methods that typically create, update, or delete data. Full-access links can expose all configured operations.
No. DataMCP performs the conversion at runtime and hosts the MCP endpoint. You keep the existing REST API and OpenAPI specification; no generated server project is required.
No. OpenAPI endpoint calls do not currently appear in the DataMCP activity log. Use the upstream API, gateway, or infrastructure logs when you need an execution record for API requests.
Keep exploring
Connect FastAPI's generated OpenAPI schema, verify proxy paths and authentication, and publish a hosted MCP link.
GUIDEChoose between a native NestJS MCP module and a hosted MCP link generated from @nestjs/swagger.
GUIDETurn an existing OpenAPI 3.x or Swagger documentation URL into a remote MCP endpoint step by step.
GUIDESeparate MCP client authentication from API keys, Bearer tokens, Basic auth, and upstream OAuth.
GUIDECombine method filtering, endpoint visibility, least-privilege credentials, API authorization, and operational limits.
GUIDEChoose between runtime OpenAPI conversion and purpose-built MCP code across workflows, authentication, hosting, maintenance, and cost.
GUIDEDefine tools, choose local or remote transport, implement authentication and backend boundaries, test failures, and plan production ownership.
Start with one link
Connect one OpenAPI specification and publish one hosted MCP link for free. Keep the API you already have.