Give your agent a social account
The Nylon MCP server exposes publishing, your connected accounts and every network’s limits as fourteen tools an AI agent can call. Point Claude, Cursor or any MCP client at it with a Nylon API key and the agent works against the same contract your backend does.
One key, fourteen tools, every network
The agent calls a tool, Nylon fans the work out to the connected accounts, and the result comes back on the same shape your backend already handles. These four carry most of the work; the rest cover scheduling, editing, retries and connections.
Your agent
MCP client
Nylon
one contract
idle
list_profiles
Return the accounts connected to the key, with network, handle and connection status. Every other tool addresses accounts by these ids.
list_networks
Every network’s character limits, media specs and post types, as data — so the agent writes a post that fits instead of learning the limit from a rejection.
create_post
Publish or schedule one payload across every account addressed. Returns a target per account with the network post id, permalink and error.
get_post
What happened afterwards: the post and each of its targets, including what published, what failed and why.
Say it, do not wire it
The agent picks the tool. You describe the outcome — a scheduled launch post, a caption checked before it goes out, an account that needs reconnecting — and the work happens against your connected accounts.
Post the launch note to every account at 9am tomorrow.
Point a client at it
Any MCP client works — Claude Code, Cursor, or your own. Add the server, pass a Nylon API key, and the tools appear.
Your key, your scope
The agent acts with a Nylon API key you issue and can revoke. It reaches exactly the accounts that key reaches — nothing more.
The same contract
MCP tools are a thin surface over the REST API. Anything the agent can do, your backend can do, with identical semantics.
Nothing to register
Connections still run on Nylon-managed OAuth apps, so an agent can publish without anyone registering a platform app.
{
"mcpServers": {
"nylon": {
"url": "https://mcp.nylon.dev",
"headers": {
"Authorization": "Bearer nylon_live_YOUR_API_KEY"
}
}
}
}Works with any MCP client
Nylon speaks the protocol, not a vendor's dialect. If your client can add a remote MCP server with a bearer token, it can use Nylon.
Claude Codeclaude mcp add
Cursormcp.json in the project
VS CodeCopilot agent mode
CodexCLI or config.tomlClaude Desktopvia mcp-remoteA client that can send an Authorization header talks to Nylon directly. One that only accepts OAuth — Claude Desktop and ChatGPT connectors today — works through mcp-remote, a local bridge that adds the header.
An agent with a key, not the keys to everything
Handing a model the ability to post publicly deserves a clear boundary. Here is exactly what it can reach and how to take it back.
Scoped to one key
The agent reaches exactly the accounts the key reaches. Issue a separate key for agent use and revoke it without touching your backend.
Reads are cheap, writes are explicit
The tool list marks every read read-only and every destructive tool destructive, so a client that asks before writes asks here too.
Everything is auditable
Every tool call is a line in your request log, marked MCP, with the endpoint, the status and the account it touched.
No standing platform access
The agent never holds a platform token. It holds a Nylon key, and Nylon holds the OAuth relationship.
Ship social publishing this week
Two connected accounts free forever. Every network, every endpoint, nothing to register — no card, no sales call.