SupercurveDocs
MCP

Tools

Every tool the Supercurve MCP server exposes, grouped by what it may change.

The server exposes 22 tools. Every tool except list_websites takes a website_id; when your account has exactly one website it is filled in for you, otherwise the tool answers with the options and your app asks you which one you mean.

Each tool carries the standard MCP annotations (readOnlyHint, destructiveHint), so a well-behaved client runs reads without asking and confirms every change with you first. Numbers always come with their time window and source.

Read-only

These tools never change anything in Supercurve.

ToolWhat it does
list_websitesThe websites your account can see, with the website_id every other tool takes, the organization each belongs to, and your role.
read_knowledgeCurrent Knowledge about the company: brand, products, customers, positioning, voice and strategy, with how each fact is trusted, plus the LinkedIn content pillars and the people who post for the company.
read_entityOne account, person, product or customer segment as Curve knows it, with its facts, relations and recent mentions.
list_entitiesThe companies, people, products and customer segments Curve tracks, by kind.
read_analyticsThe site's numbers across every area in one read: traffic, search, LinkedIn, AI search, competitors and the paid channels, each as a compact summary over the chosen window.
read_competitorThe research Curve keeps on one tracked competitor: what they do and sell, their market, positioning, funding, strengths, weaknesses and threat score with sources.
check_refreshHow collection is going on one data surface: which checks are queued, running, finished, skipped or failed, and when the next refresh is allowed.
read_memoryThe recent timeline of what Curve has observed and done for the company: site changes, data collected, drafts produced, decisions.
read_inboxThe Inbox: drafts, reports, heads-ups and questions Curve has produced, their status and measured results.
read_inbox_itemOne Inbox item in full: the draft or report, why Curve produced it, what it was based on, and how the team reacted.
search_conversationsYour own past conversations with Curve, including the text of files you attached.
read_conversationThe transcript of one past conversation, found with search_conversations.
read_fileThe extracted text of a file you attached in a past conversation.
read_meetingsMeeting notes synced from Granola over a lookback window.
search_contentSearch the company's content library by meaning.
ask_curveAsk Curve a question in plain words and get its full answer with sources. Curve reads knowledge, analytics, memory, Inbox and content itself. The thread is saved as a normal Curve conversation you can continue in the app. Nothing else changes.

Writes that only add or queue

Your app may confirm these before running them. None of them removes anything.

ToolWhat it does
request_refreshAsk for a fresh look at one data surface now instead of on the next scheduled check. It queues collection; use check_refresh to see when it lands. A surface refreshed in the last 15 minutes must cool down first.
set_monitor_intervalChange how often Curve checks one data surface, within each check's floor and ceiling.
create_draftHave Curve write a LinkedIn post or a blog article from a short brief, in the company's voice. It goes through Curve's quality check and lands in the Inbox for approval. Nothing is published by this call.

Writes that can also disable or remove

These are flagged destructive, so every client asks you first.

ToolWhat it does
manage_geo_promptsThe questions tracked in AI-search monitoring: add, disable (history kept), enable, or rescan one. At most 50 tracked prompts per website.
manage_competitorsThe tracked competitor list: add one by domain (research starts right away), promote a discovered candidate, or dismiss one (reversible). At most 25 tracked competitors per website.
manage_content_pillarsThe LinkedIn content pillars Curve drafts about: add, remove, or update one. The list can never be empty.

Not available over MCP

Publishing, page changes and anything that spends money on your behalf stay in the product, behind the Inbox's approval step. Curve's image generation is also not exposed here. A tool the Supercurve team has switched off is simply absent from the list your client shows.

On this page