ContentIn — LinkedIn Ghostwriter

io.contentinPublished by contentin.ioOfficial publisherv1.1.0Updated Nov 7, 2026

Write LinkedIn posts in your voice: ideas, drafts, scheduling, analytics from your personal AI.

VerifiedStreamable HTTPWeb executableProductivity & WorkflowCommunication & Collaboration

Overview

AI-generated overview

A remote LinkedIn ghostwriting server that lets an assistant draft posts in your voice, plus ideas, scheduling and analytics.

What you can do
  • Draft LinkedIn posts in your own voice from ideas and prompts
  • Generate post ideas and turn them into drafts
  • Schedule posts for publishing
  • Review analytics on published posts
  • Connect through a hosted endpoint rather than a local install
When to use it
Useful if you regularly publish on LinkedIn and want an assistant to help brainstorm, draft, schedule and review posts without leaving the chat.
Requirements
Remote endpoint at mcp.contentin.io over streamable HTTP. Authentication is required: OAuth where the client supports it, otherwise a ContentIn MCP key supplied in the X-MCP-Key header, obtained from the ContentIn app under Profiles then Connections. A ContentIn account is implied.
Before you install
The server publishes to your LinkedIn presence, so drafts and scheduled posts should be reviewed before they go out. It requires a ContentIn account and an MCP key or OAuth sign-in; treat the key as a secret. Post content and account data are handled by the third-party ContentIn service.

Installation

In SourceWeft

  1. Open ContentIn — LinkedIn Ghostwriter in the dashboard and add it to a workspace.
  2. Connect the required credentials. They are stored privately and never shown on public pages.
  3. Enable the server for the chats that should use its tools.

Web executable via Streamable HTTP. Remote servers run from the web runtime once configured in a workspace.

Use with an agent

Paste this prompt into Claude Code, Codex, Cursor or another agent — or into SourceWeft chat. The agent reads this server's install guide, shows you its publisher, endpoint and sign-in, and adds it to your client once you agree. Keys never go into a command.

Read https://sourceweft.com/mcp/io.contentin%2Flinkedin/install.md and connect the MCP server it describes to my client. Before changing any config, show me its publisher, endpoint and sign-in method and wait for my OK. Never put an API key in a command or in a file I would commit; ask me where it should come from.

Read the install guide the agent follows

Other MCP clients

Add this to your client's mcpServers config. The client completes OAuth sign-in on first connect.

{
  "mcpServers": {
    "contentin-linkedin-ghostwriter": {
      "type": "http",
      "url": "https://mcp.contentin.io/mcp-server"
    }
  }
}

Tools

0
This server asks you to sign in, so SourceWeft could not read its tools without an account and has not indexed them. What a connected account sees can depend on that account and its permissions.

Version history

2
  1. v1.1.0LatestNov 7, 2026
  2. v1.0.0Sep 16, 2026

Score

83% of the applicable checks met

How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.

  • Reached in the last 30 daysRequired25 pts
  • Auth declaredRequired10 pts
  • Tools listed15 pts

    Answer tools/list without a credential, or ship a package that starts in a sandbox without one.

  • DescriptionRequired15 pts
  • Logo10 pts
  • Documentation15 pts
  • LicenseNot applicable

    A hosted service is used under its provider's terms, so no license is expected here. This check is left out of the percentage.