Connection & security
A private bridge to LeadCue—not access to your repository.
Connect the GTM layer to your coding agent, install the private plugin, and learn what LeadCue stores.
Understand the Connection model
A prompt that ensures the LeadCue client plugin is current, then connects your private LeadCue URL.
Only a hash of the Connection token, plus its status and last client activity.
You can connect anonymously. Sign-in appears at the first durable action, such as saving an ICP and beginning the formal search.
An unclaimed private Connection and its sign-in claim link remain valid for seven days.
The remote MCP updates server-side. The bundled local tools update from LeadCue's self-hosted Git Marketplace; after a plugin change, start a fresh conversation. No official marketplace listing is required.
Connect in three steps
- 1
Copy the prompt. LeadCue creates it from the page you are already viewing.
- 2
Paste it into your coding agent. The client installs or updates LeadCue directly from its Git Marketplace and makes the first detectable Connection request.
- 3
Start fresh if the plugin changed. The new conversation can read the saved Trial context or help you shape a new ICP with current local tools.
Coding agents like Codex and Claude Code use the same LeadCue plugin identity. One claimed Connection keeps the account, ICP library, and saved leads.
Local email-address signals run on your machine. The remote LeadCue MCP never receives mailbox passwords, SMTP transcripts, or a command to execute.
LeadCue does not need your codebase. A public website, docs, README, or short product description is enough to start.
Clipboard activity is not a connection. The status changes only after your coding agent makes a LeadCue request.