platform-mcp-stub
Related Servers
Alternatives to platform-mcp-stub
No user-submitted related servers found.
Related Servers
- AlicenseAqualityDmaintenanceFull coverage of Anthropic Admin API to manage organization, workspaces, members, API keys, usage, and costs via natural language from any MCP client.21MIT
- FlicenseNot gradedqualityDmaintenanceEnables HR teams to automate employee onboarding workflows through an Agentic AI system integrated with Claude Desktop.1-
- FlicenseNot gradedqualityNot gradedmaintenanceEnables AI-first DevOps management of multi-tenant Solid SaaS platforms through natural language conversation. Monitor thousands of tenant instances, track AI agent performance, handle errors, manage billing, and provision new tenants directly through Claude Desktop.-
- AlicenseNot gradedqualityCmaintenanceEnables read-only reporting of Anthropic organization usage and costs through a user-connected admin API key, across any MCP-compatible client.MIT
- FlicenseNot gradedqualityCmaintenanceEnables AI agents to provision and manage external SaaS services (Clerk, Stripe, Resend, etc.) by authenticating and creating resources via YAML configuration.30 npm-
- FlicenseNot gradedqualityDmaintenanceExposes LiteLLM Proxy admin APIs as MCP tools for managing internal users, virtual keys, and spend logs via streamable-http, enabling agents to administer LiteLLM without custom HTTP glue.1-
TDQS
Scored across 3 tools
Each tool addresses a distinct domain area: rate limits, API key requests, and usage summaries. There is no meaningful overlap between them, and the status-checking behavior inside request_api_key is clearly documented rather than being a separate ambiguous tool.
All tool names follow a consistent verb_noun pattern in snake_case: get_limit_status, request_api_key, get_usage_summary. The verbs are descriptive and the naming style is uniform across the set.
Three tools is a reasonable scope for a platform admin stub focused on limits, usage, and key requests. Each tool covers a distinct administrative area without unnecessary bloat or redundant operations.
The set covers the main admin concerns suggested by the server name: rate limits, usage reporting, and API key access requests. Minor gaps exist, such as no direct approval or managed key listing, but these appear intentionally delegated to an out-of-band CLI process.