MCP connector · live now
Connect Thread Otter to your AI.
Add Thread Otter to Claude, ChatGPT, or Claude Code as an MCP connector. Then ask your AI about your GTM: it reads your project and proposes the work, in your voice. The judge, the pacing, and the ban guards stay ours, so nothing it proposes can burn your accounts.
the product works without any of this · the connector is for founders who already work inside an AI assistant
Add to your AI · no account needed
{
"mcpServers": {
"thread-otter": {
"type": "http",
"url": "https://www.threadotter.com/api/mcp"
}
}
}then ask your AI: “find buyer threads for mysite.com”
free tools, no key · full toolset with a key from Settings › MCP
Three ways to chat with Otter.
In the app
The assistant sits beside your queue. Ask what to post, who is worth a reply, or for a draft on the spot.
live · every plan
In Slack
Add Thread Otter to your workspace and mention it in your project channel. The answer lands in the thread.
live · Settings › Slack
From your own AI
Connect Claude, ChatGPT, or Claude Code over MCP. Same tools, same guardrails: it proposes, it never sends.
live · this page
One MCP server. Every agent speaks it.
A remote MCP endpoint with a project-scoped key. Add it to Claude or ChatGPT as a connector, to Claude Code as a server, or call it from any MCP client you run. No SDK, no webhook maze, no OAuth dance.
Add to your AI
{
"mcpServers": {
"thread-otter": {
"type": "http",
"url": "https://www.threadotter.com/api/mcp",
"headers": {
"Authorization": "Bearer tomcp_..."
}
}
}
}live · create a key under Settings › MCP, paste it here
Try it before you even sign up.
The same endpoint answers without a key: a small set of free tools any MCP client can call. Add the connector with no header and let your AI take Thread Otter for a spin.
find_buyer_threads
give it your website URL; it works out who your buyers are and mines recent Reddit threads where they're asking for something like it. Report in about 3 minutes.
reddit_demand_board
a weekly board of what people keep asking for across 40 startup, marketing, sales, dev, and ecommerce communities, with real threads as receipts.
subreddit_rules
any subreddit's promotion posture from our vetting data (2,000+ profiled communities), before you post the wrong thing in the wrong room.
competitor_complaints
this month's Reddit threads where people are complaining about any named product or asking for alternatives, with the threads as receipts.
demand_radar
where buyer demand ran hottest this week, six categories compared from a weekly mine of 40 communities.
No account needed
{
"mcpServers": {
"thread-otter": {
"type": "http",
"url": "https://www.threadotter.com/api/mcp"
}
}
}then ask your AI: “find buyer threads for mysite.com”
Read everything. Propose anything.
The same tools our own assistant works with, exposed to yours. Reads are instant. Writes are proposals: they land in the pipeline as drafts, never on a platform.
Reads
list_top_signals
scored buyer mentions across every watched source
read_conversation_thread
a full conversation with its draft + outcome history
list_people
the person-centric directory: signals + cold imports
read_post_performance
sends, replies, and outcomes per channel
read_product_brief
the product brief + docs the drafts are grounded in
Proposals
engage_signal
draft a reply to a signal, in the founder's voice
create_posts
brief posts as suggestions: the planner fans them out per channel
set_draft_content
submit your AI's own text into the pipeline
a stable, versioned tool set · reads are instant, writes are proposals
Your AI gets the hands, never the send button.
There is no raw send endpoint, by design. A badly prompted agent can waste its own rate limit; it cannot spam Reddit from your account. Every proposal goes through the exact pipeline autopilot uses.
That is the difference between an API that posts and one you would trust to touch your founder account.
Every write, same rails
judge · pacing · ban guards · receipts, on every proposal
MCP is live. The rest follows.
Remote MCP server
the connector above: reads + proposals for any MCP client
live nowAgent skill
install into Claude Code: our playbook baked in, so drafts follow strategy, not vibes
plannedCLI
scripts + cron: pull analytics, queue briefs from your pipeline
plannedREST API
the same surface as plain HTTPS for everything else
plannedincluded with your plan · no separate API tier
Your AI, our rails.
MCP is live today. Tell us what to build next, the CLI, an agent skill, or a REST API, and we will build against real workflows, not guesses.