Salesflare

@Salesflare show me all active opportunities in the pipeline with a close date this quarter, sorted by value

Here's an illustrative summary of what Salesflare would return: a list of 12 active opportunities totaling $340K in potential revenue. The top three are: Acme Corp renewal ($85K, closes March 15), Beta Industries expansion ($62K, closes February 28), and Gamma LLC new contract ($48K, closes March 22). Each entry includes contact owner, last interaction date, and current stage. This view helps prioritize outreach before quarter-end.

This read-heavy example demonstrates pipeline visibility. Requires API key with read access to opportunities and accounts. The actual response structure depends on your Salesflare account's custom fields and pipeline stages. Useful for weekly revenue reviews or forecasting discussions in a Space.

@Salesflare create a new contact for Jane Smith at Vertex Solutions, email jane.smith@vertex.co, and add her to the Q1 Outreach campaign

Contact created successfully. Jane Smith has been added to your Salesflare account under Vertex Solutions (new company record also created). She's now enrolled in the Q1 Outreach campaign, which will trigger the first touchpoint email in 24 hours. Her profile includes the email address provided and is tagged for follow-up. You can view or edit details in Salesflare's contact view.

This write example shows contact creation with campaign enrollment. Requires API key with write permissions for contacts and campaigns. Side-effect: Jane will receive campaign emails unless you pause the sequence. Confirm campaign settings before bulk operations. Rate limits apply if creating many contacts rapidly.

@Salesflare pull all interactions with contacts at TechStart Inc over the last 30 days and draft a summary email updating our account manager on engagement trends

Salesflare returned 18 interactions with TechStart Inc contacts: 7 emails (4 opened, 2 replied), 3 calls (avg 12 min), 5 LinkedIn messages, and 3 meeting notes. Key trend: engagement spiked after the product demo on January 15, with CTO and VP Engineering both responding within 48 hours. Here's a draft update: 'Hi Sarah — TechStart is showing strong signals post-demo. Technical stakeholders are engaged and asking implementation questions. Recommend scheduling a follow-up architecture review within two weeks to maintain momentum.' This synthesis combines interaction data with context for next steps.

This synthesis example pairs CRM data retrieval with AI reasoning to spot patterns and draft communications. Demonstrates how Salesflare's interaction history feeds strategic decisions. The AI interprets engagement signals but can't access private call recordings or internal notes unless explicitly shared in the Space.

When Salesflare MCP makes sense for small sales teams

A 5-person sales team closing 20-30 deals a quarter needs their CRM data in Switchy for pipeline reviews and forecast calls. The Salesflare MCP works here if your team already lives in Salesflare and you need read access to contacts, accounts, and deal stages during live conversations. The API key auth means setup takes under two minutes. The trade-off: if you're writing back to Salesflare frequently—logging calls, updating stages, creating tasks—you'll hit the limits of what an MCP can do compared to Salesflare's native UI. This MCP wins when your workflow is 80% reading CRM context and 20% updating it. If your team spends more time in Switchy than in Salesflare itself, connect the MCP and pull your pipeline into shared workspace threads.

Using Salesflare MCP for onboarding context transfer

A 3-person customer success team takes over accounts after the sales close and needs the full sales history without switching tools. The Salesflare MCP lets CS reps pull account timelines, contact notes, and deal context directly into Switchy threads during onboarding calls. This works when your handoff process is conversation-heavy and you need CRM data on-demand, not pre-exported. The boundary: if your CS team needs to update account health scores or log support tickets back into Salesflare, the MCP alone won't close the loop—you'll still open Salesflare for writes. This setup shines when onboarding calls happen in Switchy and the team references CRM data 5-10 times per call. Connect the MCP if your CS handoff lives in shared threads, not solo CRM tabs.

When Salesflare MCP is overkill for early-stage founders

A solo founder or 2-person team closing their first 10 customers often doesn't need an MCP at all. If you're tracking deals in a spreadsheet or using Salesflare's free tier with under 50 contacts, the overhead of connecting an MCP outweighs the benefit—you'll spend more time configuring access than you save in context-switching. The Salesflare MCP makes sense once you hit 100+ contacts and your sales motion repeats weekly. Before that threshold, copy-paste from Salesflare into Switchy threads or keep your CRM open in a second tab. This MCP is a time-saver at scale, not at inception. If you're still figuring out your sales process and your CRM changes shape every month, skip the MCP until your workflow stabilizes and you're closing deals on a predictable cadence.