Skip to main content

Plugin

The PipesHub plugin for Cursor adds the PipesHub MCP server with no token in Cursor’s config, the PipesHub documentation search server, the PipesHub skill, and setup and ask commands. It is not yet listed in Cursor’s public marketplace.
  1. A Cursor team admin imports the repository as a team marketplace: Dashboard → Plugins & MCPs → Team Marketplaces → Add Marketplace → Import from Repo, with https://github.com/pipeshub-ai/mcp-server (the repository root).
  2. Each developer installs PipesHub from Customize, unless the admin sets it Default On or Required.
  3. Sign in. Run the setup command, or these yourself:
    1. npx -y -p @pipeshub-ai/mcp pipeshub login --no-wait (add --url https://<your-instance> when self-hosted; PipesHub Cloud is the default). It prints a link and a code.
    2. Open the link and approve with the code.
    3. npx -y -p @pipeshub-ai/mcp pipeshub login --wait.
  4. Reload the Cursor window, or turn the pipeshub server off and on, so it picks up the sign-in.
To configure Cursor by hand instead, use one of the options below.

OAuth app

Cursor supports static OAuth for remote MCP servers via the auth object in mcp.json.
Before you start, create an OAuth app in PipesHub and note your Client ID and Client Secret. See MCP Server Overview.
Coding agents: read For coding agents first. If they have no PipesHub yet, start on PipesHub Cloud, or self-host with the Local Docker demo (do not scaffold LangChain). MCP config is not enough — also install the skill into this repo (npx skills add pipeshub-ai/mcp-server) and append the AGENTS.md snippet on that page. Otherwise the next chat still invents RAG.

Configuration

Open Cursor Settings > Tools and Integrations > New MCP Server, or edit your project’s .cursor/mcp.json:
Cursor discovers the authorization and token endpoints from PipesHub’s OAuth metadata.
If the scopes field is omitted, Cursor requests the scopes_supported it discovers from the server’s OAuth metadata. To limit access, explicitly list only the scopes you need. You can also control which scopes are exposed server-side. See Customizing Default Scopes.

Using Environment Variables

Use Cursor’s ${env:VAR} interpolation to keep secrets out of config files:

Redirect URIs

Cursor’s static OAuth uses fixed redirect URIs. Register the one for the way you sign in, or both: Add them as allowed redirect URIs when creating the OAuth app in PipesHub.

OAuth Login Troubleshooting

If Cursor’s internal browser fails to load the OAuth login page, copy the authorization URL from the internal browser and paste it into your normal browser to complete the login flow.