If you already use an AI assistant to summarize calls, draft replies, or keep deals moving, FollowClose can give that assistant direct access to your post-call follow-up workflow. Through MCP, your agent can read sales context, generate stored sequences, surface what needs to be sent today, rewrite individual steps, and export sequences into calendar or email-friendly formats without you bouncing between tools.
This matters because post-call follow-up usually breaks in the handoff between conversation and execution. The call happened, the intent is clear, but the actual sequence gets delayed, watered down, or never sent. Connecting FollowClose to an MCP-compatible agent turns that gap into a usable workflow: the agent can take the transcript or notes, create the sequence, adjust one step when needed, and tell you exactly what is due next.
Three concrete use cases
1. Turn a call transcript into a stored sequence
You finish a sales call, drop the transcript into Claude Desktop, and ask it to create a sequence for Maya Chen at Acme Corp. The agent can analyze the call first, confirm the signals are strong enough, then create the sequence in FollowClose and read it back to you with scheduled steps.
2. Run a daily follow-up check
Each morning, your agent can ask FollowClose what is due today in your timezone. Instead of scanning tabs and notes, you can ask a plain-language question like “What follow-ups do I need to send today?” and get back the actual steps, subjects, and body drafts that are ready.
3. Rewrite one weak email without rebuilding everything
If email 3 feels too soft or too long, you do not need to regenerate the whole sequence. Your agent can fetch the stored sequence, update the subject or body directly, or call the single-step regenerate tool with a concrete instruction like “make this shorter and more direct about looping in the VP.”
Quick start
Step 1 — Generate an API key
You need an active FollowClose subscription or trial.
- Open your dashboard
- Go to Settings
- Generate a new API key
- Copy it immediately — the raw key is shown once
Step 2 — Add FollowClose to Claude Desktop
Open your Claude Desktop config file:
- macOS:
~/Library/Application Support/Claude/claude_desktop_config.json - Windows:
%APPDATA%\Claude\claude_desktop_config.json
Add this MCP server entry:
{
"mcpServers": {
"followclose": {
"url": "https://followclose.com/api/mcp",
"headers": {
"Authorization": "Bearer fc_live_your_key_here"
}
}
}
}
Restart Claude Desktop after saving the file.
Step 3 — Generic HTTP MCP config
If your client is not Claude Desktop, the important pieces are:
Endpoint: https://followclose.com/api/mcp
Methods: GET, POST, DELETE
Transport: Streamable HTTP
Header: Authorization: Bearer fc_live_your_key_here
Once connected, test it with a simple prompt such as: “Ping FollowClose.”
FAQ
What can my agent actually do with FollowClose MCP?
It can analyze transcripts, create sequences, read stored sequences, list due follow-ups, mark steps sent or skipped, update a stored step, regenerate a single step with AI, and export a sequence as JSON, Markdown, ICS, or ZIP.
Do I need a paid plan for MCP access?
MCP access works on active paid subscriptions and trialing accounts. If billing lapses, existing keys stop working until the subscription returns to active or trialing.
Are API keys reusable after billing is restored?
Yes. FollowClose does not require you to generate a new key after resubscribing. Keys are blocked at verification time when billing is inactive, then resume working once the subscription is active again unless they were revoked or expired.
Can I restrict what a key is allowed to do?
Yes. Keys are scope-based. The available scopes are sequence:read, sequence:write, followups:read, and exports:create. A narrower key is the right default when an agent only needs read access or due-followup checks.
What happens if the key is leaked?
Revoke it in Settings and it stops working immediately. FollowClose stores only the hashed key value after creation, not the raw secret.
Does FollowClose log transcript text or generated email content in MCP audit logs?
No. MCP audit logs are metadata-only. They should contain tool names, timing, success or failure, and safe export metadata, not transcript text, generated email bodies, signed download URLs, or prospect identities.
What rate limits should I expect?
Per key, FollowClose currently applies 60/min and 500/day globally, plus tighter AI-tool limits of 10/min and 50/day for sequence creation, context extraction, and step regeneration. Agents should back off instead of retrying in a tight loop.
Can I use it with n8n?
Not as a first-class n8n integration yet. The current requirement is an MCP client that supports Streamable HTTP plus Bearer token auth. If your n8n setup can act as an MCP client with that transport, it can work; otherwise it is still a roadmap item.
Which tool should an agent call first for a raw transcript?
In most cases, extract_followup_context first. It is stateless and lets the agent check whether the transcript has enough usable signal before creating a stored sequence.
What is the safest setup for multiple agents?
Use one key per client or workflow. That keeps revocation clean, keeps last used timestamps meaningful, and reduces the blast radius if one environment is misconfigured.