Bridgeapp MCP server
{
"mcpServers": {
"bridgeapp": {
"type": "http",
"url": "https://mcp.bridgeapp.ai/mcp"
}
}
}{
"mcpServers": {
"bridgeapp": {
"type": "http",
"url": "https://mcp.bridgeapp.ai/mcp"
}
}
}{
"mcpServers": {
"bridgeapp": {
"type": "http",
"url": "https://mcp.bridgeapp.ai/mcp"
}
}
}{
"servers": {
"bridgeapp": {
"type": "http",
"url": "https://mcp.bridgeapp.ai/mcp"
}
}
}{
"mcpServers": {
"bridgeapp": {
"type": "http",
"url": "https://mcp.bridgeapp.ai/mcp"
}
}
}file .mcp.json (in your project root)file claude_desktop_config.jsonfile ~/.cursor/mcp.jsonfile .vscode/mcp.jsonfile ~/.codeium/windsurf/mcp_config.jsonversion 1.0.0
What it does
This server connects coding agents to a BridgeApp workspace via MCP, exposing tasks, chats, threads, pages, and projects under the signed-in account's permissions. It is intended for developers using AI coding agents (Claude Code, Codex, Cursor) who want to read and act on BridgeApp workspace data from within their agent.
- Retrieve a task's plan, comments, subtasks, blockers, and associated project brief to give an agent full context before starting work.
- Read a shared BridgeApp message or thread, including embedded agent transcripts, when a teammate shares it with the agent.
- Create a well-formed task in BridgeApp from an agent request, including a duplicate check before submission.
Tools this server exposes
| Tool | Does |
|---|---|
| list_projects | Lists all projects accessible to the signed-in account; an empty result confirms the connection is working. |
Before you enable it
An MCP server runs with whatever access you give it. Start with a development account rather than production, and check which tools the server exposes before you let an agent call them unattended.