Investigate a reported issue beside the code, or run a customer workflow without a repository. Pathbound gives Cursor current profiles, timelines, conversations, and product activity through one MCP connection.
Cursor is useful beside a repository, but it is no longer limited to one. The same customer tools can support an interactive investigation or a recurring operational job.
Bring the account record, recent events, and support history into the same thread as the product code and logs.
Use the same <code>mcp.json</code> connection from the terminal for interactive work or a controlled headless process.
Schedule a customer review or trigger one from another system. Cursor supports Automations with no repository attached.
The one-click link installs the remote server definition. Use the manual path when you want to review or share the configuration yourself.
Select Add to Cursor above, or merge this entry into ~/.cursor/mcp.json. Use .cursor/mcp.json only when the server definition should travel with a specific repository.
{
"mcpServers": {
"pathbound": {
"type": "http",
"url": "https://mcp.pathbound.ai/mcp"
}
}
}In Cursor, open the Pathbound MCP entry and authenticate. From Cursor Agent CLI, run the login command below. Your browser opens the Pathbound authorization flow; no API key needs to be pasted into an interactive configuration.
Confirm that Pathbound is enabled and inspect the live tool catalog before asking it to retrieve a known customer.
cursor-agent mcp login pathbound
cursor-agent mcp list
cursor-agent mcp list-tools pathboundCursor documents remote Streamable HTTP servers, OAuth, global and project configuration, and CLI MCP commands in its MCP reference and CLI reference.
Pathbound resolves the customer identity before Cursor asks for it. Cursor can work from that record alongside the other tools your team has approved.
Find the contact, read the product timeline and conversations, and separate observed customer evidence from assumptions about the root cause.
Compare product activity across periods, inspect the companies behind material changes, and return the affected accounts with supporting evidence.
Draft a support response, escalation, test plan, or product brief from the current customer record. Keep sending and production writes behind a separate approval.
Create an Automation in Cursor, leave the repository field empty, enable Pathbound, and begin with a schedule you can review. Add external triggers only after the output is stable.
Cursor documents no-repo templates for customer health, product analytics, product FAQ, finance, and Slack digests in its Automations release notes.
Every Monday, review customer activity from the last 7 days.
Use Pathbound to:
1. Compare activity by event type and company with the prior 7 days.
2. Retrieve the company and recent contact activity behind material changes.
3. Return the evidence, affected customers, and open questions.
Read only. Do not update customer records or send messages.Cursor asks for approval before running MCP tools by default in an interactive session. Keep that boundary in place while testing Pathbound, and keep a no-repo Automation read-only until its queries and output have been reviewed.
For a headless runner, create a Pathbound REST API key with only the required read scopes. Do not place the key in a versioned .cursor/mcp.json. Enable individual write or send tools only when the workflow has an explicit owner and approval path.
Yes. Cursor Automations can run with no repository attached. Add Pathbound as an MCP, choose it for the Automation, then give the workflow a schedule or trigger. This is useful for customer-health reviews, product-activity summaries, and support research.
Cursor Agent CLI reads the same mcp.json configuration as the desktop app. A global entry in ~/.cursor/mcp.json is available across workspaces on that machine. Team administrators can also distribute approved MCP servers through a team marketplace.
For an interactive session, add the Pathbound URL and complete OAuth from Cursor or with cursor-agent mcp login pathbound. For a headless workflow that cannot open a browser, use a scoped Pathbound REST API key as a bearer credential.
The recurring workflow can be written in plain language and run without a repository. An administrator should configure the MCP connection, credential, triggers, and allowed tools before sharing it with support, customer success, or operations teams.
Only when the Pathbound credential allows the relevant write tool. Start with read-only customer, company, conversation, and event access. Enable individual write paths only after the workflow and approval boundary are reviewed. Versioning and rollback are not live yet.
Sign up, connect one CRM or drop the events snippet, and point your MCP client at mcp.pathbound.ai/mcp.