ContentIn — LinkedIn Ghostwriter is a remote MCP server that gives an AI agent 8 tools, among them capture_substance, generate_ideas, get_post_analytics. It answers at https://mcp.contentin.io/mcp-server over streamable HTTP, and it listed its tools to an anonymous client, so no sign-in was needed for that. Our probes reached it 6 of 6 times since 10 September 2026; the last check, on 19 October 2026, succeeded.
Write LinkedIn posts in your voice: ideas, drafts, scheduling, analytics from your personal AI.
Description as the publisher wrote it.
| Tool | What it does |
|---|---|
capture_substance | Save a piece of the user's first-party substance — a story, an opinion, a data point, or a framework — into their ContentIn content bank, filed under one of their content pillars. This is the highest-leverage thing you can do for them: ever Inputs: content_pillar, substance_type, content |
generate_ideas | Generate fresh LinkedIn post ideas for a COLD request — the user wants options but has NOT given you material of their own ('what should I post about this week?', 'ideas for [topic]'). Ideas are grounded in the user's content pillars and th Inputs: topic, content_pillar, style, count |
get_post_analytics | Get LinkedIn performance for one published ContentIn post: impressions, members reached, likes, comments, shares, and a derived engagement rate. IMPORTANT: metrics are fetched on a schedule and only for posts published through a connected L Inputs: post_id, include_history |
list_posts | List the posts on this ContentIn profile — drafts, scheduled, published and ideas. Use this to find a post's id before scheduling, publishing, repurposing or pulling analytics for it, and to answer questions about what the user has written Inputs: status, from, to, search, limit |
publish_post | Publish a post to the user's LinkedIn immediately. THIS IS IRREVERSIBLE — it is public the moment it succeeds. TWO-STEP AND MANDATORY: call it first WITHOUT confirm_token to get back the exact text that would go out and a confirm_token; sho Inputs: post_id, post_content, confirm_token |
repurpose_post | Rewrite an existing post from a new angle, in the user's voice. Pass post_id (a ContentIn post id from list_posts) to repurpose one of their own posts — the current text is read from ContentIn, so you do not need to have seen it. Pass origi Inputs: post_id, original_post, new_angle, style, content_pillar, user_constraints |
schedule_post | Queue a post for automatic publishing to LinkedIn at a given time. TWO-STEP AND DELIBERATELY SO: call it first WITHOUT confirm_token to get back the exact text and a confirm_token; show that exact text to the user, get their explicit go-ahe Inputs: post_id, post_content, post_time, title, confirm_token |
write_post_in_my_voice | THE MAIN TOOL. Write a LinkedIn post in this user's own voice, from their own material. Use it whenever the user describes something they want to post about — a story, an opinion, a result, a lesson, a rough brief. It runs ContentIn's voice Inputs: user_idea, style, user_constraints |
Every block below points at https://mcp.contentin.io/mcp-server. Pick your client and copy.
claude mcp add --transport http contentin-linkedin-ghostwriter https://mcp.contentin.io/mcp-server
{
"mcpServers": {
"contentin-linkedin-ghostwriter": {
"command": "npx",
"args": ["-y", "mcp-remote", "https://mcp.contentin.io/mcp-server"]
}
}
}{
"mcpServers": {
"contentin-linkedin-ghostwriter": {
"url": "https://mcp.contentin.io/mcp-server"
}
}
}{
"servers": {
"contentin-linkedin-ghostwriter": {
"type": "http",
"url": "https://mcp.contentin.io/mcp-server"
}
}
}{
"context_servers": {
"contentin-linkedin-ghostwriter": {
"url": "https://mcp.contentin.io/mcp-server"
}
}
}{
"mcpServers": {
"contentin-linkedin-ghostwriter": {
"serverUrl": "https://mcp.contentin.io/mcp-server"
}
}
}{
"mcpServers": {
"contentin-linkedin-ghostwriter": {
"url": "https://mcp.contentin.io/mcp-server"
}
}
}name: ContentIn — LinkedIn Ghostwriter
version: 0.0.1
schema: v1
mcpServers:
- name: ContentIn — LinkedIn Ghostwriter
type: streamable-http
url: https://mcp.contentin.io/mcp-server{
"mcpServers": {
"contentin-linkedin-ghostwriter": {
"httpUrl": "https://mcp.contentin.io/mcp-server"
}
}
}{
"mcpServers": {
"contentin-linkedin-ghostwriter": {
"type": "http",
"url": "https://mcp.contentin.io/mcp-server"
}
}
}{
"mcpServers": {
"contentin-linkedin-ghostwriter": {
"url": "https://mcp.contentin.io/mcp-server"
}
}
}goose://extension?url=https%3A%2F%2Fmcp.contentin.io%2Fmcp-server&type=streamable_http&id=contentin-linkedin-ghostwriter&name=ContentIn%20%E2%80%94%20LinkedIn%20Ghostwriter
It answered our last check on 19 October 2026 in 475 ms. Over 6 checks since 10 September 2026 it answered 6. Status here comes from Neuronto's own probes, not from the publisher.
Yes. It is published by contentin.io and served from mcp.contentin.io, the vendor's own domain: https://mcp.contentin.io/mcp-server.
8, as returned by the server's own tools/list on 12 September 2026: capture_substance, generate_ideas, get_post_analytics, list_posts, publish_post, repurpose_post, schedule_post, write_post_in_my_voice.
It answered our last check on 19 October 2026 in 475 ms. Over 6 checks since 10 September 2026 it answered 6.
Put the server under mcpServers in ~/.cursor/mcp.json with the URL https://mcp.contentin.io/mcp-server. The exact JSON is above, with the same setup for Claude Code, Claude Desktop, VS Code, Windsurf, Zed, Gemini CLI and the rest.
It listed its tools to an anonymous client, so reading the tool list needs no key. Individual tools can still ask for credentials in their own inputs.
Publisher: io.contentin. Endpoint host: mcp.contentin.io. ARD identifier: urn:air:io.contentin:mcp:linkedin.
First indexed 10 September 2026. The tools are exactly what the server returned; nothing on this page
is inferred from its name. Ranking in Neuronto search is never for sale.