Koskamo

ContentIn LinkedIn MCP

A remote MCP server that integrates AI assistants with LinkedIn, allowing users to publish posts, schedule content, read analytics, and use a ghostwriter feature to generate posts in their own voice. It supports multiple MCP clients via a single connection scoped to a specific profile.

Visit ContentIn

Endpoint and access

OAuth sign-in: the first time you connect, your client opens the vendor's own authorization prompt in a browser.

ContentIn LinkedIn MCP logo, by ContentInVendor evidenceStreamable HTTPOAuth sign-inEndpoint checked 2026-11-06Operated by ContentIn
MCP endpoint (Streamable HTTP)
https://mcp.contentin.io/mcp-server
Vendor documentation

Checks and signals

Each line is separate evidence, not a trust score.

  • Passed Endpoint answered the live check ·
  • Passed Official MCP Registry namespace is tied to contentin.io ·
  • Passed Endpoint is on the registry namespace domain ·
  • Availability 1 of 1 checks passed in 30 days

What you can do with it

  • Publish LinkedIn posts directly from AI chat
  • Schedule posts for future publication
  • Read engagement analytics for published content
  • Generate drafts using a personalized voice model

Source and maintenance

Vendor evidenceRegistry 1.0.0
mcp-registry: io.contentin/linkedin@1.0.0Project website

Tools

Reported by the attributed source; not independently observed by Koskamo.

No tool definitions available.

90-day uptime

A lightweight connection check about every six hours, sampled on hosts with many listings. It shows the server answered, not that its tools work.

Too few checks for a percentage yet (3 of 3 answered).

  1. 2026-11-06: 1 of 1 checks answered
  2. 2026-11-07: 2 of 2 checks answered

30-day availability

Aggregated from read-only remote checks; this is not a tool-execution or security guarantee.

Successful checks
1 of 1 (100%)
Average latency
258 ms
95th percentile latency
258 ms

Maintenance history

Public check and source-refresh events. Editorial and ownership records remain private.

  • · probe · passed · 258 ms · metadata changed · refuses unauthenticated initialize (HTTP 401)

Connect from your client

Each snippet registers the same endpoint; pick the client you use.

This server is operated by the named third party. Listing and endpoint checks are not an endorsement or a security audit. Review the operator's permissions, terms, and data handling before connecting. How listings are checked and corrected.

Claude Code

Run this once in a terminal. It registers the remote server. Use --scope project to write .mcp.json for the repo.
Claude Code configuration
claude mcp add --transport http contentin-linkedin-mcp https://mcp.contentin.io/mcp-server

Codex

Run this once. Codex stores MCP servers in ~/.codex/config.toml (or .codex/config.toml in a trusted project).
Codex configuration
codex mcp add contentin-linkedin-mcp --url https://mcp.contentin.io/mcp-server

Cursor

Merge this server into .cursor/mcp.json in your project, then enable contentin-linkedin-mcp in your MCP settings.
Cursor configuration
{
  "mcpServers": {
    "contentin-linkedin-mcp": {
      "url": "https://mcp.contentin.io/mcp-server"
    }
  }
}

Cline

Merge this into cline_mcp_settings.json (Cline → MCP Servers → Configure).
Cline configuration
{
  "mcpServers": {
    "contentin-linkedin-mcp": {
      "type": "streamableHttp",
      "url": "https://mcp.contentin.io/mcp-server",
      "disabled": false
    }
  }
}

VS Code

Merge this server into .vscode/mcp.json. Use MCP: List Servers to start contentin-linkedin-mcp and inspect its tools.
VS Code configuration
{
  "servers": {
    "contentin-linkedin-mcp": {
      "type": "http",
      "url": "https://mcp.contentin.io/mcp-server"
    }
  }
}

Gemini CLI

Run this once. It writes .gemini/settings.json in the current project; pass --scope user for ~/.gemini/settings.json.
Gemini CLI configuration
gemini mcp add --transport http contentin-linkedin-mcp https://mcp.contentin.io/mcp-server

Claude Desktop

Open Claude Settings > Connectors > Add custom connector, enter this server URL and enable it for the conversation. This is a manual remote-connector handoff, not a desktop JSON configuration.
Claude Desktop configuration
https://mcp.contentin.io/mcp-server

Windsurf

Merge this into ~/.codeium/windsurf/mcp_config.json, then refresh MCP in Cascade. Windsurf remote servers use serverUrl, not url.
Windsurf configuration
{
  "mcpServers": {
    "contentin-linkedin-mcp": {
      "serverUrl": "https://mcp.contentin.io/mcp-server"
    }
  }
}

Let your agent find its tools

Find servers like ContentIn LinkedIn MCP from your agent. Add Koskamo once to search the index for endpoints, access requirements, and client setup. Public discovery needs no key.

Connect Koskamo Explore workflows
See all 1,402

Do you run ContentIn LinkedIn MCP?

Prove ownership with a DNS record, a well-known file, or your Official MCP Registry entry, and your edits publish immediately. Proofs are re-checked weekly; admins can still hide or remove a listing.

Claim this listing