MCP server
The DialDozer MCP server translates the HTTP API into small tools that agents can inspect and call. It keeps API keys out of prompts, validates input before requests, and returns compact JSON.
Why MCP
Section titled “Why MCP”- Discoverable: agents receive tool names, descriptions, and input schemas.
- Scoped: the server can only do what its API key permits.
- Auditable: each action maps to a documented HTTP request.
- Deterministic: tools return structured resources instead of scraping UI.
Available capabilities
Section titled “Available capabilities”| Tool | API mapping | Required scope |
|---|---|---|
dialdozer_get_lead | GET leads/{id} | leads:read |
dialdozer_get_conversation | GET conversations/{id} | conversations:read |
dialdozer_send_message | POST messages | messages:write |
dialdozer_cti_lookup | GET cti/lookup | cti |
dialdozer_cti_dial | POST cti/dial | cti, agent-bound key |
dialdozer_create_lead | POST lead_intake.php | leads:write |
dialdozer_ingest_metrics | POST kpi_ingest.php | metrics:write |
Start with MCP setup, then share the agent guide with your agent runtime.