runelay+BufferIntegration · API key
Buffer on Runelay, an open source MCP gateway
Connect Buffer once. Claude Code, Cursor, Codex and Grok all use that connection, and the credential never leaves your server.
What this connection does
Posts agendados, ideias e métricas das redes sociais. Runelay connects to the Buffer remote MCP server at https://mcp.buffer.com/mcp and puts its tools behind your own endpoint.
Agents find them with search_tools and run them with call_tool, so the Buffer tool list is not loaded into context until it is needed.
Connect Buffer
Create a token
Create a personal access token at publish.buffer.com/settings/api with the access you want your agents to have.
Paste it in the panel
Pick Buffer from the catalog in the connectors and paste the token.
Done
The token is stored encrypted on your server. Every agent with a Runelay key can use the connection.
Use Buffer in your agents
Agents do not need a Buffer entry of their own. Point each one at Runelay and Buffer is there.
Questions
Does my Buffer credential reach the agent?
No. It stays on your Runelay server, encrypted with AES-256-GCM using your RUNELAY_SECRET. Agents only hold their Runelay key.
Do I connect Buffer once per agent?
No. You connect it once in Runelay, and every agent that points at your endpoint uses the same connection.
I already have Buffer set up in an agent. Can I bring it?
Yes. runelay migrate reads the MCP servers your agents already have. If the CLI can read the token it arrives connected; otherwise it waits in the reconnect queue in the panel.