TOCA MCP Server
Related Servers
Alternatives to TOCA MCP Server
No user-submitted related servers found.
Related Servers
- AlicenseAqualityFmaintenanceEnables AI assistants to interact with Instagram by scraping profiles, posts, reels, DMs, and business insights through a robust, DOM-agnostic browser orchestration engine that bypasses Instagram's anti-automation measures.281Apache 2.0
- AlicenseNot gradedqualityBmaintenanceEnables agents to break high-level business objectives into dependency-ordered sub-task graphs and then directly generate the finished deliverables, such as financial spreadsheets, executive presentations, and analytical reports. It runs as a zero-dependency Python MCP server over JSON-RPC stdio, adding deterministic authorization, role-boundary validation, and telemetry.7MIT
- FlicenseNot gradedqualityBmaintenanceEnables AI agents to execute real-world API actions with exactly-once reliability, deduplication, auditing, and human-in-the-loop safeguards via MCP.1-
- FlicenseNot gradedqualityBmaintenanceEnables orchestrating workflows across GitHub, Telegram, and Stripe with a reliability gate that retries, reroutes, deduplicates, and rolls back side effects, while maintaining a verifiable hash-chained audit log.-
- AlicenseNot gradedqualityBmaintenanceTurns Google Workspace into 45 MCP tools spanning Gmail, Drive, Calendar, Docs, Sheets, Slides, Chat, Tasks and Contacts, with server-side OAuth and a single bearer token so any AI client can read, send, create, and manage workspace content without a browser or Google SDK.MIT
- FlicenseNot gradedqualityBmaintenanceEnables autonomous scheduling of creator content deliverable calendars and embargo wave campaigns through natural language, integrating with MCP-compliant clients for deterministic, zero-dependency execution.8-
TDQS
Scored across 12 tools
Most tools have clearly distinct purposes (e.g., toca.workflow.create vs toca.workflow.get vs toca.workflow.advance). The exception is toca.system.health versus toca.verify—both touch on readiness/state but from different angles. Minor overlap is acceptable.
All tool names follow a consistent pattern of 'toca.<domain>.<verb>' with clear verbs (get, create, advance, query) and nouns (capability, workflow, approval, audit, event). No mixing of styles or conventions.
12 tools is well within the ideal 3-15 range. Each tool covers a distinct operation across core domains (system, capabilities, workflows, approvals, audit, events), and the count feels appropriately scoped for the server's purpose.
The server covers key operations but has notable gaps: workflow lacks an update/abort/delete, approval only has create/get (no approve/deny), and there is no event publishing—only reading. The execute tool is comprehensive but may serve as a generic workaround, yet missing lifecycle operations could still cause agent failures in certain flows.