MCP Tools DirectoryAbout this integration
Permissioned search and cited answers over Slack, Drive, Gmail, Jira, and 50+ workplace sources.
- Transport
- stdio
- Authentication
- client-credentials
- Initial setup
- credentials
- Runtime
- unattended
- Evidence
- documented
- Version
- 2.4.2
- Package
- @pipeshub-ai/mcp
- Last compatibility test
- Not independently tested
Connect your agent
@pipeshub-ai/mcpPublisher documentation and the executable package manifest were reviewed. The approved unattended scope is the local stdio package configured with an instance URL and OAuth client credentials; browser-based OAuth and the separate remote HTTP connection are outside this connection claim. Nothing was executed or independently security-audited.
Capabilities: Search and retrieve records from a configured PipesHub instance, Access documented chat, directory, source, and agent tools
Connected profiles
Additional details
io.github.pipeshub-ai/mcp
Source ↗ · Checked 2026-09-172.4.2
Source ↗ · Checked 2026-09-17CC0-1.0; package licenses are separate
Source ↗ · Checked 2026-09-17npm
Source ↗ · Checked 2026-09-17@pipeshub-ai/mcp
Source ↗ · Checked 2026-09-192.4.2
Source ↗ · Checked 2026-09-19The publisher explicitly documents running the package as a local stdio process with the noninteractive OAuth client_credentials grant.
Source ↗ · Checked 2026-09-19The reviewed mode uses a provisioned PipesHub OAuth application's client ID and client secret; the publisher also documents bearer-token and interactive OAuth alternatives that are outside this selected mode.
Source ↗ · Checked 2026-09-19An MCP host launches npx -y @pipeshub-ai/mcp start with the PipesHub instance URL and credential arguments over stdio; the existing listing remains endpoint-free stdio.
Source ↗ · Checked 2026-09-19Publisher documentation reviewed; package and integration endpoint not executed or independently security-audited.
Source ↗ · Checked 2026-09-19