Content Tools

contentin.io

Manages LinkedIn content creation, scheduling, and performance analytics.

1 endpoint8 known toolsFirst detected August 19, 2026Last detected August 19, 2026

ENDPOINT 1

https://mcp.contentin.io/mcp-server

No auth detected

MCP server metadata

Name: contentin
Version: 1.0.0

Capabilities

tools.listChanged

Known tools 8

list_posts

List the posts on this ContentIn profile — drafts, scheduled, published and ideas.

Inferred read-only

get_post_analytics

Get LinkedIn performance for one published ContentIn post: impressions, members reached, likes, comments, shares, and a derived engagement rate.

Potential side effects

write_post_in_my_voice

THE MAIN TOOL.

Inferred read-only

repurpose_post

Rewrite an existing post from a new angle, in the user's voice.

Potential side effects

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?

Potential side effects

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.

Inferred read-only

schedule_post

Queue a post for automatic publishing to LinkedIn at a given time.

Potential side effects

publish_post

Publish a post to the user's LinkedIn immediately.

Potential side effects

CONNECT WITH APPROVAL

Client installation

Review this server and its permissions before adding it. Secret placeholders must be set locally.

Codex

~/.codex/config.toml

[mcp_servers.contentin]
url = "https://mcp.contentin.io/mcp-server"
enabled = true

Claude Code

.mcp.json

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

Claude Desktop

Settings → Connectors → Add custom connector

Name: contentin
Remote MCP URL: https://mcp.contentin.io/mcp-server

Add this remote URL as a custom connector in Claude Desktop. Availability depends on the user plan and workspace policy.

Cursor

.cursor/mcp.json

{
  "mcpServers": {
    "contentin": {
      "url": "https://mcp.contentin.io/mcp-server"
    }
  }
}

Visual Studio Code

.vscode/mcp.json

Add to Visual Studio Code

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

Generic MCP

Client-specific MCP configuration

{
  "name": "contentin",
  "transport": "streamable-http",
  "url": "https://mcp.contentin.io/mcp-server"
}

MCP Inspector

Run the official MCP Inspector locally and enter the indexed Streamable HTTP endpoint.

TRUST AND VERIFICATION EVIDENCE

Trust Data Available

BuiltWith Trust API v2 evidence for contentin.io was fetched 2026-08-21T22:59:37.351Z.

Trust status Trusted

contentin.io is assessed as Trusted: Domain has an established technology history spanning over a year.

Indexed

Evidence is source-attributed and does not guarantee that a third-party server is safe. Risk labels are conservative metadata heuristics.