Buffer
Connect Buffer to schedule and publish posts across your social channels, run the full post lifecycle, and track performance.
One Buffer personal API key, the Bearer token you paste into PopMCP's Personal API key field.
- Setup time
- 4 min
- Auth
- API credentials
- API base URL
- https://api.buffer.com
- Rate limits
- Per client: 100 requests per 15 minutes on every plan, 250 requests per 24 hours (500 on Team), and 3,000 / 7,500 / 15,000 requests per 30 days on Free / Essentials / Team.
Before you begin
- A Buffer account. Free works, and allows 1 personal key, Essentials 3, Team 5
- The key acts on your own Buffer account and reaches every organization and channel in it
- Personal keys always carry an expiry, so plan to reconnect when it lapses
Get your credentials
Open Buffer's API settings
Click the profile icon in the lower-left corner of the dashboard and choose API.
Queue
Posts scheduled across your connected channels.
The account menu sits behind the avatar at the bottom of the left rail.
Start a new personal key
Open the Personal Access tab and click + New Key in the Keys section.
API
Personal keys and OAuth clients for this Buffer account.
| Name | Key | Permissions | Status | Expires |
|---|---|---|---|---|
| ZapierPersonal key | ****91be | All | Active | Nov 2, 2026 |
| n8n workflowPersonal key | ****3d70 | All | Expiring | Sep 14, 2026 |
Free allows 1 personal key, Essentials 3, Team 5.
Name the key, keep the permissions, pick an expiry
Name the key PopMCP and leave every box under Permissions ticked. Set the expiry to 1 year, then click Generate API Key.
API
Personal keys and OAuth clients for this Buffer account.
All permissions are ticked by default.
Copy the key into PopMCP
Click Copy key in the dialog. Paste the token into PopMCP's Personal API key field and save.
API
Personal keys and OAuth clients for this Buffer account.
The value is masked on screen. Copy key still copies the whole token.
Connect in PopMCP
Open your workspace, choose Buffer in the marketplace, and fill in the connect dialog:
| Field | What to enter |
|---|---|
| Personal API keysecret | Buffer app → Settings → API → Personal Keys tab → + New Key → choose permissions + an expiry → Generate API Key → copy it. Stored encrypted; used server-side only (sent as Authorization: Bearer). The connection is locked to this key's account. Note: a personal key has an expiry (up to 1 year). Reconnect with a fresh key when it lapses.Encrypted with AES-256-GCM on save and never shown again. |
PopMCP verifies the credential against Buffer immediately. On success the connection flips to Verified and its MCP tools are provisioned.
Verify it worked
The Buffer connector in PopMCP shows Connected. Asking it to list your channels returns the social accounts you have linked in Buffer.
Troubleshooting
401 Unauthorized
Why: The key expired, was revoked, or the Authorization header lost the token.
Fix: Create a fresh personal key on Settings then API, and reconnect in PopMCP.
429 Too Many Requests
Why: You crossed one of Buffer's three windows: 15 minute, 24 hour or 30 day.
Fix: The 429 body names the window that was exhausted. Wait it out, or ask Buffer developer support for a higher limit.
Buffer refuses to create another key
Why: Your plan's key allowance is used up: 1 on Free, 3 on Essentials, 5 on Team.
Fix: Delete a key you no longer use, or upgrade the plan.
Posts land on the wrong brand
Why: The personal key spans every organization on the account.
Fix: Name the channel or organization explicitly in your prompt. The credential cannot be narrowed.
You want to revoke access later
Why: Keys and connected clients are managed in two places on the same tab.
Fix: Delete the key under Keys, or remove the entry under Active Integrations, which revokes access straight away.