cursor-agent-bridge
Enables MCP clients like Claude Code to delegate coding tasks to the local Cursor Agent CLI, with persistent per-workspace sessions that resume across calls.
README
cursor-agent-bridge
An MCP server that lets Claude Code (or any MCP client) hand off coding tasks to the local Cursor Agent CLI, running in a specific project workspace. Each workspace gets its own persistent Cursor session that automatically resumes across calls, so Cursor remembers prior turns for that project even after you've worked on other projects in between.
Useful for running Claude and Cursor side by side on the same codebase — Claude plans and reviews, Cursor executes, and both stay in sync per project.
Setup
{
"mcpServers": {
"cursor-agent-bridge": {
"command": "node",
"args": ["/path/to/cursor-agent-bridge/index.js"]
}
}
}
Requires the cursor-agent CLI installed and on PATH (or set
CURSOR_AGENT_PATH).
Tools
- cursor_agent_delegate — send a prompt + workspace path to Cursor Agent, resuming that workspace's session if one exists.
- cursor_agent_sessions — list all workspaces with an active/remembered session and when they were last used.
How it works
This bridge delegates project-scoped coding work to the local Cursor Agent CLI.
Shell and SSH permission
File editing is the default mode. Unrestricted shell commands, SSH, and network access are disabled unless the caller opts in for an individual tool call.
A calling Claude or GPT agent must:
- Explain that enabling shell mode lets Cursor run local and remote commands without further approval.
- Ask the user for explicit permission in the current conversation and wait.
- Set both
allow_shell: trueandshell_permission_confirmed: trueonly after approval.
Permission is per call and must not be inferred from an earlier task. When
enabled, the bridge launches Cursor with --force --sandbox disabled, allowing
it to use the Mac's SSH configuration, credentials, and Tailscale routes.
Clients that already loaded the MCP server must restart or reconnect it to see schema or implementation changes.
Timeout
Each call defaults to a 10-minute timeout. Any calling AI (Claude, ChatGPT,
etc.) can raise this per call via the timeout_ms parameter, up to a hard
cap of 60 minutes.
Recommended Servers
playwright-mcp
A Model Context Protocol server that enables LLMs to interact with web pages through structured accessibility snapshots without requiring vision models or screenshots.
Magic Component Platform (MCP)
An AI-powered tool that generates modern UI components from natural language descriptions, integrating with popular IDEs to streamline UI development workflow.
Audiense Insights MCP Server
Enables interaction with Audiense Insights accounts via the Model Context Protocol, facilitating the extraction and analysis of marketing insights and audience data including demographics, behavior, and influencer engagement.
VeyraX MCP
Single MCP tool to connect all your favorite tools: Gmail, Calendar and 40 more.
graphlit-mcp-server
The Model Context Protocol (MCP) Server enables integration between MCP clients and the Graphlit service. Ingest anything from Slack to Gmail to podcast feeds, in addition to web crawling, into a Graphlit project - and then retrieve relevant contents from the MCP client.
Kagi MCP Server
An MCP server that integrates Kagi search capabilities with Claude AI, enabling Claude to perform real-time web searches when answering questions that require up-to-date information.
E2B
Using MCP to run code via e2b.
Neon Database
MCP server for interacting with Neon Management API and databases
Exa Search
A Model Context Protocol (MCP) server lets AI assistants like Claude use the Exa AI Search API for web searches. This setup allows AI models to get real-time web information in a safe and controlled way.
Qdrant Server
This repository is an example of how to create a MCP server for Qdrant, a vector search engine.