Add a Swagger/OpenAPI file and the endpoints are prepared as MCP tools. Each endpoint can be published or kept private.
- Publish the endpoints agents should use, leave the rest closed.
- Write tool descriptions in clear language agents can follow.
Turn API endpoints and selected database objects into MCP tools. You decide what gets published and what stays private.
https://api.example.com/openapi.jsonorders.get_order_by_idPublishedAdd an API or database source, choose what to publish, refine the tool descriptions, and monitor usage from one place.
Add a Swagger/OpenAPI file and the endpoints are prepared as MCP tools. Each endpoint can be published or kept private.
For PostgreSQL and SQL Server, choose the tables, views, columns, and relationships that should be available.
Selected objects and relationships are defined before publishing.
Try the tools in the built-in chat screen first. When ready, connect the same MCP URL to the client your team uses.
Every MCP call can be reviewed in logs, and usage can be understood through simple charts.
The walkthrough shows source import, generated tools, publishing controls, chat-based testing, and MCP client setup.
Start with the SaaS product, or contact RTT Intelligence for private deployment, integration design, and on-premise requirements.