# PipesHub [Health: Active]

**Category:** 💬 Communication  
**Repository:** https://github.com/pipeshub-ai/mcp-server  
**GitHub Stars:** 7  
**npm Downloads (last month):** 9504  
**Views:** 2  
**Installs:** 0  
**Upvotes:** 0  
**Directory Page:** https://allmcps.com/mcp/pipeshub

## Description
Permissioned search and cited answers over Slack, Drive, Gmail, Jira, and 50+ workplace sources.

## Claude Desktop Quick Installation
Install path detected from listing signals. Uses `npx` (confidence: high):

```json
"mcpServers": {
  "pipeshub": {
    "command": "npx",
    "args": ["-y","@pipeshub-ai/mcp"]
  }
}
```

## Documentation

## 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.

_Full upstream README: https://allmcps.com/mcp/pipeshub/readme_