MCP setup guide
Connect Brainy Social to your AI client
Brainy Social is a remote MCP server. Any client that speaks MCP over Streamable HTTP can read your Brand Brain and, with publishing access, create, schedule and track posts. Pick your client below and copy the config.
November 19, 2026
MCP server URL
https://brainy-social.com/api/mcpTwo ways to sign in
- Sign in (OAuth): the client opens Brainy Social, you sign in, choose one workspace and the access (read, or read and publish), and click Allow. Nothing to copy. Best for people.
- Agent API key: a
bsk_…key sent asAuthorization: Bearer …. Best for headless agents, CI jobs and clients without sign-in.
Create an agent API key
- In Brainy Social open the gear menu → AI & MCP → MCP server → Agent API keys (owners and admins).
- Name the key after the agent that will use it, choose Read only or Read and publish, and an expiry (or never).
- Click Create key and copy it: it is shown once. Only a hash is stored; the list shows its first characters and when it was last used.
- A key works for one workspace and acts as the person who created it, with their current role. It stops if they leave, are suspended, or when it expires.
- Revoke a key on the same page at any time: agents using it lose access immediately.
- Keep keys in a secret store or an environment variable, never in a shared repository. The examples below use a placeholder, not a real key.
Claude (claude.ai and Claude Desktop)
Settings → Connectors
- Open Settings → Connectors → Add custom connector.
- Paste the MCP server URL, click Add, then Connect.
- Sign in to Brainy Social, choose the workspace and the access, then click Allow.
With an API key instead, Claude Desktop runs the server through the mcp-remote bridge in claude_desktop_config.json:
Agent API key{
"mcpServers": {
"brainy": {
"command": "npx",
"args": [
"-y",
"mcp-remote",
"https://brainy-social.com/api/mcp",
"--header",
"Authorization:${BRAINY_AUTH}"
],
"env": {
"BRAINY_AUTH": "Bearer bsk_EXAMPLE_not_a_real_token"
}
}
}
}ChatGPT
Settings → Apps & Connectors
- Turn on developer mode, then open Settings → Apps & Connectors → Create.
- Paste the MCP server URL and choose OAuth as the authentication.
- Click Connect, sign in to Brainy Social, choose the workspace and the access, then click Allow.
ChatGPT connects with sign-in only. For your own code, use an agent API key with the REST API or a raw MCP call.
Claude Code
Terminal
Sign in (OAuth)claude mcp add --transport http brainy https://brainy-social.com/api/mcp
# then, inside Claude Code: /mcp → brainy → AuthenticateAdd --scope project to share the server through .mcp.json (never commit a key; use the sign-in flow there).
claude mcp add --transport http brainy https://brainy-social.com/api/mcp \
--header "Authorization: Bearer bsk_EXAMPLE_not_a_real_token"Cursor
~/.cursor/mcp.json (or .cursor/mcp.json in a project)
Sign in (OAuth){
"mcpServers": {
"brainy": {
"url": "https://brainy-social.com/api/mcp"
}
}
}Without headers Cursor shows a Connect / Needs login button for the sign-in flow.
Agent API key{
"mcpServers": {
"brainy": {
"url": "https://brainy-social.com/api/mcp",
"headers": {
"Authorization": "Bearer bsk_EXAMPLE_not_a_real_token"
}
}
}
}VS Code (GitHub Copilot agent mode)
.vscode/mcp.json (or MCP: Add Server…)
Sign in (OAuth){
"servers": {
"brainy": {
"type": "http",
"url": "https://brainy-social.com/api/mcp"
}
}
}With the API key config VS Code asks for the key once and stores it in its secret storage.
Agent API key{
"inputs": [
{
"type": "promptString",
"id": "brainy-api-key",
"description": "Brainy Social agent API key",
"password": true
}
],
"servers": {
"brainy": {
"type": "http",
"url": "https://brainy-social.com/api/mcp",
"headers": {
"Authorization": "Bearer ${input:brainy-api-key}"
}
}
}
}Codex (CLI and IDE extension)
Terminal, or ~/.codex/config.toml
Sign in (OAuth)codex mcp add brainy --url https://brainy-social.com/api/mcp
codex mcp login brainySign-in needs a browser. On a headless machine use the API key: Codex sends the variable's value as the Bearer token.
Agent API key# ~/.codex/config.toml
[mcp_servers.brainy]
url = "https://brainy-social.com/api/mcp"
bearer_token_env_var = "BRAINY_API_KEY"
# in the shell that starts Codex:
export BRAINY_API_KEY=bsk_EXAMPLE_not_a_real_tokenWindsurf
~/.codeium/windsurf/mcp_config.json (Cascade → MCP servers → View raw config)
Sign in (OAuth){
"mcpServers": {
"brainy": {
"serverUrl": "https://brainy-social.com/api/mcp"
}
}
}Windsurf signs in when the config has no headers. On Teams and Enterprise an admin may need to allow remote MCP servers.
Agent API key{
"mcpServers": {
"brainy": {
"serverUrl": "https://brainy-social.com/api/mcp",
"headers": {
"Authorization": "Bearer bsk_EXAMPLE_not_a_real_token"
}
}
}
}Any stdio-only client (the mcp-remote bridge)
The client's MCP config file
Sign in (OAuth){
"mcpServers": {
"brainy": {
"command": "npx",
"args": [
"-y",
"mcp-remote",
"https://brainy-social.com/api/mcp"
]
}
}
}mcp-remote runs locally with Node.js, speaks stdio to your client and Streamable HTTP to Brainy. Without a header it opens your browser for sign-in; with one it sends your key. The key goes in an env variable because some clients split arguments on spaces.
Agent API key{
"mcpServers": {
"brainy": {
"command": "npx",
"args": [
"-y",
"mcp-remote",
"https://brainy-social.com/api/mcp",
"--header",
"Authorization:${BRAINY_AUTH}"
],
"env": {
"BRAINY_AUTH": "Bearer bsk_EXAMPLE_not_a_real_token"
}
}
}
}Headless agents without an MCP client
The server is plain JSON-RPC over HTTPS POST (stateless, no session): an agent can call a tool directly with its key. For publishing from your own code, the REST API in the developer docs takes the same key.
curl -s https://brainy-social.com/api/mcp \
-H "Authorization: Bearer bsk_EXAMPLE_not_a_real_token" \
-H "Content-Type: application/json" \
-d '{"jsonrpc":"2.0","id":1,"method":"tools/call","params":{"name":"get_brand_prompt","arguments":{"language":"en"}}}'If it doesn't connect
- 401: the key is wrong, revoked or expired, or the sign-in was disconnected. Create a new key, or connect again.
- 403 "MCP access isn't included in this workspace's Brainy Social plan": upgrade to a plan with MCP.
- Publishing tools missing: the key or connection has read access only. Create one with Read and publish.
- Browser-based clients on another site are refused (Origin check); desktop, CLI and server clients send no Origin and are fine.