PipesHub

Install

Works with Claude Code, VS Code, Codex, Cursor, Windsurf, Claude Desktop. Read the repository before you give any tool access to your data.

npx agentmarket install connector/pipeshub-ai-mcp

About

Use cases: knowledge-base

No reviews yet. Installed it? Reviews come from verified installers only. How reviews work

Permissions

What this server can do and what it asks for, from its tool list, install config and code. Checked Oct 25, 2026.

Tools

9 read · 0 write · 2 delete

Secrets

1 (API keys, tokens or passwords)

Install scripts

None found

Runs as

Node.js package

Tools (11)

Read from the source code; the running server may differ. Descriptions are the server’s own words; hidden characters are shown as [U+…].

• describe_tool_inputDescribe Toolread-only

  Get the input schema for one or more tools. It is a good idea to call this tool first to understand how to successfully call execute_tool.

• execute_toolExecute Toolcan change or delete data

  Execute a tool by name with the provided input parameters. If executing a given tool for the first time, it is recommended to call describe_tool_input first to understand the expected input schema.

• list_scopesList Scopesread-only

  List the scopes available on this server. Scopes are categories that group related tools together. They can be used as search terms when filtering the list of tools.

• list_toolsList Toolsread-only

  List available tools. Optionally filter by search terms that match against tool name, description, and scopes.

• pipeshub_agentsList PipesHub agents (with toolsets & knowledge)read-only

  List the PipesHub **agents** configured for this org, each with its capabilities. Agents are specialized assistants (custom system prompt, tools, knowledge scope). To converse with one, take its `agentId` and pass it to `pipeshub_chat`'s `agentId` argument. Each agent is returned as: `{ agentId, name, description, systemPrompt, startMessage, tags, webSearch, isActive, toolsets, knowledge }`. - `toolsets` — what the agent can DO: each `{ name, tools }` where `name` is the connector (e.g. `jira`, `gmail`) and `tools` are the runnable tool ids (e.g. `jira.create_issue`, `gmail.send_email`).…

• pipeshub_chatChat with PipesHubcan change or delete data

  Optional. Ask PipesHub's own assistant. Its answer is a synthesis of a few retrieved passages — never a whole document, never a complete list. **If you can call tools, answer the question yourself:** `pipeshub_search`, then read the records that matter with `pipeshub_get_record_content` (`mode:"navigate"` for what is under an epic, space or folder, and for every "how many" / "all"). That is as accurate as adding this tool, with fewer wrong claims, at lower cost and latency. Use this tool only when you cannot run your own search-and-read loop, when the user asks for PipesHub's answer, to run …

• pipeshub_directoryPipesHub directory (users / groups / teams / whoami)read-only

  Look up people, groups, and teams in PipesHub. Five actions — pick `action`. Not for documents or files: that is `pipeshub_search`. - `whoami` — the caller's id, email, full name. Use before `get_user` on yourself. Errors if the credential is expired or revoked. - `list_users` — page org users; `search` matches name or email. - `get_user` — full `User` for one `userId`. - `list_groups` — org groups with `userCount`; `search` matches name. - `list_my_teams` — teams the caller is on, with `canEdit` / `canDelete` / `canManageMembers`; `search` matches name. Omit `page`/`limit` for the first…

• pipeshub_download_recordDownload a document by record idread-only

  Download the file as stored for one record — not PipesHub's parsed content, metadata header, or summary. Use this when the user wants the file itself (download, attach, open). Get `recordId` from a chat citation or a `pipeshub_search` hit. Do not use this to read, summarize, or answer "what does this doc say?" regardless of format. That is `pipeshub_get_record_content` `mode:"content"`. Text formats come back inline; images, audio, and binary as base64. `convertTo` accepts only `application/pdf`; anything else is ignored.

• pipeshub_get_record_contentRead, browse, or resolve recordsread-only

  Four operations on the org's records. Pick by what you hold: `mode:"lookup"` — a URL, issue key (PA-1787), or external ID → its recordId plus the record's metadata `mode:"navigate"` — a question about structure: what is under X, what links to Y → browses the hierarchy `mode:"content"` — a recordId, and you need that record's text `mode:"thread"` — a Slack message whose whole thread you need **`mode:"content"` (default)** — the only way to read one record's full text. Use it whenever missing part of the document could make the answer wrong:…

• pipeshub_searchSemantic searchread-only

  Vector / semantic search across the org's indexed documents. **The default first step for a question about the org's knowledge**, and for locating a document by name, topic, or phrase. Then read the records that matter with `pipeshub_get_record_content` and answer from them; search again with other wording or sources if the first results miss. `pipeshub_chat`, where offered, is optional: it runs PipesHub's assistant and returns an answer with citations to check. For a full-document task (summarize, extract, review, "what does the doc say?"), read the top hit with `mode:"content"`. Also: reso…

• pipeshub_sourcesList PipesHub sources and AI modelsread-only

  Discover available chat sources and AI models in one call. Returns up to three sections: - `sources` — connectors (`kind: "connector"`) and collections (`kind: "knowledgeBase"`). For `pipeshub_search` and `pipeshub_chat`, put a connector `id` in `apps` and a collection `id` in `kb`. `sourcesTruncated: true` means the list stopped at 1,000 sources. Readable ones carry `coverage`. - `llmModels` — chat / generation models. Each item's `modelKey` is the value to pass on `pipeshub_chat` as `modelKey`. Pick `isDefault: true` unless the user asks for a specific model. - `embeddingModels…

Compare and alternatives

Featured in

• Best MCP servers for Slack

Signals

Stars

17

Forks

7

Open issues

1

Last commit

Oct 24, 2026 (4 days ago)

Last release

Oct 25, 2026 (3 days ago)

From GitHub (fetched Oct 24, 2026).

Details

Registry name

io.github.pipeshub-ai/mcp

Version

4.7.0

Auth

Bearer token

Packages

npm @pipeshub-ai/mcp

License

Apache-2.0

Repository

github.com/pipeshub-ai/mcp-server

Website

docs.pipeshub.com/for-agents

First seen

Oct 24, 2026

Last checked

Oct 26, 2026

Source

Official MCP Registrygithub-graphql