Log inSubmit server
PipesHub logo

PipesHub

Permission-aware workplace search and cited answers across Slack, Drive, Gmail, Jira, and 50+ sources.

InstallRepositoryWebsite
Full README Compare alternatives Embed widget Claim this listing

Install PipesHub

Pick your client, then add it in one click or paste the config.

STDIONode.js
~/Library/Application Support/Claude/claude_desktop_config.json
claude_desktop_config.json
{
  "mcpServers": {
    "pipeshub": {
      "command": "npx",
      "args": [
        "-y",
        "@pipeshub-ai/mcp"
      ]
    }
  }
}

Settings → Developer → Edit Config, merge this into mcpServers, then fully quit and reopen Claude Desktop.

Install not yet sandbox-tested— we haven't run this command through our automated sandbox yet. Not a red flag; we're working through the catalog.

Overview

PipesHub MCP server connects MCP clients to permissioned workplace search across Slack, Drive, Gmail, Jira, and 50+ sources. It exposes tools for searching and reading records, downloading content, checking directories and sources, and optionally chatting with PipesHub agents. The remote endpoint uses Streamable HTTP at `/mcp`, with OAuth credentials or bearer tokens. Reach for it when an agent needs answers grounded in company data while respecting each user's access permissions.

Use cases

  • Search company messages and documents with user permissions
  • Answer workplace questions with cited records
  • Retrieve Jira, Slack, Drive, or Gmail content
  • Inspect connected workplace sources and directories

Key features

  • Permission-aware workplace search
  • Cited answers from connected sources
  • Streamable HTTP MCP endpoint
  • OAuth and bearer-token authentication
  • Record reading and downloading
  • Optional PipesHub agent chat

Security & health

What it can reach and how reliably it runs — from our own checks, not the maintainer’s claims.

ActiveLast checked 1d ago

Recent health check succeeded.

7/7 checks healthy over the last 39d

Supply-chain signal

No high-severity advisories surfaced by our automated scan.

Critical 0High 0Medium 0Low 0

Scanned 11d ago via OSV.dev · @pipeshub-ai/mcp (npm)

Adoption & maintenance

Factual signals from GitHub, npm, and our automated checks — not a rating.

GitHub stars7Stargazers on the source repository.
npm downloads9.5kPackage downloads in the last 30 days.
Last commit1d agoMost recent push to the default branch.
Directory activity2 viewsConfig copies, upvotes, and views on AllMCPs.

How PipesHub works

What PipesHub MCP server does

PipesHub MCP server gives MCP-compatible agents access to workplace information held in PipesHub. Its stated coverage includes Slack, Drive, Gmail, Jira, and more than 50 workplace sources. Search results and answers can be permission-aware and cited, which makes the server relevant for agents that need to retrieve internal information without treating the connected systems as one unrestricted data store.

The repository describes the server as a remote MCP service rather than a package that runs inside each client. It is suitable for the Workplace & Productivity category when an assistant must answer questions from company records, locate relevant documents or messages, or inspect connected workplace sources.

How it works

PipesHub MCP server publishes a Streamable HTTP MCP endpoint at /mcp. An MCP client connects directly to the endpoint, so the standard setup does not require a local npm package or a local stdio process. The instance can be hosted in the cloud or self-hosted.

Authentication is configured through an OAuth app created in PipesHub, using a client ID and client secret. The documentation also describes bearer-token authentication. PipesHub publishes OAuth discovery metadata at /.well-known/oauth-protected-resource/mcp, allowing clients to find the authorization and token endpoints. Access depends on the scopes granted to the OAuth app and exposed by the PipesHub instance.

The recommended workflow is to search and read records first. Chat is available through pipeshub_chat, but the README identifies it as optional. Results can retain the user's permissions, so the same request may expose different information to different people.

Setup and configuration

Before connecting a client, deploy or obtain access to a PipesHub instance and configure an OAuth app under Settings > Developer Settings > OAuth Apps. Register the redirect URI required by the chosen client, then copy the app's client ID and secret. The remote URL follows the pattern PIPESHUB_INSTANCE_URL/mcp.

Client-specific examples are provided for Cursor, Claude Code, Gemini CLI, Codex CLI, Claude.ai, and LibreChat. Cursor can use an auth object in mcp.json, while Claude Code can add the server with claude mcp add --transport http. Secrets can be supplied through environment-variable interpolation in Cursor or through MCP_CLIENT_SECRET for the Claude Code command.

OAuth scopes must match the scopes granted to the app. Claude Code requests every scope advertised by discovery and does not let the user select individual scopes, so the server-side scope list may need to be narrowed with MCP_SCOPES.

Tools and capabilities

The PipesHub MCP server exposes these documented tools:

  • pipeshub_search for finding relevant records.
  • pipeshub_get_record_content for reading record content.
  • pipeshub_download_record for downloading a record.
  • pipeshub_directory for directory-related access.
  • pipeshub_sources for inspecting available sources.
  • pipeshub_chat for optional conversational access.
  • pipeshub_agents for PipesHub agent capabilities.

The documentation recommends search and record reading as the default path for retrieval tasks. Exact arguments and tool guidance are maintained in the repository's TOOLS.md.

Limitations and notes

OAuth redirect URIs differ by client, and incorrect or mismatched scopes can prevent authorization. QM cannot attach a third-party MCP endpoint as a client; its separate deployment-layer bundle provides a pipeshub command instead.

Read the full README View source on GitHub

Reviews

No reviews yet — be the first to share how it worked for you.

Frequently Asked Questions about PipesHub

PipesHub is an MCP server that connects agents to workplace sources including Slack, Drive, Gmail, and Jira. Its main tools search and read records, download content, inspect directories and sources, and optionally use PipesHub chat and agents. Access is permission-aware, and answers can include citations.

You connect an MCP client to your PipesHub instance's `/mcp` URL rather than installing a local npm package. Create a PipesHub OAuth app, register the client's redirect URI, and configure its client ID and secret. The repository also documents a local Docker demo and a coding-agent skill.

Yes, PipesHub works with Cursor through its remote MCP configuration. Add the instance's `/mcp` URL and OAuth credentials to Cursor's MCP settings or `.cursor/mcp.json`, then register Cursor's OAuth callback URI in PipesHub.

PipesHub uses the scopes granted to the OAuth app and advertised through its discovery metadata. Cursor can request a selected scope list, while Claude Code requests all exposed scopes. A mismatch between the app and server scopes causes authorization errors.

Related MCP servers

All in Communication All alternatives
Add a badge to your READMEShow it’s listed — live SVG, Markdown or HTML.

AllMCPs Directory Badge

Full Badge Customizer

Showcase your server listing on GitHub or your project documentation. Embed this dynamic SVG badge to highlight official listing status and live engagement.

Badge Style:
Live Dynamic SVG PreviewPipesHub AllMCPs Directory Badge
Markdown (GitHub README)
[![AllMCPs](https://allmcps.com/api/badge/pipeshub?style=directory)](https://allmcps.com/mcp/pipeshub)
HTML Embed
<a href="https://allmcps.com/mcp/pipeshub"><img src="https://allmcps.com/api/badge/pipeshub?style=directory" alt="PipesHub on AllMCPs" /></a>