The Buffer connector.
Social channels, queued posts and post metrics. Connect once with your own key. Every agent your team runs reads the same 6 tools under one permission model.
How access is governed
6
Read tools
Open by default. They run when called, and every call is logged with the endpoint, tool and capability.
0
Write tools
Buffer exposes no write tools. Nothing it does mutates external state.
0
Destructive tools
Buffer defines no destructive tools. Nothing here deletes data.
Defaults come from the capability on each tool definition, and an admin can tighten or open any tool individually. The endpoint's capability ceiling can only tighten that policy. An endpoint scoped to read never surfaces a write tool.
Every Buffer tool
6 tools, named as the agent sees them.
- get_accountread
Get the Buffer account and its organizations (id, name, channel count). Call this first when the workspace has more than one organization — every other tool is scoped to one.
- list_channelsread
List connected social channels with id, service (twitter, linkedin, instagram…), display name and queue state. Channel ids feed list_posts and get_post_metrics.
- list_postsread
List posts — drafts, scheduled, sent or errored — newest first. Filter by channel or status to answer "what is queued this week" or "what went out".
- get_postread
Get one post with its full text and per-post performance metrics (impressions, reactions, comments — the set varies by network).
- get_post_metricsread
Get aggregate post performance over a date range without paging through every post. Returns post count, reactions and comments always, plus network-specific metrics when every channel in the filter supports them.
- list_ideasread
List saved content ideas from the Buffer idea board, with their text, title and intended services.
Use it from any agent
The same Buffer tools reach Claude Code, Cursor, Claude Desktop or your own agent through one MCP endpoint. The endpoint is scoped to a group, the token is issued per group and revocable from the dashboard, and an allowed-tool list and capability ceiling limit what it exposes. Reads run. Gated writes refuse unless an admin opens them. Destructive tools remain unavailable over MCP.
{
"mcpServers": {
"growth": {
"type": "http",
"url": "https://app.notara.ai/mcp/g/acme/growth",
"headers": {
"Authorization": "Bearer ntr_mcp_xxxxxxxxxxxxxxxxxxxx"
}
}
}
}The URL and token are placeholders. Real endpoints are issued per group from the dashboard.
Setup
- 01
Create a Buffer API Key in your Buffer account (where to find it). The key is yours: Notara stores it encrypted and never sees a bill.
- 02
Paste it into the Notara dashboard. Credentials can be scoped to the workspace or to one person.
- 03
The tools appear with their capability defaults already set. Tighten or open any of them per tool, then invite the agent to a channel or issue an MCP token.
Connect Buffer once. Use it everywhere.
Use Notara directly, or bring us the workflow that needs to be redesigned and built.