VS Code Copilot MCP — Social Media Tools for GitHub Copilot | Nimply

Name: Nimply
Author: Nimply

Copilot's agent mode changed what VS Code can do: instead of only completing code, Copilot picks up tools and carries out tasks. Which tools it has is up to you — MCP servers registered in your workspace show up in the tools picker, and Copilot can call them as part of any chat.

Nimply is a natural addition to that list for anyone who both writes software and maintains a social presence around it. A single .vscode/mcp.json file connects Copilot to your Nimply workspace, where it can check which channels are connected, draft and schedule posts, and pull analytics — covering Instagram, Facebook, TikTok, YouTube, LinkedIn, X, Pinterest, and Threads without you opening another app.

What is VS Code with Copilot agent mode?

Visual Studio Code is the most widely used code editor, and GitHub Copilot is its built-in AI assistant. In agent mode, Copilot goes beyond suggestions: it reasons through a task, edits files, runs commands, and invokes tools. VS Code's MCP support is how third-party tools enter that loop — a server declared in mcp.json becomes a set of capabilities Copilot can select and use.

Nimply exposes its MCP server as a hosted HTTP endpoint, so VS Code talks to it directly — no local process, no extension to install. Authentication is an API key from your workspace's Settings → Developers page, and VS Code's input placeholders let you supply it at connection time rather than storing it in a file, which matters when the config is committed for a whole team.

What Copilot can do with Nimply connected

Draft announcements from the code in front of you

Ask Copilot to write a post about the feature branch you just finished. Because it reads your workspace, the copy reflects what the code actually does — and with Nimply attached it can go straight into your queue as a scheduled post rather than a snippet you paste elsewhere.

Check on your channels without context-switching

A quick "list my Nimply channels and tell me which need reconnecting" in Copilot Chat surfaces expired connections before they silently break your schedule. Small maintenance tasks stop requiring a trip to the dashboard.

Review performance while you plan the next post

Copilot can pull post and workspace analytics through Nimply's tools, so you can ask what performed well recently and shape the next announcement accordingly — research and drafting in the same chat.

Share one config across the team, not one key

With the promptString input pattern, a committed .vscode/mcp.json carries no secret: each developer is prompted for their own nim_live_ key when the server starts. Everyone on the repo gets the integration; nobody inherits someone else's credentials.

Connect VS Code to Nimply

You need a Nimply account with a connected channel and an API key from Settings → Developers. The rest is one config file.

1
Create a Nimply API key
In Nimply, go to Settings → Developers and generate a key. It begins with nim_live_ and is bound to a single workspace and its permissions; revoking it takes one click.

Add the MCP server

Run MCP: Add Server from the Command Palette, or create .vscode/mcp.json in your workspace by hand:

.vscode/mcp.json

{
  "servers": {
    "nimply": {
      "type": "http",
      "url": "https://mcp.nimply.io/mcp",
      "headers": {
        "Authorization": "Bearer nim_live_YOUR_KEY"
      }
    }
  }
}

Optional: prompt for the key instead of storing it

If the config will be committed, replace the literal key with an input placeholder. VS Code asks for the key securely when the server starts:

.vscode/mcp.json

{
  "inputs": [
    { "id": "nimply-key", "type": "promptString", "password": true, "description": "Nimply API key" }
  ],
  "servers": {
    "nimply": {
      "type": "http",
      "url": "https://mcp.nimply.io/mcp",
      "headers": { "Authorization": "Bearer ${input:nimply-key}" }
    }
  }
}

4
Use it from Copilot Chat in agent mode
Open Copilot Chat, switch to agent mode, and find the Nimply tools under the tools picker. Try: "List my Nimply channels and tell me which need reconnecting."

Frequently asked questions

Why don't the Nimply tools appear in Copilot Chat?

Tools are only available in agent mode — ask mode does not call tools. Switch the chat to agent mode and check the tools picker. If the server itself failed, run MCP: List Servers, select nimply, and choose Show Output for the error detail.

Does this require anything besides VS Code and Copilot?

No local server or extension. Nimply's MCP endpoint is hosted at https://mcp.nimply.io/mcp and VS Code connects to it over HTTP using your API key. You need a Nimply workspace with at least one social channel connected.

Which platforms can Copilot publish to?

Whatever is connected in your workspace: Instagram, Facebook, TikTok, YouTube, LinkedIn, X (Twitter), Pinterest, and Threads. Copilot operates on your real posting queue through the same rules as the app.

Is it safe to commit .vscode/mcp.json to a shared repo?

Yes, if you use the inputs pattern so the file contains a placeholder rather than a key. Each teammate is prompted for their own credential. Never commit a file with a literal nim_live_ value in it.

Can Copilot publish something I have not reviewed?

Only within the bounds you set. You can direct it to create drafts rather than publish, or send posts into Nimply's approval workflow where a human approves each one. Every action is also limited by the API key's workspace permissions.