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, andsetup and ask commands. It is not yet listed in Cursor’s public marketplace.
- 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). - Each developer installs PipesHub from Customize, unless the admin sets it Default On or Required.
- Sign in. Run the
setupcommand, or these yourself: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.- Open the link and approve with the code.
npx -y -p @pipeshub-ai/mcp pipeshub login --wait.
- Reload the Cursor window, or turn the
pipeshubserver off and on, so it picks up the sign-in.
OAuth app
Cursor supports static OAuth for remote MCP servers via theauth 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.
Configuration
Open Cursor Settings > Tools and Integrations > New MCP Server, or edit your project’s.cursor/mcp.json:
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.