Contacts+

@Contacts+ list all contacts tagged 'investor' and show me their email addresses and phone numbers

Found 4 contacts tagged 'investor' in your Contacts+ address book: 1. Sarah Chen – sarah.chen@venture.co, +1-415-555-0142 2. Michael Torres – m.torres@seedfund.io, +1-650-555-0893 3. Priya Kapoor – priya@growthcap.com, +1-408-555-0267 4. James Liu – jliu@angelnetwork.org, +1-925-555-0451 This is an illustrative example showing how the MCP retrieves contact records filtered by tag and surfaces key fields. Actual results depend on your current address book state.

This example demonstrates read-only filtering by tag and field extraction. The MCP requires OAuth2 consent with read scope for your Contacts+ account. Results are paginated; large address books may require multiple cursor-controlled requests to retrieve all matching contacts.

@Contacts+ create a new contact for Alex Rivera, email alex@startup.dev, phone +1-512-555-0329, and tag them 'founder' and 'Austin'

Created contact for Alex Rivera in your Contacts+ address book: • Contact ID: cnt_9k3m2p7q • Email: alex@startup.dev • Phone: +1-512-555-0329 • Tags: founder, Austin Both tags were applied successfully. If either tag name didn't exist, the MCP created it automatically. This illustrative example shows the structured response after a successful write operation.

This example showcases contact creation with multi-field data and automatic tag assignment. The MCP requires write scope. Non-existent tags are created on-the-fly. The returned contact ID and etag are necessary for subsequent updates or deletion, so the AI can chain operations in a single conversation.

@Contacts+ find all contacts without an email address and draft a short note explaining why keeping email current matters for our CRM sync

Found 7 contacts in your Contacts+ address book missing email addresses. Here's a suggested note: "Heads up: These contacts don't have email addresses on file, which blocks our CRM sync and prevents them from receiving automated updates. Adding emails ensures they stay in the loop for newsletters, event invites, and deal flow notifications. Priority candidates: contacts tagged 'active client' or 'board member.'" This illustrative example pairs the MCP's list-and-filter capability with AI reasoning to surface a data-quality insight.

This example combines the MCP's read tools with the AI's synthesis ability to identify gaps and draft actionable guidance. Useful for data hygiene workflows. The MCP doesn't modify contacts here—it only surfaces the list for human review. Large address books may require pagination to scan all records.

When Contacts+ beats a full CRM for seed-stage outreach

A two-founder SaaS team closing their first twenty enterprise pilots doesn't need Salesforce—they need a shared contact book that syncs across devices and lets them tag prospects by stage. Contacts+ wins here because the OAuth flow takes under two minutes, the tagging model maps cleanly to "demo scheduled" or "contract sent", and the 13-tool surface is small enough that both founders understand it in one sitting. The etag-based concurrency protection means neither founder overwrites the other's notes when they both update a contact after a call. This works until you hit roughly 200 active deals or need pipeline reporting—at that threshold, migrate to a proper CRM and archive the Contacts+ integration.

Tagging conference leads in bulk after a trade show

A three-person growth team returns from a conference with 80 business cards and wants to tag every lead with "Q1 2025 conference" before the first follow-up email goes out. The Create Tag and List Contacts tools let them script the batch operation in under ten minutes—no CSV export, no spreadsheet pivot, no manual clicking. The etag refresh requirement adds one extra GET_TAGS call per tag update, but that's negligible at this scale. This scenario breaks down above roughly 500 contacts per event because the cursor-controlled pagination in List Contacts becomes tedious, and you'd want a dedicated event-management tool with richer segmentation. For sub-200 contact events, Contacts+ is faster than any alternative.

When personal contact notes need to move between CS reps

A four-person customer success team rotates accounts quarterly and needs a lightweight way to pass context—preferred communication style, internal champion name, renewal timing—without spinning up a knowledge base. The Get Contacts and Delete Contact tools let the outgoing rep export their annotated contact list and the incoming rep import it with full profile data intact. The OAuth2 flow means each rep controls their own address book, so there's no shared-credential risk. This works for teams under roughly ten people where the contact volume per rep stays below 150 active accounts. Beyond that threshold, the lack of role-based access control and audit logs becomes a compliance gap, and you need a proper CS platform with structured handoff workflows.