2pr.io

io.2prPublished by 2pr.ioOfficial publisherv1.0.0Updated Oct 25, 2026

Draft, schedule and publish LinkedIn posts, reply to comments and read analytics via 2pr.io.

VerifiedStreamable HTTPWeb executableCommunication & CollaborationBusiness & Commerce

Overview

AI-generated overview

A remote MCP server that lets an assistant draft, schedule and publish LinkedIn posts, reply to comments and read analytics through 2pr.io.

What you can do
Draft LinkedIn posts and prepare them for publishing through 2pr.io, which handles the LinkedIn connection on the user's behalf. Schedule posts for later publication and publish them to LinkedIn. Reply to comments on published posts. Read analytics on post performance. The manifest lists no individual tools, so the exact operations are not documented here.
When to use it
Useful when an assistant should help run a LinkedIn presence end to end: writing posts, planning a publishing schedule, answering comments and checking how posts performed, without switching between tools.
Requirements
A remote MCP endpoint at 2pr.io reached over streamable HTTP. OAuth authentication is required, so the user must sign in and authorize access, presumably to a 2pr.io account linked to LinkedIn. No environment variables or headers are declared.
Before you install
The server can publish posts and reply to comments publicly on LinkedIn, so review drafts before anything goes out. It reads analytics from the connected account. Access is granted through OAuth, so check which account and permissions are authorized and revoke access when no longer needed.

Installation

In SourceWeft

  1. Open 2pr.io 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.2pr%2F2pr/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": {
    "2pr-io": {
      "type": "http",
      "url": "https://2pr.io/api/mcp"
    }
  }
}

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

1
  1. v1.0.0LatestSep 16, 2026

Score

67% 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

    Declare a GitHub repository with a README, or serve resource_documentation in the OAuth protected-resource metadata.

  • 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.