MCP.Market

Blog2Social - Social Media Publishing MCP server

online · 100% uptime
by Adenion·io.github.Adenion/blog2social-api-mcp·v1.0.0
No reviews yet

Connect AI agents to Blog2Social and automate social media content workflows via MCP.

B81/100grade B
Write a reviewRun it
What users say
No reviews yet
Be the first
Safety scan
B81/100

full report

Adoption
Growing

0 stars

Reviews

Write one

Nobody has reviewed Blog2Social - Social Media Publishing yet.

If you have run it, two minutes of your experience saves the next person an afternoon.

Blog2Social - Social Media Publishing tools (8, 2 write)

write = sends, deletes, buys or posts
  • connections.addFree

    Starts authorization for a social network account. Get network_id and a supported account type from networks.list; network_type_id 0 means profile, 1 page and 2 group. The response contains an auth_link for the user to open and authorize Blog2Social. Pinterest is an exception: it requires a custom application (service_conditions_id) and does not return an auth_link.

  • connections.listFree

    Returns the social accounts currently connected to the authenticated Blog2Social user, with details such as the network, account type and display name. Use an account client_user_network_id in posts.create to choose where to publish.

  • connections.removewrite actionFree

    Removes a social account connection from the authenticated Blog2Social user. Call connections.list first to get the account's client_user_network_id. After removal, the account can no longer be used for publishing unless it is connected again.

  • credits.balanceFree

    Returns the current credit balance of the authenticated Blog2Social API account. Publishing is not possible when the balance is 0, so check it if a post cannot be published.

  • networks.listFree

    Returns the social networks that can be connected to Blog2Social, including each network name, URL, network_id and whether profiles, pages or groups are supported. Use network_id and a supported network_type_id with connections.add to start connecting an account.

  • networks.list_propertiesFree

    Returns publishing capabilities and limits for each network and account type, such as supported media formats, video support and character limits. Check these requirements when preparing a post for a specific network and account type.

  • posts.createwrite actionFree

    Publishes a post to the connected account identified by client_user_network_id. Use postFormat 0 for text or link posts (a link is optional), 1 for image posts, or 2 for video posts; image and video posts require mediaObjects. The response includes a publish_url for non-video posts. Video posts return a video_token to check with videos.check.

  • videos.checkFree

    Checks the publishing status of a video post using the video_token returned by posts.create. Returns the status for each target social account: pending, failed or successful. A publish_url is included when publishing succeeds; check again while the status is pending.

Public scan report

scanner v0.1.10 · 2026-10-02 · same rubric, same numbers if you re-run it

1 high
  • –Code scanremote-only server, no package to scann/a
  • Live reliabilityremote reachable in 1591ms20/20
  • Tool poisoning8 tool descriptions checked15/15
  • Auth qualityopen endpoint exposes 2 write-action tools with no auth3/15
  • Maintenancelast push 0 days ago15/15
  • Maintainer identityregistry namespace matches repository owner; GitHub account older than a year8/10

Findings (1)

  • highWrite-action tools reachable without authenticationauth.open-write
Overall 81/100. Components that don't apply are left out of the denominator. Any critical finding is an F.RubricAppeal a findingJSON

How Blog2Social - Social Media Publishing compares

Against every graded MCP server, from our own scans and uptime checks. Updated after each scan run.

Safety score
81/100
higher than 62% of 48,255 servers
Tools
8
the typical server has 7
Tools that change things
25%
typical: 0%. Fewer write tools means less an agent can break
Uptime
100%
of our recent checks; the typical remote server answers 100%
Response time
693 ms
faster than 20% of 30,031 servers

What its tools let an agent do: 5 read · 2 create · 1 delete

Install Blog2Social - Social Media Publishing in Claude Code, Cursor or VS Code

claude mcp add --transport http blog2social-api-mcp https://api.blog2social.com/mcp
Add to Cursor

What the publisher says

From the Blog2Social - Social Media Publishing repository's README, as published. We do not edit it. Read it on GitHub

Blog2Social MCP Server

The Blog2Social MCP Server provides a hosted Model Context Protocol (MCP) interface for connecting AI assistants, AI agents, coding assistants and automation tools directly to Blog2Social.

