Reference
The stable contract around LeadCue’s live MCP tools.
Review connection states, workflow entry points, version behavior, data boundaries, and runtime-discovered schemas.
Connection and version states
| State | What the client can do | Required next step |
|---|---|---|
| Pending | Initialize the MCP and discover tools. Durable workspace actions return auth_required. | Open the returned sign-in URL, claim the Connection, then retry the named tool. |
| Claimed | Use the same ICP library, saved leads, and workflow state from supported clients. | Call the workflow entry point that matches the user’s current goal. |
| Expired or revoked | The private token is unusable. | Create a new Connection; never reuse or forward the old URL. |
refresh_required | Read status and diagnostic metadata, but do not continue the stale workflow. | Reconnect or start a fresh conversation, then retry retryTool. |
Start each workflow at its stable entry point
| Goal | Start here | Contract boundary |
|---|---|---|
| Check compatibility | get_leadcue_status | Use the returned release, contract version, status, and retry guidance. |
| Research a new batch | search_leads | The client explores current density first, then searches only inside the reviewed ICP and time window. |
| Avoid duplicate work | has_lead | Call as soon as a plausible personal profile URL is available, before full evidence collection. |
| Save a qualified result | save_lead | The client owns semantic judgment; LeadCue enforces deterministic integrity and deduplication. |
| Configure CMO Mode | prepare_cmo_mode | Preparation is proposal-only. Approval, activation, and each run remain separate boundaries. |
| Work with Email Outreach | get_email_outreach_status | Always follow its current nextAction; setup, sequence review, activation, and sending are separate confirmations. |
Discover schemas instead of copying them
MCP clients use tools/list to obtain the currently registered tool names, descriptions, input schemas, and supported output structure. The private Connection URL is generated by LeadCue and must never be placed in documentation, source code, logs, or screenshots.
{
"jsonrpc": "2.0",
"id": 1,
"method": "tools/list",
"params": {}
}The client normally performs this exchange automatically. A tool call can return structured states such as auth_required, refresh_required, or a workflow-specificnextAction; treat those fields as control flow, not prose to paraphrase away.
Compatibility and data boundaries
Supported coding agents include the following client examples, each with its own requirements.
Use a current Codex client with LeadCue plugin support. The Connection prompt installs or updates the bundled plugin before connecting.
Requires Claude Code 2.1.145+, Chrome or Edge, Claude in Chrome 1.0.36+, and a direct supported Anthropic plan.
Routine server releases arrive on the next request. The Connection remains token-scoped and the remote service receives no repository access.
Email diagnostics run locally. LeadCue never receives mailbox passwords, raw SMTP transcripts, or an executable supplied by the server.
LeadCue support contract updated . Runtime status remains authoritative.