Centia MCP Server
OfficialRelated Servers
Alternatives to Centia MCP Server
No user-submitted related servers found.
Related Servers
- FlicenseAqualityDmaintenanceExposes two MCP tools (discover and execute) that enable agents to query an OpenAPI schema via natural language and execute matched API operations.2-
- AlicenseNot gradedqualityDmaintenanceAuto-generates MCP tools from your OpenAPI spec, allowing natural language interaction with any API via configurable headers and serverless deployment.19 npmMIT
- AlicenseAqualityDmaintenanceExposes Azure AI Foundry agents, workflows, and AI Search vector-database capabilities as MCP tools, enabling natural language interaction with agents, semantic search, and index management.102MIT

cod-api MCP Serverofficial
FlicenseNot gradedqualityDmaintenanceExposes REST API endpoints defined in an OpenAPI Specification as MCP tools, allowing AI models to call them via the ModelContext Protocol.-- AlicenseAqualityBmaintenanceExposes OpenAPI/Swagger API documentation as MCP tools, enabling AI agents to search, inspect, and call API endpoints through natural language.510 npmMIT
- AlicenseNot gradedqualityDmaintenanceExposes OpenAPI specifications as MCP tools, enabling AI assistants to explore and understand API structures, endpoints, schemas, and documentation through semantic queries.8 npmMIT
TDQS
Scored across 56 tools
Every tool name uniquely pairs a verb (delete, get, patch, post) with a resource (client, column, etc.), leaving no ambiguity. Even with 56 tools, each combination is distinct and clearly indicates the resource and action.
All tool names follow a strict verb_noun pattern using PascalCase and HTTP verbs (delete, get, patch, post). This consistency makes the tool set predictable and easy to navigate.
With 56 tools, the count far exceeds the recommended range (3-15). While the domain may require many operations, this volume is likely to overwhelm agents and suggests an overly broad scope.
The tool set covers CRUD for most major resources (tables, schemas, columns, etc.) and includes file handling, SQL, GraphQL, and OAuth. Minor gaps exist (e.g., no delete for events or devices), but the core database operations are well-covered.