ToolBridge MCP
Related Servers
Alternatives to ToolBridge MCP
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityBmaintenanceA production-grade platform that connects AI assistants to internal databases and filesystems through a single authenticated endpoint. It features role-based access control, SSO integration, and built-in tools for querying SQL databases and managing files with full audit logging.6MIT
- AlicenseNot gradedqualityCmaintenanceEnables AI assistants to search internal knowledge bases, create Confluence articles, file Jira tickets, and look up Okta users, with guardrails and streaming support.MIT
- FlicenseNot gradedqualityDmaintenanceEnables AI agents to search HR policies, create IT support tickets, and send external emails with configurable security levels and human-in-the-loop validation.-
- AlicenseNot gradedqualityCmaintenanceEnables AI assistants to connect to business tools like Stripe, Xero, Slack, Jira, and more, with PII redaction applied to tool responses before they reach the model.61 npmMIT
- FlicenseNot gradedqualityDmaintenanceProvides read-only access to Confluence, GitHub, Jira, Figma, Outlook, Teams, and browser automation for AI clients, enabling safe discovery, retrieval, and summarization of company knowledge without modifying source systems.-
- AlicenseNot gradedqualityCmaintenanceEnables AI assistants to safely interact with operations systems such as cloud inventory, runbooks, and ticketing while enforcing role-based access, JWT authentication, write confirmation, secret and PII redaction, rate limits, and audit logging.MIT
TDQS
Scored across 13 tools
Each tool targets a distinct resource and action: wiki search vs. page fetch, ticket list vs. get vs. create/update, and separate directory, on-call, asset, expense, metrics, and audit lookups. There are no overlapping purposes that would cause an agent to misselect.
Most names follow a predictable domain_action pattern such as wiki_search, ticket_get, ticket_create, asset_lookup, and metrics_query. Minor deviations include singular/plural inconsistency (ticket_get vs. tickets_list) and audit_recent lacking an explicit action verb.
With 13 tools, the set is well-scoped for an internal tool bridge spanning wiki, tickets, directory, on-call, assets, expenses, metrics, and audit. Each tool has a clear role, with no obvious filler.
The surface covers broad read/search workflows and a full core ticket lifecycle (list, get, create, update), so most common helpdesk and internal lookup tasks are supported. Gaps remain in write operations for ancillary systems such as wiki editing, asset management, and expense submission/approval, but these may be intentionally out of scope.