mc8yp
Related Servers
Alternatives to mc8yp
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityDmaintenanceAn MCP server that gives AI agents full access to the Clever Cloud API through three tools: search, execute, and doc, using a code mode pattern to compose API commands.4Apache 2.0
- AlicenseNot gradedqualityDmaintenanceAn MCP server that gives AI coding agents structured access to a project's architecture, rules, modules, and technical decisions.MIT
- AlicenseAqualityCmaintenanceMCP server that exposes RESTForge capabilities to AI agents, enabling them to set up, configure, generate code, and manage RESTForge projects through natural language.2944 npmMIT
- AlicenseBqualityDmaintenanceProduction-grade MCP server that gives AI agents safe access to your local dev environment: filesystem, databases, processes, and OpenAPI specs.1540 npm4MIT
- AlicenseNot gradedqualityDmaintenanceAn MCP server that enables AI agents to explore, search, and query API definitions from OpenAPI/Swagger JSON files.MIT
- FlicenseNot gradedqualityBmaintenanceAn MCP server that gives an AI agent read and write access to a live SysML v2 model through the vendor-neutral OMG SysML v2 REST API.3-
TDQS
Scored across 3 tools
The three tools occupy clearly different roles: codemode executes code against the API, status reads/reports current state, and set-active-tenant mutates tenant selection. The one soft overlap is that status can 'self-heal' by resetting lost credentials, which brushes against set-active-tenant's clearing behavior, but the read-vs-write boundary is still clear from the descriptions.
Two tools are bare nouns (codemode, status) while one is a kebab-case verb-noun (set-active-tenant), so there is no single predictable pattern. Each name is individually readable and the inconsistency is mild rather than chaotic.
Three tools is lean for a gateway server, but codemode is a meta-tool that absorbs the entire discover-describe-call surface, so the real toolset is effectively unbounded through it. setup/status/execute is a defensible minimal triple; only slightly under a typical well-scoped count.
The session lifecycle is covered: check state (status), connect/switch (set-active-tenant), execute (codemode), plus cache refresh via status.refresh and tenant clearing via a null argument. The notable gap is credential/authentication setup — status references 'stored tenant credentials' but no tool exists to establish them, so onboarding a new tenant depends on out-of-band state.