Pipeshub

Model Context Protocol (MCP) Server for the Pipeshub API.

Summary

PipesHub API: Unified API documentation for PipesHub services.

PipesHub is an enterprise-grade platform providing:

• User authentication and management
• Document storage and version control
• Knowledge base management
• Enterprise search and conversational AI
• Third-party integrations via connectors
• System configuration management
• Crawling job scheduling
• Email services

Authentication

Most endpoints require JWT Bearer token authentication. Some internal endpoints use scoped tokens for service-to-service communication.

Base URLs

All endpoints use the /api/v1 prefix unless otherwise noted.

Table of Contents

• Pipeshub
  • Authentication
  • Base URLs
  • Installation
  • Development
  • Contributions
  • Progressive Discovery

Installation

Install the MCP server as a Desktop Extension using the pre-built mcp-server.mcpb file:

Simply drag and drop the mcp-server.mcpb file onto Claude Desktop to install the extension.

The MCP bundle package includes the MCP server and all necessary configuration. Once installed, the server will be available without additional setup.

[!NOTE] MCP bundles provide a streamlined way to package and distribute MCP servers. Learn more about Desktop Extensions.

Or manually:

1. Open Cursor Settings
2. Select Tools and Integrations
3. Select New MCP Server
4. If the configuration file is empty paste the following JSON into the MCP Server Configuration:

{
  "command": "npx",
  "args": [
    "@pipeshub-ai/mcp",
    "start",
    "--instance-url",
    "https://app.pipeshub.com",
    "--bearer-auth",
    "",
    "--client-id",
    "",
    "--client-secret",
    "",
    "--token-url",
    "/api/v1/oauth2/token"
  ]
}

claude mcp add Pipeshub -- npx -y @pipeshub-ai/mcp start --instance-url https://app.pipeshub.com --bearer-auth  --client-id  --client-secret  --token-url /api/v1/oauth2/token

gemini mcp add Pipeshub -- npx -y @pipeshub-ai/mcp start --instance-url https://app.pipeshub.com --bearer-auth  --client-id  --client-secret  --token-url /api/v1/oauth2/token

Refer to Official Windsurf documentation for latest information

1. Open Windsurf Settings
2. Select Cascade on left side menu
3. Click on Manage MCPs. (To Manage MCPs you should be signed in with a Windsurf Account)
4. Click on View raw config to open up the mcp configuration file.
5. If the configuration file is empty paste the full json

{
  "command": "npx",
  "args": [
    "@pipeshub-ai/mcp",
    "start",
    "--instance-url",
    "https://app.pipeshub.com",
    "--bearer-auth",
    "",
    "--client-id",
    "",
    "--client-secret",
    "",
    "--token-url",
    "/api/v1/oauth2/token"
  ]
}

Or manually:

Refer to Official VS Code documentation for latest information

1. Open Command Palette
2. Search and open MCP: Open User Configuration. This should open mcp.json file
3. If the configuration file is empty paste the full json

{
  "command": "npx",
  "args": [
    "@pipeshub-ai/mcp",
    "start",
    "--instance-url",
    "https://app.pipeshub.com",
    "--bearer-auth",
    "",
    "--client-id",
    "",
    "--client-secret",
    "",
    "--token-url",
    "/api/v1/oauth2/token"
  ]
}

npx @pipeshub-ai/mcp start --instance-url https://app.pipeshub.com --bearer-auth  --client-id  --client-secret  --token-url /api/v1/oauth2/token

For a full list of server arguments, run:

npx @pipeshub-ai/mcp --help

Development

Run locally without a published npm package:

1. Clone this repository
2. Run npm install
3. Run npm run build
4. Run node ./bin/mcp-server.js start --server-url --bearer-auth To use this local version with Cursor, Claude or other MCP Clients, you'll need to add the following config:

{
  "command": "node",
  "args": [
    "./bin/mcp-server.js",
    "start",
    "--server-url",
    "",
    "--bearer-auth",
    ""
  ]
}

Or to debug the MCP server locally, use the official MCP Inspector:

npx @modelcontextprotocol/inspector node ./bin/mcp-server.js start --server-url  --bearer-auth

Contributions

While we value contributions to this MCP Server, the code is generated programmatically. Any manual changes added to internal files will be overwritten on the next generation. We look forward to hearing your feedback. Feel free to open a PR or an issue with a proof of concept and we'll do our best to include it in a future release.

Progressive Discovery

MCP servers with many tools can bloat LLM context windows, leading to increased token usage and tool confusion. Dynamic mode solves this by exposing only a small set of meta-tools that let agents progressively discover and invoke tools on demand.

To enable dynamic mode, pass the --mode dynamic flag when starting your server:

{
  "mcpServers": {
    "Pipeshub": {
      "command": "npx",
      "args": ["@pipeshub-ai/mcp", "start", "--mode", "dynamic"],
      // ... other server arguments
    }
  }
}

In dynamic mode, the server registers only the following meta-tools instead of every individual tool:

• list_tools: Lists all available tools with their names and descriptions.
• describe_tool: Returns the input schema for one or more tools by name.
• execute_tool: Executes a tool by name with the provided input parameters.

This approach significantly reduces the number of tokens sent to the LLM on each request, which is especially useful for servers with a large number of tools.