# Cline MCP: Publish Social Posts From VS Code

**Source:** https://posteverywhere.ai/connectors/cline

---

# Publish social posts from VS Code with Cline

Yes. Cline adds MCP servers through a panel in VS Code, so there is no file to find.

Cline is the one client here that does not make you hunt for a config file. It exposes an MCP Servers panel inside VS Code, and you paste the same JSON block into it. No path to get wrong, no restart to remember.

Everything else works as it does elsewhere: the local server runs through npx, authenticates with your API key, and gives Cline the same 33 tools that the hosted connector gives Claude or ChatGPT.

Because Cline manages the server list itself, there is no file to keep in sync and nothing to migrate when you move machines. It is the least fragile of the four local setups for exactly that reason.

[Start your 7 day trial](https://app.posteverywhere.ai/signup)[All connectors →](https://posteverywhere.ai/connectors)Card required · $0 charged today · cancel any time

## How to connect PostEverywhere to Cline

Cline handles MCP servers through a panel rather than a file, which makes this the least fiddly setup of the four editor clients.

Before you start

- VS Code with the Cline extension installed.
- Node on your PATH, because the server is launched through npx.
- A PostEverywhere API key and at least one connected social account.
the MCP Servers panel in VS Codejson`{
  "mcpServers": {
    "posteverywhere": {
      "command": "npx",
      "args": ["-y", "@posteverywhere/mcp"],
      "env": { "POSTEVERYWHERE_API_KEY": "pe_live_YOUR_KEY" }
    }
  }
}`

- 1Get an API key from your PostEverywhere account. The same key works for the REST API and the SDK.

- 2Add the block below to the MCP Servers panel in VS Code.

- 3Restart Cline. The 33 tools appear once it reloads its MCP configuration.

## What you can ask Cline once it is connected

Cline earns its place when the announcement should happen in the same window as the work, without a context switch. Each one maps onto a real tool, covering scheduling, [AI captions](https://posteverywhere.ai/ai-content-generator) and [analytics](https://posteverywhere.ai/social-media-analytics). The [AI agents page](https://posteverywhere.ai/agents) has the full surface.

Post a release note the moment the build goes green

Draft a build-in-public update from the diff you just reviewed

Schedule a week of updates without opening a browser tab

Ask what is queued before you add anything else

Move a scheduled post that no longer fits

Find out why an overnight post failed

The publishing tools join Cline's existing set, so a task that ends in a release note can end in a scheduled post instead of a reminder to write one.

### What the tools cover

Cline gets the full 33-tool surface: scheduling, cross-posting, media upload, campaigns, analytics and account health. The practical benefit inside VS Code is that these compose with Cline's own file and terminal tools, so a task can read a changelog, write from it, and schedule the result without you assembling the pieces.

### Prompts that work, and what comes back

“Summarise this pull request as a short LinkedIn post and schedule it for the morning.”

Cline drafts from the diff you are reviewing and queues the post without a context switch.

“Queue a week of updates from these notes, one per weekday.”

It splits the notes into five posts and spaces them, rather than scheduling one long one.

“Did anything fail to publish? Retry and report.”

It checks delivery, retries failures and gives you the platform's actual error message.

## Cline MCP troubleshooting

The three things that actually go wrong, and what fixes each one.

The server appears but will not start

Almost always a malformed JSON block. The panel accepts what you paste without validating it, so check the braces and quotes carefully.

Tools are registered but Cline never uses them

Ask explicitly, naming the platform and the time. Cline is conservative about reaching for tools it has not been pointed at.

It worked yesterday and not today

Reload the VS Code window. The extension re-reads its server list on reload, and a stale process occasionally survives an update.

## What it will not do

Worth knowing now rather than after you have started a trial.

- It runs inside VS Code, so it is available when the editor is. Scheduled posts publish from our infrastructure either way.
- The server list belongs to the extension, so reinstalling Cline means adding it again.
- It is a publishing integration. Comments, messages and inbox work are outside what the tools cover.

## When to use Cline rather than another editor

Cline is the pick when you want the least setup friction of the local clients. No file path to find, no restart to remember, and it lives in an editor most people already have open.

Reference material: [Cline MCP configuration guide](https://docs.cline.bot/mcp/configuring-mcp-servers), [The Model Context Protocol spec](https://modelcontextprotocol.io). The full agent surface, including the REST API, is on the [AI agents page](https://posteverywhere.ai/agents).

## Included on every paid plan from $9/mo

The open-source server is free. You need a PostEverywhere plan for the API key, from $9 a month. One key covers the connector, the [REST API](https://posteverywhere.ai/social-media-api) and the SDK. Working in a different editor? [See all connectors](https://posteverywhere.ai/connectors), wire it up from [n8n, Make or Zapier](https://posteverywhere.ai/integrations), or read how the whole [agent setup](https://posteverywhere.ai/agents) fits together.

[Start your 7 day trial](https://app.posteverywhere.ai/signup)

## Cline MCP FAQ

### How do I connect PostEverywhere to Cline?

Get an API key from your PostEverywhere account. The same key works for the REST API and the SDK. Then: Add the block below to the MCP Servers panel in VS Code. Then: Restart Cline. The 33 tools appear once it reloads its MCP configuration. There is no plan restriction on this client.

### Can Cline post to social media?

Yes. Cline adds MCP servers through a panel in VS Code, so there is no file to find. Cline earns its place when the announcement should happen in the same window as the work, without a context switch.

### How do I add an MCP server in Cline?

Open the MCP Servers panel in VS Code and paste the JSON block. Cline handles the rest, so unlike Windsurf or Zed there is no config file path to locate and no restart needed.

### Does Cline need the hosted connector?

No. Cline uses the local open-source server through npx, authenticated with an API key. The hosted OAuth connector is for Claude, ChatGPT, Grok and Cursor.

### Will this work in any VS Code fork?

It works wherever Cline runs, since the panel belongs to the extension rather than the editor. The same JSON also works in Windsurf and Zed, though both of those want it in a file instead.

### What does it cost to use Cline this way?

The open-source server is free. You need a PostEverywhere plan for the API key, from $9 a month. Every plan has a 7-day trial and a card is required to start it.

## Other assistants

[Claude](https://posteverywhere.ai/connectors/claude)[ChatGPT](https://posteverywhere.ai/connectors/chatgpt)[Cursor](https://posteverywhere.ai/connectors/cursor)[Claude Code](https://posteverywhere.ai/connectors/claude-code)[Grok](https://posteverywhere.ai/connectors/grok)[Windsurf](https://posteverywhere.ai/connectors/windsurf)[Zed](https://posteverywhere.ai/connectors/zed)[Codex CLI](https://posteverywhere.ai/connectors/codex-cli)