Skip to main content
Reference for the tools exposed by the PipesHub MCP server. These tools let an AI client (Cursor, Claude Code, Gemini CLI, Claude.ai, LibreChat, etc.) talk to PipesHub — search and chat over the org’s indexed documents, look up people and groups, download files, and talk to configured PipesHub agents. The server exposes seven tools. Each one wraps several lower-level API calls so the LLM gets a single, well-shaped response. This page matches the package’s TOOLS.md.

​
pipeshub_chat

Ask a question and get an answer grounded in the org’s indexed sources, with citations. It reads a few retrieved passages — never a whole document, never a complete list. Three questions this tool gets wrong — check them first:
  • Structure — “what’s under this epic?”, “which pages are in this space?”, “what’s in this folder?” → pipeshub_get_record_content mode:"navigate".
  • Exhaustive — “how many X?”, “list all the Y”, “every Z” → mode:"navigate". Chat undercounts and will not say so.
  • One named document — summarize it, extract from it, what does it say about X → pipeshub_search for the recordId, then mode:"content".
Everything else about the org’s knowledge belongs here: policies, processes, “what do we know about X”, questions spanning several documents. Response: the AI’s answer, citations[] (each with recordId), followUpQuestions, plus the conversationId to use for follow-ups. If citations is empty, relay the answer as unsourced and not confirmed; do not restate its claims as fact. Vector / semantic search across the org’s indexed documents. Use it to locate a document — by name, topic, or a phrase — and to resolve it to a recordId. It is also step 1 of reading a specific document: search, take the top hit’s recordId, then call pipeshub_get_record_content. Response: hits[] (recordId, recordName, score, snippet, mimeType, webUrl) sorted by score, plus uniqueRecords[] for deduped record-level info. Hits are a ranked sample, never a complete list. Never count them to answer “how many” / “all” / “every”; use mode:"navigate" instead.

​
pipeshub_get_record_content

Three operations on records, selected by mode.
  • mode: "content" — the only way to see a document’s full text. Use it to summarize, extract, or quote a named document. Prefer it over pipeshub_download_record when you need what the record says rather than the file bytes.
  • mode: "navigate" — browse the hierarchy (project / space / folder → records → children). Use it for structure and for every “how many” / “all” / “every” question. Pass depth: 2 or 3 to see several levels in one call. Returns no document text.
  • mode: "lookup" — resolve a Jira key, URL, or external ID to a recordId plus metadata.

​
pipeshub_download_record

Stream the binary content of a single record. Use it when the user wants the actual file bytes (download, attach, open).

​
pipeshub_directory

Look up people, groups, and teams. One tool with five actions.

​
pipeshub_sources

Discover available chat sources and AI models in one call. Call this once at the start of a session and cache the result. Each source id is the value to put in pipeshub_chat’s or pipeshub_search’s apps filter.

​
pipeshub_agents

List the PipesHub agents configured for this org. To converse with one, take its agentId and pass it to pipeshub_chat. Route on toolsets / knowledge, not the name. Match the request to the agent whose tools can actually perform it. The list may be empty — for plain Q&A, use pipeshub_chat without agentId.

​
Quick Decision Guide