Close

@Close show me all notes from the last 7 days for leads owned by Sarah, sorted by most recent first.

Here are the 12 notes from the past week for Sarah's leads: • **Acme Corp** (2 days ago): "Follow-up call scheduled for Thursday. They're interested in Enterprise tier but need board approval." • **TechStart Inc** (3 days ago): "Demo went well. Asked about API rate limits and SSO integration." • **BuildRight LLC** (4 days ago): "Not ready to move forward until Q2. Set reminder for March." [9 more notes listed with lead name, timestamp, and content preview] All notes are sorted by creation date descending. This is an illustrative example—actual note content and count will vary based on your Close account activity.

This example demonstrates the Get Notes tool's filtering and retrieval capabilities. The MCP requires a valid API key with read access to notes and lead data. Note that Close's API returns paginated results—large note sets may require multiple queries or may hit rate limits (typically 600 requests per minute).

@Close create a new lead for "Quantum Dynamics" with website quantumdynamics.io, add contact Emma Chen as CTO with email emma@quantumdynamics.io, and set status to "Potential".

Lead created successfully: **Quantum Dynamics** (ID: lead_abc123xyz) • Website: quantumdynamics.io • Status: Potential • Contact added: Emma Chen (CTO) — emma@quantumdynamics.io The lead is now visible in your Close pipeline. You can view it at close.com/lead/lead_abc123xyz. This is an illustrative example—actual lead IDs and URLs will differ in your account.

This example shows the Create Lead tool's ability to set up a new prospect with company details and contact information in one action. The MCP writes directly to your Close CRM, so this creates a real lead record. Ensure your API key has write permissions for leads and contacts. Lead status values must match your Close account's configured statuses.

@Close review all tasks due this week across the sales team, then draft a priority summary highlighting any overdue items and grouping by assigned user.

**Sales Team Task Summary (Week of Jan 13)** **Overdue (3 tasks):** • Sarah: Follow up with Acme Corp re: pricing (due Jan 10) • Mike: Send contract to BuildRight LLC (due Jan 11) **Due This Week (8 tasks):** • Sarah (3): Demo prep for TechStart, proposal review for Quantum, contract negotiation call • Mike (2): Q1 forecast update, pipeline review meeting • Jordan (3): Onboarding call for new client, feature demo, renewal discussion Recommendation: Prioritize Sarah's overdue Acme follow-up—they're in final decision stage. This summary is illustrative based on typical task data patterns.

This example combines the MCP's task retrieval with AI reasoning to synthesize actionable insights from raw CRM data. The Create Task and task-listing tools work together here. Be aware that Close's task API doesn't natively support cross-user queries—the MCP may need to fetch tasks per user and aggregate them, which can be slower for large teams.

When Close MCP beats manual CRM entry for demo follow-up

A 3-person sales team runs 8-12 product demos a week and needs call notes in Close within an hour of each call. The Close MCP's Create Call and Create Task tools let your AI assistant log the call, extract next steps from a transcript, and create follow-up tasks without opening the CRM. This works cleanly when your team already uses Close as the source of truth and demos follow a predictable format. The trade-off: if your reps need to attach custom fields or multi-thread email sequences during logging, you'll still need the Close UI for those steps. If your team closes 80% of deals in under three touches and call logging is the bottleneck, this MCP removes that friction.

Close MCP for qualifying 50+ inbound leads per week

A 5-person growth team at a B2B SaaS startup gets 50-70 inbound leads weekly from web forms and needs to route them to the right rep within 4 hours. The Close MCP's Create Lead and Get Notes tools let your AI assistant create the lead record, pull recent activity from similar companies, and assign based on territory rules you define in the prompt. This setup works when lead data is clean and routing logic is rules-based, not judgment calls. The boundary: if your qualification process requires pulling Clearbit enrichment or cross-referencing a Google Sheet of account tiers, you'll need additional MCPs or a Zapier step. If speed-to-contact is your conversion lever and your team is under 10 people, this MCP keeps leads from sitting in a queue.

When Close MCP handles post-sale SMS workflows

A 4-person customer success team manages 120 SMB accounts and sends SMS check-ins at 30, 60, and 90 days post-sale. The Close MCP's Create SMS Message tool lets your AI assistant send templated check-ins, log responses, and flag accounts that need a call based on sentiment in the reply. This works when your SMS volume is under 200 messages a month and responses follow common patterns. The limit: Close's SMS tool doesn't support media attachments or bulk sends over 50 at once, so high-touch onboarding programs or screenshot-heavy troubleshooting won't fit. If your CS motion is lightweight and SMS is a retention signal, not a support channel, this MCP automates the repetitive parts without adding a dedicated SMS platform.