Follow Through
v1.0.0A powerful MCP server built with NitroStack
Add via Cursor Settings UI (Settings > Features > MCP > Add New MCP Server):
{
"mcpServers": {
// your other mcp servers
"follow-through": {
"url": "https://followthrough-6a6ceb6a-team-metalodians-srmist.app.nitrocloud.ai/mcp"
}
}
}
Connect remote tools directly via Claude's Web UI:
Configure custom tools directly via ChatGPT's Web UI:
Add the following configuration block under mcpServers in your Antigravity configuration file (~/.gemini/config/mcp_config.json):
{
"mcpServers": {
// your other mcp servers
"follow-through": {
"serverUrl": "https://followthrough-6a6ceb6a-team-metalodians-srmist.app.nitrocloud.ai/mcp"
}
}
}
Add the following configuration block to your Codex configuration file (~/.codex/config.toml):
[mcp_servers.follow-through] url = "https://followthrough-6a6ceb6a-team-metalodians-srmist.app.nitrocloud.ai/mcp"
Connect directly using the Server-Sent Events endpoint:
https://followthrough-6a6ceb6a-team-metalodians-srmist.app.nitrocloud.ai/mcp
Parses a meeting transcript and returns structured commitment objects: who promised what, to whom, by when, and with what confidence. For every commitment found it immediately creates a durable store record AND a Linear ticket — catching the 90% of commitments that would never become a manual ticket. Deduplicates against commitments already in the store.
Returns a ready-to-use sample meeting transcript (with participants and meeting date) designed to exercise all three confidence levels — paste its transcript_text into extract_commitments to run the demo flow.
Creates or updates a commitment record in the durable store. The store is the source of truth for every commitment lifecycle state.
Returns commitments matching a filter — used by the scheduler to find items due for a poll or nudge check. With no filters, returns every commitment.
Promotes a logged aspirational commitment ("we should probably...") so the scheduler starts actively chasing it. This is the human override that moves an idea into the follow-up loop.
Searches Slack for messages that could constitute evidence a commitment was fulfilled. Returns raw candidate messages; the verification agent scores them semantically rather than trusting keyword hits.
Searches a mocked inbox/sent-items store for emails relevant to a commitment — e.g. mail sent to an external beneficiary that proves the work shipped.
Sends a contextual reminder to the commitment owner via Slack or email, referencing the original commitment language and deadline. Tone calibration: gentle first, specific second, urgent only on hard blockers.
Creates a Linear ticket for a newly extracted commitment so it's never lost — even commitments nobody manually ticketed. Keys stay server-side in the Linear service; this tool never exposes them to the model.
Reads the current status of a Linear ticket — used by the scheduler to verify work marked Done in Linear, not just in Slack/email.
Updates the status of a Linear ticket. Lets the scheduler pick up a ticket manually marked Done.
Adds a manager as a watcher on the ticket with a supportive, context-rich comment explaining what was promised, what has been tried, and why it is being surfaced now.
Advances the internal clock by N days and runs one scheduler poll. This is the demo control that makes a week of chasing observable in seconds. In production the scheduler polls itself on a real interval (SCHEDULER_INTERVAL_MS) — this tool exists so the full open → nudge → escalate lifecycle can be shown live.
Wipes the commitment store, ticket store, and resets the virtual clock to today. Use this to restart the demo scenario cleanly.