Skip to main content
Instead of connecting to PipesHub’s remote MCP endpoint, you can run the MCP server locally as a stdio process using the @pipeshub-ai/mcp npm package. This is useful when you prefer a local setup or need to work in environments where direct HTTP connections to the remote MCP endpoint aren’t practical.

Prerequisites

  • Node.js 20+ installed
  • A PipesHub instance URL
  • Authentication credentials: a Personal Access Token (recommended — no OAuth app setup needed) or OAuth Client ID + Secret
For the --bearer-auth flag used throughout this page, a Personal Access Token is the easiest option: create one under Developer Settings > Personal Access Tokens and use it directly — no OAuth app, redirect URIs, or token exchange required.

Placeholders

Replace these in all configurations below:

Claude Desktop

Claude Desktop has its own dedicated guide, since it can’t connect to a local HTTP MCP endpoint and needs either a custom connector (hosted) or this stdio bridge. See Claude Desktop for the full setup.

Cursor

Open Cursor Settings > Tools and Integrations > New MCP Server, or edit your project’s .cursor/mcp.json:

Claude Code CLI

Gemini CLI

VS Code

Open Command Palette > MCP: Open User Configuration, then add:

Windsurf

Open Windsurf Settings > Cascade > Manage MCPs > View raw config, then add:

Running from Source (Development)

To run the local MCP server from a cloned repository instead of the npm package:
For MCP client configuration, replace npx @pipeshub-ai/mcp with node ./bin/mcp-server.js:
To debug with MCP Inspector:

CLI Help

For a full list of server arguments: