Developers are usually the last people to post about their own work. The release ships, the changelog is written, and the social announcement sits in the someday pile — because it lives in a different tool, in a different mindset, three tabs away from where the actual work happened.
Connecting Claude Code to Nimply removes that distance. The agent already has your repo open; with Nimply's MCP tools it can also draft the post, pick the channel, and schedule the slot. "Ship notes for v2.3 are in CHANGELOG.md — draft a launch post from them and schedule it for tomorrow 10am on LinkedIn" is a complete instruction, executed where you already are.
What is Claude Code?
Claude Code is Anthropic's agentic coding tool for the terminal. It reads and edits your codebase, runs commands, and — because it is a full MCP client — extends itself with external tools registered through the claude mcp add command. Servers can be personal, or committed to a repo so the whole team shares them.
Nimply's remote MCP server is one command away. Authenticate with an API key in a header, or skip the key entirely and use OAuth from inside the session. Because Claude Code can run shell commands, it also gets the most capable media path: it can push raw file bytes from your machine straight to Nimply via a presigned upload, no public hosting required.
What Claude Code does with Nimply attached
Release announcements straight from the repo
The most accurate launch post is written by something that read the actual changes. Claude Code can summarize a diff or changelog it just worked on, draft platform-appropriate copy, and schedule it — the announcement is grounded in the code, not a marketer's secondhand notes.
A changelog-to-social pipeline
Make posting part of your release routine: after tagging a version, ask Claude Code to turn the new CHANGELOG entries into a post per channel and queue them into the next free slots. What used to be a separate marketing task becomes one more step in the ship checklist.
Publish media generated during the session
Screenshots, demo clips, charts rendered from a script — files that exist only on your machine. Claude Code requests a presigned upload from Nimply, PUTs the bytes directly, and attaches the media to a post. Nothing has to be hosted publicly first.
Debug your publishing like you debug your code
"Check Nimply for any FAILED posts this week and tell me the errors" is a natural terminal request. Claude Code lists the failures, reads the error details, and can retry or reschedule — the same investigate-and-fix loop you use on CI, applied to your content queue.
Connect Claude Code to Nimply
One command registers the server. Pick API-key auth for scriptability, or OAuth if you would rather not manage a credential.
- 1
Create an API key
In your Nimply workspace, open Settings → Developers and create a key with the scopes you want the agent to have. Keys start with nim_live_ and can be revoked independently, so give each agent its own.
- 2
Add the server
Register Nimply as an HTTP MCP server with the key in the Authorization header:
Terminalclaude mcp add --transport http nimply https://mcp.nimply.io/mcp \ --header "Authorization: Bearer nim_live_YOUR_KEY" - 3
Or authenticate with OAuth instead
No key needed if you prefer: add the server bare, then authenticate from inside a Claude Code session.
Terminalclaude mcp add --transport http nimply https://mcp.nimply.io/mcp # then inside Claude Code: /mcp # → select nimply → Authenticate - 4
Pick a scope and put it to work
Use --scope user to have Nimply available in every project, or --scope project to commit the server to .mcp.json so teammates get it too — the key itself is never shared. Then try it: ask Claude Code to list your channels or draft a post from your latest changelog.
Frequently asked questions
Do I have to use an API key, or does OAuth work in the terminal?
Both work. The API key goes in an Authorization header when you add the server — good for reproducible setups. Or add the server without a key and run /mcp inside Claude Code to authenticate with OAuth instead.
Can my team share the Nimply connection through the repo?
Yes. Adding the server with --scope project writes it to .mcp.json in your repo — without the key. Each teammate supplies their own credential, so committing the config never leaks a secret.
Claude Code says "publish now" succeeded but the post shows SCHEDULED — is something wrong?
No — publishing is asynchronous. After a publish request the post enters SCHEDULED and is processed shortly after; the agent should poll the post until it reads PUBLISHED or FAILED. This is expected behavior, not an error.
What does a 403 error with a scope name mean?
Your API key lacks that permission — for example, a read-only key cannot publish. Create a key in Settings → Developers with the needed scopes and re-add the server.
Which platforms can Claude Code publish to?
All channels connected to your Nimply workspace: Instagram, Facebook, TikTok, YouTube, LinkedIn, X (Twitter), Pinterest, and Threads — including platform-specific options like YouTube visibility and categories, TikTok privacy levels, and Pinterest boards.
The server shows as failed in /mcp — how do I debug it?
Check the URL and header spelling first — run claude mcp get nimply to inspect the stored config. A 401 usually means the key was mistyped or revoked; keys always begin with nim_live_.
Works well alongside
Ready to try it?
Create a free Nimply account, connect your channels, and you're one config entry away.