DCE MCP Connector
MCP (Model Context Protocol) server for Dual Canvas Execution. Connect DCE to Cursor, Claude Desktop, Polsia, and any other MCP-compatible client. Query and update your execution data from inside your AI tools.
Available Tools
| Tool | Description |
|---|---|
bedc_get_todos | Get pending 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) |
bedc_create_topic | Create a topic |
bedc_update_topic | Update a topic |
Configuration
Set via environment variables:
| Variable | Description |
|---|---|
DCE_BASE_URL | DCE API base URL (e.g. https://app.betterexecute.com) |
DCE_API_KEY | Your org's external API key (from DCE Settings) |
DCE_ORG_ID | Organisation UUID |
Cursor Setup
Add to .cursor/mcp.json:
{
"mcpServers": {
"bedc": {
"command": "node",
"args": ["path/to/bedc-mcp/dist/index.js"],
"env": {
"DCE_BASE_URL": "https://app.betterexecute.com",
"DCE_API_KEY": "your-api-key",
"DCE_ORG_ID": "your-org-uuid"
}
}
}
}Claude Desktop Setup
Add to claude_desktop_config.json:
{
"mcpServers": {
"bedc": {
"command": "node",
"args": ["path/to/bedc-mcp/dist/index.js"],
"env": {
"DCE_BASE_URL": "https://app.betterexecute.com",
"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 APIdirectly with Polsia's custom HTTP tool.
Build & Run
cd connectors/bedc-mcp
npm install
npm run build
node dist/index.jsThe server communicates over stdin/stdout. MCP clients spawn it as a subprocess and connect automatically.