PipesHub MCP Server
OfficialRelated Servers
Alternatives to PipesHub MCP Server
No user-submitted related servers found.
Related Servers
- FlicenseNot gradedqualityDmaintenanceFacilitates integration of PrivateGPT with MCP-compatible applications, enabling chat functionalities and secure management of knowledge sources and user access.-
- AlicenseAqualityDmaintenanceEnables MCP-compatible clients to interact with AnythingLLM, providing tools for workspace management, chat and thread operations, document operations, vector search, and system inspection.346MIT
- AlicenseNot gradedqualityBmaintenanceEnables agent clients to safely connect to tools and execution resources through MCP with authorization, approvals, audit, chat-context isolation, SSH/Docker access, and long-running command session tracking.MIT
- FlicenseNot gradedqualityFmaintenanceEnables interaction with Rocket.Chat instances through MCP protocol. Allows users to manage chat operations and integrate with Rocket.Chat servers using natural language commands.6-
- AlicenseNot gradedqualityDmaintenanceEnables access to Apollo's tools and services through a standardized MCP interface, compatible with MCP-compliant clients.1MIT
- FlicenseNot gradedqualityBmaintenanceEnables a Business MCP Hub to manage and interact with remote agent devices through typed MCP tools, including file operations, terminal/SSH execution, skills, and MCP server calls, with WebSocket relay and device registry.-
TDQS
Scored across 7 tools
Each tool has a clearly distinct role: search locates and resolves records, get_record_content reads/navigates/lookups, chat answers questions with citations, download_record fetches raw bytes, sources discovers connectors/models, directory handles people/groups/teams, and agents lists assistants. Cross-references in descriptions prevent confusion, and modes within get_record_content are well-separated.
All tools share the pipeshub_ prefix and use snake_case, but the pattern mixes verbs (search, get, download, chat) with nouns (sources, directory, agents). This is a minor deviation since the verb/noun is still intuitive and readable.
Seven tools cover the server's read-focused scope well. Each tool bundles related actions (e.g., get_record_content has three modes, directory has five actions), so the count is appropriately scoped without being bloated or too thin.
The server fully covers the retrieval/lookup side of knowledge management: search, full-content access, hierarchical navigation, identifier resolution, binary download, chat, source/model discovery, directory lookup, and agent listing. No obvious gaps for its stated purpose of querying an org's indexed data.