Threads Analytics
English
English繁體中文日本語
GitHub

GUIDE / MCP SERVER

Your Threads data,one question away.

Your dashboard already runs an MCP server at /api/mcp. Connect the AI agent you already use — Claude Code, Claude, Codex, Cursor — and it can read your posts, analytics, and follower history to answer questions and write reports. Read-only, and you approve every connection.

Connect your agentWhat is MCP?

About 2 minutes · No API keys · Read-only

WORKS WITHClaude CodeClaudeCodexCursor+ any MCP client
YOUR MCP ENDPOINT

https://your-deployment.example.com/api/mcp

claude mcp add --transport http threads-analytics https://your-deployment.example.com/api/mcp

Replace your-deployment.example.com with your deployed dashboard's domain.

01 / WHAT IT CAN DO

Six read-only tools. Six report prompts.

The server turns your synced data into structured tools. You ask in plain language; your agent picks the right tool and reads only what it needs.

threads-analytics · MCPREAD-ONLY
get_account_overviewSee the account at a glance

Username, sync status, post count, data range, and follower growth summary — the first call every conversation starts with.

list_posts · get_postSearch and read every post

Filter by date, media type, or text, sort by views, likes, or engagement rate, then pull any post's full text.

get_analytics31 analytics sections

Best time to post, keyword analysis, posting streaks, views distribution, and more — computed over any date range you ask for.

get_follower_historyFollow the audience curve

Daily follower snapshots with a growth summary, plus the latest country, city, age, and gender demographics.

compare_periodsCompare any two periods

Posts, views, engagement, and follower growth side by side, with absolute and percentage changes.

6 built-in promptsReports, ready to run

Performance review, content strategy, posting schedule, and three more — pick one from your client's prompt menu and get a full report back.

02 / HOW TO CONNECT

No API keys. Approve it in your browser.

Authentication is OAuth 2.1 with PKCE and dynamic client registration: the client registers itself, your browser opens your dashboard's sign-in, and you approve access on a consent screen.

  1. Copy your endpoint

    The MCP server lives at /api/mcp on the dashboard you deployed — the same domain you sign in to, nothing extra to run.

  2. Add it to your client

    One command in Claude Code or Codex, a custom connector in Claude, a URL entry in Cursor — switch between them below.

  3. Sign in and approve

    Your browser opens the dashboard login. Approve the read-only scope and the agent is connected — revoke it anytime in Settings.

One command, then /mcp

Run the one-line command — copyable at the top of this page — then run /mcp inside Claude Code and complete the sign-in when the browser opens.

The last step is always the same: authorize.

Whichever client you use, your browser opens your dashboard's sign-in. Approve the read-only scope on this screen and the agent is connected.

your-deployment.example.comOAuth

Authorize access

Claude is asking to connect to your Threads Analytics.

This will allow the agent to:

Read your posts, metrics, and analytics data

It cannot change any data or post on your behalf.

your-deployment.example.comSettings

Connected agents

MCP clients you have authorized to read your analytics data.

Claude CodeAuthorized Sep 4, 7:53 PM · Last used 8:21 PM
CodexAuthorized Sep 4, 8:08 PM · Last used 8:09 PM

Connected once, revocable anytime.

Every agent you approve shows up under Settings → Connected Agents on your dashboard, with when it was authorized and last used. Revoke wipes its tokens instantly — the client has to pass the consent screen again to reconnect.

03 / HOW TO USE IT

Ask in your own words, or start from a prompt.

Once connected, the tools appear automatically — there is nothing to configure. Ask anything about your account, or run one of the six built-in prompts; each takes an optional period like 30d or 90d.

TRY ASKING

Your agent decides which tools to call — overview first, then posts, analytics, or follower history as needed.

PROMPT MENU
performance-reviewPerformance review

Trends, your best and worst posts with likely reasons, and three concrete actions for the next period.

content-strategyContent strategy

Which formats, lengths, and topics work — and the content mix to publish going forward.

posting-schedulePosting schedule

A concrete weekly schedule built from when your audience actually engages.

viral-post-breakdownViral post breakdown

Deep-dives your outlier posts and extracts the repeatable patterns behind them.

audience-insightsAudience insights

Follower growth and demographics, and what they imply for content and timing.

topic-analysisTopic analysis

Which topics and writing patterns drive performance, plus five post ideas that apply them.

Point your agent at your own data.

Deploy the dashboard, connect the agent you already use, and your next performance report is one prompt away.

Connect your agentView on GitHub

Every connected agent shows up in Settings → Connected Agents — revoke access with one click.