Handbook
301-03 — MCP and Cursor
A topology sketch explaining when Python is MCP client vs when Cursor hosts LCDL as MCP sidecar.
Updated
What you will build
A topology sketch explaining when Python is MCP client vs when Cursor hosts LCDL as MCP sidecar.
Prerequisites
Files you will touch
Documentation reads only:
| Doc | Topic |
|---|---|
| MCP client | Python → MCP server (e.g. Playwright) |
| MCP sidecar | LCDL tools inside Cursor |
| Sidecar overview | Short orientation |
| Cursor integration | Rules/skills |
Step 1 — Draw two arrows
- IDE → LCDL tools (sidecar stdio server).
- LCDL script → external MCP (fetch snapshot example).
Step 2 — Policy alignment
Note organizational policies for browser, network egress, and secret storage—LCDL documents expectations; consumers enforce.
Step 3 — Smoke optional examples
Offline-first:
PYTHONPATH=src python3 examples/contracts/load_contract_spec.py
Live MCP examples stay behind docs warnings—see example READMEs under examples/mcp/.
Expected output
Team agrees which integration matches their Cursor rollout.
Common failures
| Confusion | Resolution |
|---|---|
| Mixing client vs sidecar docs | Re-read table above |
Verify
Quiz yourself: “Who owns the Playwright process?” → Consumer / MCP server, not forge_lcdl.