Agile CRM

@agile-crm list all contacts created in the last 30 days and show me their tags and lead scores

Found 47 contacts created since January 15. Here's a summary: 12 contacts tagged 'enterprise-trial' (avg score 68), 18 tagged 'webinar-signup' (avg score 42), 9 tagged 'referral' (avg score 55), and 8 untagged (avg score 31). The highest-scoring contact is Sarah Chen at 94 points, tagged 'enterprise-trial' and 'product-qualified'. The API returned these in creation order; I've grouped them by tag for readability.

This example shows list-and-analyze capability. The MCP returns paginated results in creation order; the AI synthesizes patterns across pages. Requires read scope on contacts. Large contact lists may hit rate limits—Agile CRM enforces 500 requests per hour on most plans.

@agile-crm create a new deal called 'Q1 Enterprise Expansion - Acme Corp' in the Sales pipeline at Discovery stage, associate it with contact ID 8472, and set the value to $45000

Created deal #3891 'Q1 Enterprise Expansion - Acme Corp' in the Sales pipeline at the Discovery milestone, valued at $45,000. Associated with contact Sarah Chen (ID 8472). The deal is now visible in your Agile CRM board and will appear in pipeline reports. Note: milestone names are case-sensitive—I matched 'Discovery' exactly as it exists in your Sales pipeline.

This example demonstrates deal creation with contact linking. The MCP validates milestone names against your account's pipeline configuration and will fail if the stage doesn't exist or is misspelled. Requires write scope on deals and contacts. Side-effect: creates a permanent record and may trigger automation rules you've configured in Agile CRM.

@agile-crm pull all deals in 'Negotiation' stage across all pipelines, then draft a weekly sales summary highlighting total value and any deals stuck for more than 14 days

Retrieved 11 deals in Negotiation totaling $287,000. Weekly summary: 7 deals progressing normally ($198K), but 4 deals have been in Negotiation for 15+ days—'Global Logistics RFP' (23 days, $62K), 'Healthcare SaaS Upgrade' (18 days, $18K), 'Retail POS Rollout' (17 days, $7K), and 'Manufacturing Integration' (16 days, $2K). Recommend follow-up on the top two stalled deals this week to maintain Q1 momentum.

This example pairs MCP data retrieval with AI reasoning to surface insights. The MCP fetches deal metadata including stage and timestamps; the AI calculates time-in-stage and prioritizes by value. Useful for sales managers who want narrative summaries instead of raw CRM exports. Accuracy depends on your team consistently updating deal stages.

When Agile CRM beats a spreadsheet for early sales

A 3-person SaaS startup fields 40-60 inbound demo requests a week from their landing page. They need to score leads, tag by vertical, and move qualified prospects into a pipeline without hiring a sales ops person. The Agile CRM MCP handles this: create contacts with tags and scoring in one call, then create deals and attach them to the right milestone. The list-contacts cursor makes it easy to surface today's hot leads in a morning standup thread. This breaks down around 200 leads per week—pagination gets slow and you'll want dedicated CRM tooling instead of an AI workspace. Below that threshold, Agile CRM in Switchy keeps your sales motion visible to the whole team without context-switching to another app.

Why this MCP works for post-sale account handoffs

A 6-person agency closes 8-12 new clients a month and needs to route each signed deal from sales to a CS owner, update contact records with onboarding notes, and track renewal milestones. The Agile CRM MCP's deal and contact tools let the team do this in Switchy: get the deal by ID, read the attached contacts, update tags or custom properties, then move the deal to the onboarding milestone. The API-key auth means any team member can trigger the handoff without waiting on an admin. This stops working well if you have complex multi-stage pipelines or need field-level permissions—Agile CRM's native UI is better there. For straightforward handoffs at small scale, the MCP keeps the workflow in one place.

When Agile CRM closes the loop on customer issues

A 5-person B2B product team uses Intercom for support and Agile CRM for account records. When a customer reports a bug or requests a feature, they want that context written back to the CRM contact so the account owner sees it before the next check-in call. The Agile CRM MCP makes this a one-step action: search for the contact by email (via list-contacts filtering), then update tags or add a note. The 10-tool scope is enough to handle create, read, update, and delete on contacts and deals without needing a Zapier bridge. This pattern falls apart if you're syncing more than 50 tickets a day—you'll hit rate limits and need a proper integration. Below that, the MCP turns support signal into account intelligence without leaving Switchy.