Claude Desktop MCP for Social Media — Connect Nimply to the Claude App | Nimply

Name: Nimply
Author: Nimply

There is a difference between a tool you visit and a tool you live in. Claude Desktop is the second kind for many people: it is where notes get drafted, ideas get worked out, and half the day's writing happens. Adding Nimply means your social media calendar lives in that same window instead of in another browser tab you keep forgetting to check.

The connection takes whichever shape you prefer. If you like things simple, add Nimply as a connector and approve it with OAuth — done in under a minute. If you keep your tools in config files, drop a few lines into claude_desktop_config.json with an API key instead. Either way, Claude Desktop can create and schedule posts, import media, move things around your calendar, and report on performance across all eight platforms Nimply supports.

What is Claude Desktop?

Claude Desktop is Anthropic's native app for macOS and Windows — the same Claude as the website, but resident on your machine, in your dock, always a keystroke away. It supports the Model Context Protocol two ways: through the connector UI (like claude.ai) and through a local configuration file, which makes it the natural middle ground between the browser and a developer terminal.

Nimply's MCP server is remote, so Claude Desktop needs no local process or install to reach it. The app calls Nimply's tools directly, and everything it does is bounded by the workspace and permissions you connected — whether that came from an OAuth approval screen or the scopes on an API key.

What Claude Desktop can run for you

Fold publishing into your working day

You are already in Claude Desktop writing the announcement, the blog intro, the launch email. When the copy is ready, the post is one sentence away: ask Claude to schedule it, pick the channel and time, and get back to what you were doing. No context switch, no separate tool.

Reshuffle the calendar by asking

"List everything scheduled this week and move Thursday's post to Saturday" is a real request Claude Desktop can fulfill. It reads your scheduled posts from Nimply, makes the change, and tells you the new lineup — faster than dragging cards around a calendar view.

Turn an image into a scheduled post

Point Claude at an image URL and say where it should go: "Upload this to Nimply and schedule it as an Instagram post for Friday 9am." Nimply imports the media, attaches it, and books the slot — the whole pipeline happens inside one message.

Do your weekly review in the app

Instead of opening an analytics dashboard, ask. Claude Desktop pulls channel and post metrics from Nimply, so "how did last week go, and what should I double down on?" gets you numbers and a discussion about them in the same breath.

Connect Claude Desktop to Nimply

Two paths to the same place: OAuth through the connector UI (recommended), or an API key in the config file if that is how you manage your tools.

1
Add Nimply as a connector (OAuth)
In Claude Desktop, open Settings → Connectors → Add custom connector and enter https://mcp.nimply.io/mcp. A browser window opens — log in to Nimply, pick a workspace, and click Allow access. That is the whole setup.
2
Or configure it by file (API key)
Prefer file-based config? Create an API key in Nimply under Settings → Developers, then add Nimply to claude_desktop_config.json via Settings → Developer → Edit Config:
claude_desktop_config.json
```
{
  "mcpServers": {
    "nimply": {
      "type": "http",
      "url": "https://mcp.nimply.io/mcp",
      "headers": {
        "Authorization": "Bearer nim_live_YOUR_KEY"
      }
    }
  }
}
```
3
Restart and take it for a spin
If you went the config-file route, fully quit and reopen Claude Desktop — the config is read at startup. Then confirm the connection with something concrete, like asking Claude to list your connected channels or everything scheduled this week.

Frequently asked questions

Should I use OAuth or an API key with Claude Desktop?

OAuth is the recommended path — you approve access in the browser and never handle a credential. The API key route exists for people who prefer file-based configuration or want a key they can manage and revoke independently from Settings → Developers. Both end up with the same tools.

I edited the config file but the Nimply tools do not appear. Why?

Claude Desktop reads its configuration at startup, so a running app will not pick up the change. Fully quit the app (not just close the window) and reopen it.

What does a 401 error mean?

The API key was revoked, expired, or mistyped. Valid keys always start with nim_live_ — check the value in your config against Settings → Developers in Nimply, or create a fresh key.

Which platforms can I manage from Claude Desktop?

Every channel connected to your Nimply workspace: Instagram, Facebook, TikTok, YouTube, LinkedIn, X (Twitter), Pinterest, and Threads. Platform-specific tools handle details like YouTube visibility, TikTok privacy settings, and Pinterest boards.

Is this different from the claude.ai connector?

Same server, same tools, same OAuth flow — the difference is where you use it. Claude Desktop additionally supports the config-file option with an API key, which claude.ai does not.

Can Claude Desktop attach images to posts?

Yes — give it a public URL and it imports the image or video into Nimply and attaches it to a post. Uploading raw local files via presigned URLs is designed for tools that can run HTTP commands, like CLIs and IDE agents.