wcc_mcp_server
Related Servers
Alternatives to wcc_mcp_server
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityCmaintenancePublishes a shared MCP endpoint where API-key users in different groups see and call only the tools their policies permit, mixing remote upstream tools with local ones. Tool discovery and execution are both filtered, hidden-tool calls are denied before their handlers run, and every action is tagged with subject and group in structured JSON logs.MIT

MonoMCP Gatewayofficial
FlicenseNot gradedqualityBmaintenanceA unified MCP layer that serves organization toolkits as MCP endpoints with per-tool permissions, an async approval queue, and full audit logging.-
clue2app-user-mcpofficial
AlicenseAqualityDmaintenanceExposes user, membership, and role administration tools via MCP, acting as a thin passthrough to a coordinator API with RBAC enforced by the coordinator using caller bearer tokens.8Academic Free v1.1- AlicenseAqualityBmaintenanceA read-only MCP server for the Humanitix Public API that exposes nine tools to list events, fetch event details, list orders/tickets, check-in counts, and sales summaries.9MIT
- AlicenseNot gradedqualityAmaintenanceProvides a single MCP endpoint that dynamically discovers, routes, policy-checks, and executes hundreds of MCP tools from any agent, with optional LLM-based routing.8 npm1Apache 2.0
- AlicenseNot gradedqualityCmaintenanceExposes an MCP-style JSON-RPC interface at /api/mcp that lets an assistant read a live model catalog, compile and score routing policies across fast/balanced/deep lanes, patch lane assignments, and replay per-entity hash chains to verify integrity. All tools share the same service layer as the web UI, so agents can also export a sealed routing manifest.129 npmMIT
TDQS
Scored across 10 tools
Each tool targets a distinct stage in the event lifecycle: pre-check, drafting, speaker lookup, registration, scheduling, publishing, post-event processing, and cleanup. Even set_registration_link and create_registration_form are clearly separated (one saves an existing link, the other creates a new form). No two tools are ambiguous.
Most tools follow a verb_noun pattern (draft_event, publish_event, collect_attendance, cleanup_state). Minor deviations exist: quick_conflict_check uses a modifier + noun_verb, and speaker_lookup has object_verb order. Overall the pattern is predictable and readable.
10 tools is well within the ideal range and each tool serves a necessary step in the event management workflow. The count feels intentionally scoped, covering planning through post-event actions without unnecessary bloat.
The surface covers the full event lifecycle: conflict checking, drafting, speaker lookup, registration, publishing, attendance, recording, and cleanup. Minor gaps exist (e.g., no update/cancel for published events, poster generation noted as not automated), but the core workflow is complete and agents can execute end-to-end.