DCE MCP Server

MCP (Model Context Protocol) server for Dual Canvas Execution (DCE). Use with Polsia, Cursor, Claude Desktop, and other MCP clients.

Tools

| Tool | Description | |------|-------------| | bedc_check_config | Check DCE connection health (calls /ping) | | bedc_get_teams | List org teams with IDs and member counts | | bedc_get_members | List org members with user IDs, names, emails, roles | | bedc_get_todos | Get open to-dos | | bedc_get_topics | Get open topics | | bedc_get_meetings_latest | Get latest meeting with recap | | bedc_get_vto | Get Company Strategy and Execution plan | | bedc_get_scorecards | List scorecards (KPIs) | | bedc_get_scorecard | Get scorecard with measurables and weekly entries | | bedc_create_todo | Create a todo | | bedc_update_todo | Update a todo (status, dueDate) |

Task comments, @mentions, and file attachments are in-app only (added 2026-07). They are not yet exposed as MCP tools or over /api/external, so an agent cannot read or post task comments through this connector. Treat a task's title/status/due-date as the agent-visible surface; the discussion thread lives in the DCE UI.

| bedc_create_topic | Create a topic | | bedc_update_topic | Update a topic |

Config

Set via environment variables (DCE_* preferred; BEDC_* is still supported for backward compatibility):

| Variable | Description | |----------|-------------| | DCE_BASE_URL | DCE API base URL (e.g. https://app.dce.example.com) | | DCE_API_KEY | Your org's external API key (from DCE Settings) | | DCE_ORG_ID | Org UUID |

Cursor

Add to .cursor/mcp.json:

{
  "mcpServers": {
    "bedc": {
      "command": "node",
      "args": ["/path/to/better-execute/connectors/bedc-mcp/dist/index.js"],
      "env": {
        "DCE_BASE_URL": "https://better-execute.vercel.app",
        "DCE_API_KEY": "your-api-key",
        "DCE_ORG_ID": "your-org-uuid"
      }
    }
  }
}

Claude Desktop

Add to claude_desktop_config.json (macOS: ~/Library/Application Support/Claude/claude_desktop_config.json):

{
  "mcpServers": {
    "bedc": {
      "command": "node",
      "args": ["/path/to/better-execute/connectors/bedc-mcp/dist/index.js"],
      "env": {
        "DCE_BASE_URL": "https://better-execute.vercel.app",
        "DCE_API_KEY": "your-api-key",
        "DCE_ORG_ID": "your-org-uuid"
      }
    }
  }
}

Polsia

If Polsia supports MCP connectors, add the DCE MCP server using the same config pattern. Otherwise, use the DCE REST API directly with Polsia's custom HTTP tool if available.

Build

cd connectors/bedc-mcp
npm install
npm run build

Run (stdio)

DCE_BASE_URL=https://better-execute.vercel.app \
DCE_API_KEY=your-key \
DCE_ORG_ID=your-org-uuid \
node dist/index.js

The server communicates over stdin/stdout. MCP clients spawn it as a subprocess and connect via stdin/stdout.

Activity Tracking

This server automatically sends X-DCE-Source: mcp with every request, so your DCE Integrations Hub shows which calls came from MCP clients.