MCP (beta)
Beta. The MCP is part of the Siftsy Analyst API, and it is in beta. It uses the same key, scopes, and rate limits as the REST API, including the write scopes for adding posts and accounts. Tool names and response shapes can still change. The REST API at /analyst/v1 is the stable contract for warehouses and scheduled syncs. Use the MCP from a chat, not as a loader.
The Siftsy MCP is the Analyst API for an AI chat. Ask how a campaign landed, what people are saying during a viral moment, or how your posts compare with a competitor’s, and the chat answers from your team’s Siftsy workspace with scores, themes, and the quotes behind them. Paste a post link and it checks whether Siftsy already has it, and adds it if you say so.
Every post row carries stable join keys, so the chat can line Siftsy’s results up with what you already have open in the conversation, such as a campaign tracker or a creator list.
Send the key as Authorization: Bearer sk_live_… (or sk_test_…). Monitoring keys (mk_) are rejected. The server speaks streamable HTTP in stateless mode and answers with a single JSON body. There is no session and no server-sent events.
Connect
Cursor
Claude
stdio bridge
Add this under Settings → MCP, or in ~/.cursor/mcp.json. Use a key from Team Settings → API. Turn on posts:write / accounts:write for that key if the chat should be able to add posts (see Writes).
The key is a credential. Prefer a sk_test_ key while you try the connection, and do not commit the header into a repository.
First session
You do not call the tools yourself. Connect the server, then ask in plain language. A useful first message:
Use cases
These are the jobs teams use Siftsy for, written as prompts you can paste. Swap in your own collection, brand, and dates.
Measure how a campaign actually landed.
Read the room during a crisis or viral moment.
See what people say on a competitor’s posts.
Turn thousands of comments into themes, and pull the quotes that prove them.
Surface recurring questions, complaints, and requests.
Validate a hunch before you spend budget on it.
Explain the why behind engagement numbers.
Line Siftsy up with a campaign tracker you already have.
What to expect
- The model calls
whoamiandlist_collectionsso it knows the workspace. scan_postsflags where to look. Flags are not the finding.analyzeexplains why. If it is still running, the model waits and callsget_analysis. Do not tell it to poll in a tight loop.sample_commentspulls at most 25 notable comments as evidence, not the thread.export_tablereturns rows you can join onlink. Larger tables come back as a file the client can read.
If the model starts an AI search for “negative comments,” stop it. That is a filter. An AI search and a written answer share a small daily budget.
How to read the results
The tools follow the same path an analyst uses in the product: orient, add, comb, drill, evidence, export.
A few rules are built into the tool descriptions, because they are easy to get wrong:
- content is what was posted. The scores and mix bars are how commenters responded.
- Consensus is how commenters react to each other, not to the post. A thread can be negative toward the post and still high in consensus.
- Read share of comments next to share of content. 13% of comments across 92% of posts is a broad current. The same 13% on 2 of 12 posts is a flashpoint.
- Scores are 1–10. Shares are 0–1. Mix bars and
engagementRateare 0–100. Week and month keys are that period’s first day. - A filter stays fast. An AI search, and a written
answer, share a budget of 2 per minute and 10 per day. “Negative comments” is a filter, not a search. - Scan flags say where to look.
analyzesays why.
Every post row includes postId, link, platform, account (lowercase, no @), postedAt, collectionIds, and tags.
Analyze
analyze creates a 7-day analysis. It does not edit the workspace. Ask for the smallest parts that answer the question. "full" is stats, scores, content, and a sample of notable comments. It does not write an answer.
answer is not available on a comparison. The tool starts one analysis per side and tells you so. Four sides are four answers, which can hit the 2-per-minute cap, so it starts them as jobs. Check each with get_analysis. Do not retry a rate limit immediately.
A snapshot usually finishes in the same call. Anything still running comes back as a handle:
get_analysis waits up to about 20 seconds for the analysis to finish, so the model makes a few calls rather than a tight loop. The whole HTTP request shares that budget: a batch does not get 20 seconds per call. Analyses last 7 days. A later turn can reuse the analysisId. When you write the finding up, cite that id and links.appUrl so a teammate can open the same workspace.
Export and joining
When you paste a post or profile link from TikTok, Instagram, YouTube, Facebook, LinkedIn, X, Reddit, or Pinterest, the model calls check_links first. It reports whether each post is already on the team and whether each profile is a saved account. Nothing is added or charged. If something is missing, the model offers to add it to the team and waits for you to say yes. It can only add it when the key has the write scopes (see Writes). Otherwise it tells you what is missing.
match_posts takes links from your own campaign tracker or creator list and returns matchedPostIds plus a status for every link that did not match. Pass the ids to scan_posts, breakdown, or analyze. Nothing is added or charged.
export_table returns up to about 200 rows inline, with the column names (columns for an analysis, csvColumns for a scan or breakdown). Larger tables come back as a preview plus a siftsy:// resource. Reading that resource recomputes the CSV and spends another call in the same rate class. Nothing is written to S3.
sample_comments returns at most 25 notable comments. It is evidence behind an analysis, not a thread export.
Prompts
The server ships four prompts: weekly-readout, what-changed, join-my-data, and evidence-check. They tell the model which tools to call. They do not run the tools by themselves.
Writes
Writes are part of the beta. From the chat you can add a new campaign’s creator posts, the posts behind a viral moment, or a competitor’s recent posts, then analyze them in the same conversation.
These tools only appear for a key that has posts:write or accounts:write. Both scopes are off by default. A team admin turns them on per key under Team Settings → API.
Adding posts, adding an account, and refreshing spend the team’s credits, the same way Add New does in the product. Rejected links are not billed. The model asks before it adds anything. add_account always previews first (dryRun: true) and shows what it found and what it would cost; it only adds the posts after you confirm. New posts have to process before they can be analyzed. The model polls with get_content_job and can analyze them once they are complete. See Adding content.
Limits
Each tool reserves the rate class of the REST route it stands for, and the response counts against the daily byte budget. See Rate limits. POST /mcp itself is not a way around the analysis_search cap.
