LeadPipe MCP
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| LEADPIPE_DEMO | No | Set to `1` to run the in-memory demo (no Google anything). Enables demo mode as an alternative to real mode. | 0 |
| LEADPIPE_SHEET_ID | No | The pipeline Sheet's ID (required in real mode). | |
| LEADPIPE_TIMEZONE | No | IANA timezone for business hours and summaries. | UTC |
| LEADPIPE_WRITE_MODE | No | `direct`, `dry_run`, or `approval` (default: approval, direct in demo). | approval |
| LEADPIPE_CALENDAR_ID | No | Calendar to check and book (`primary` allowed) (required in real mode). | |
| LEADPIPE_BUSINESS_HOURS | No | Business hours, Monday to Friday by default. | 09:00-17:00 |
| GOOGLE_APPLICATION_CREDENTIALS | No | Path to your own service account key file; contents are never logged or returned (required in real mode). |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": false
} |
| prompts | {
"listChanged": false
} |
| resources | {
"subscribe": false,
"listChanged": false
} |
| experimental | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| capture_leadC | Record a new lead, deduplicating on email then phone before any write. |
| get_leadB | Fetch one lead by lead_id, email or phone (exactly one). |
| list_hot_leadsB | List HOT leads (score 80+), highest score first, oldest first. |
| score_leadC | Apply the deterministic scoring model. The eight component judgements are supplied by the caller; the total is computed server-side and never accepted as an input. |
| update_stageC | Move a lead to a new stage; illegal transitions are rejected. |
| check_availabilityC | Free slots on the business calendar, intersected with business hours. Busy times are returned without titles. |
| book_appointmentB | Book a calendar appointment for a lead. Availability is re-checked at call time and repeat calls never duplicate. |
| daily_pipeline_summaryB | One-call summary: counts by stage and band, hot unbooked leads, today's appointments, overdue next actions. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 8 tools
Each tool maps to a distinct operation: capturing/getting/scoring/updating a lead, listing hot leads, summarizing the pipeline, checking availability, or booking an appointment. The only potential overlap is list_hot_leads versus daily_pipeline_summary's hot-unbooked section, but the descriptions clearly distinguish a focused list from an aggregate summary.
Seven of eight tools use a predictable snake_case verb_noun pattern such as score_lead, capture_lead, and book_appointment. daily_pipeline_summary is a noun phrase rather than a verb-led name, which is a minor deviation but still readable.
Eight tools fit the lead pipeline and appointment-booking scope well, with each tool earning its place. There is no obvious padding, and the count is comfortably within the ideal range.
The surface covers core lead capture, lookup, scoring, stage transitions, hot-lead listing, daily summaries, availability checking, and booking. However, there is no general update tool for lead contact fields/owner/notes, no search or list beyond hot leads, and no appointment cancellation/rescheduling, leaving notable lifecycle gaps.