With the MCP server, compatible AI applications can use Blog2Social functionality through natural-language instructions instead of requiring a custom Blog2Social API integration for each application.

The MCP server can be used to:

  • view connected social media accounts
  • discover supported social networks
  • connect and disconnect social media accounts
  • check Blog2Social credit balances
  • inspect publishing capabilities and network-specific limits
  • publish text, link, image and video posts
  • check the publishing status of video posts

The MCP server is hosted by Blog2Social. No local MCP server installation is required. Authentication is handled through OAuth.

MCP Endpoint

https://api.blog2social.com/mcp

The endpoint is the same for all supported MCP clients.

How it works

The Blog2Social MCP Server acts as a bridge between an AI application and Blog2Social:

AI Assistant / AI Agent
          |
          | MCP
          v
Blog2Social MCP Server
          |
          | Blog2Social API
          v
     Blog2Social
          |
          +-- Connected Social Accounts
          +-- Social Networks
          +-- Posts
          +-- Publishing

This means that an MCP-compatible application can interact with Blog2Social using standardized MCP tools rather than implementing the Blog2Social API itself.

For example, an AI assistant can be instructed to:

Show me my connected social media accounts.

or:

Publish this article to my LinkedIn page and Facebook page.

The AI application can then use the appropriate Blog2Social MCP tools to perform the requested operation.

Authentication

Blog2Social MCP uses OAuth for authentication and authorization.

The typical authentication flow is:

AI Application
      |
      v
Blog2Social MCP
      |
      v
Blog2Social OAuth
      |
      v
Login & Authorization
      |
      v
MCP Connection
      |
      v
Blog2Social MCP Tools

You do not need to enter your Blog2Social password into the AI application's MCP configuration.

After adding the MCP endpoint, the client redirects you through the Blog2Social OAuth flow. Log in to Blog2Social and explicitly authorize the connection.

Security: Do not add your Blog2Social password, service token or access token to an MCP client configuration file. Authentication is handled through OAuth.

Available Tools

The Blog2Social MCP server currently provides the following tools.

connections.list

Read-only

Returns the social media accounts currently connected to the authenticated Blog2Social account.

The response includes information such as:

  • social network
  • account type
  • display name
  • clientusernetwork_id

The clientusernetwork_id identifies the connected account and is used when publishing posts with posts.create.

Example use:

Show me all social media accounts connected to Blog2Social.

connections.add

Writes

Starts the authorization process for connecting a social network account.

The tool uses:

  • network_id – identifies the social network
  • networktypeid – identifies the account type

Supported account types are:

0 = Profile
1 = Page
2 = Group

The tool normally returns an authorization link that the user opens to authorize the connection.

Pinterest is an exception and may require a custom application configuration instead of the standard authorization link.

Example use:

Connect my LinkedIn account to Blog2Social.

The available networks and supported account types should be checked with networks.list before starting the connection process.

connections.remove

Destructive

Shortened. The full README is on GitHub.

Nothing above is checked by us. What we check is on the safety report.

Blog2Social - Social Media Publishing: common questions

Is Blog2Social - Social Media Publishing MCP server safe?
Mostly: it is graded B (81/100). Read the Blog2Social - Social Media Publishing safety report
How do I install Blog2Social - Social Media Publishing?
It runs remotely at api.blog2social.com. Add it to Claude Code, Cursor, VS Code or Claude Desktop with the snippets above, or call it through the mcp.market gateway without installing anything.
Does Blog2Social - Social Media Publishing need an API key?
Not as far as the registry entry and our scan can tell: no credentials are declared or required.
Is Blog2Social - Social Media Publishing maintained?
The last commit was 33 days ago (2026-10-02). The latest release is v1.0.0.
Is Blog2Social - Social Media Publishing up?
100% of our last 28 checks got an answer. We check remote servers about four times a day.
How does Blog2Social - Social Media Publishing compare with other MCP servers?
safety score 81/100 (higher than 62% of 48,255 servers); tools 8 (the typical server has 7); tools that change things 25% (typical: 0%. Fewer write tools means less an agent can break). Full comparison.