# Blog2Social - Social Media Publishing [Health: Active]

**Category:** 💻 Developer Tools  
**Repository:** https://github.com/Adenion/blog2social-api-mcp  
**GitHub Stars:** 1  
**Views:** 0  
**Installs:** 0  
**Upvotes:** 0  
**Directory Page:** https://allmcps.com/mcp/blog2social-social-media-publishing

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

## Tools
Capabilities this server exposes over MCP:

- **connections.list** — **Read-only**
- **connections.add** — **Writes**
- **connections.remove** — **Destructive**
- **networks.list** — **Read-only**
- **networks.list_properties** — **Read-only**
- **credits.balance** — **Read-only**
- **posts.create** — **Writes**
- **videos.check** — **Read-only**

## Claude Desktop Quick Installation
Remote MCP endpoint (confidence: high). Install path detected from listing signals. Add as a URL/SSE server in your client:

```json
"mcpServers": {
  "blog2social-social-media-publishing": {
    "url": "https://api.blog2social.com/mcp"
  }
}
```

## Documentation

## What Blog2Social - Social Media Publishing does

Blog2Social - Social Media Publishing MCP server exposes Blog2Social functionality to MCP-compatible AI assistants, agents, coding assistants, and automation tools. It acts as an intermediary between the client and the Blog2Social API, allowing natural-language requests to be translated into Blog2Social operations.

The server can show connected social media accounts, list available networks, start or remove account connections, inspect network-specific publishing rules, check API credits, create posts, and inspect video publishing status. Publishing targets are connected accounts identified by a `client_user_network_id`.

## How it works

The service is hosted by Blog2Social at `https://api.blog2social.com/mcp`. An MCP client connects to that endpoint, then uses the exposed tools to call Blog2Social operations. For example, a client can first retrieve connected accounts, identify the desired page or profile, and then pass that account identifier to `posts.create`.

Authentication uses Blog2Social OAuth. The client redirects the user to Blog2Social, where they log in and explicitly authorize the connection. The MCP configuration should not contain a Blog2Social password, service token, or access token.

## Setup and configuration

No local installation is required. You do not need to clone the repository, install Node.js or Python, run a local process, configure a database, or manually create an OAuth token.

Configure the MCP-compatible client with this hosted URL:

```text
https://api.blog2social.com/mcp
```

The exact configuration format depends on the client. After the endpoint is added, complete the OAuth flow when prompted. Claude can connect through its custom connector settings by adding the same URL and authorizing the Blog2Social account.

## Tools and capabilities

Blog2Social - Social Media Publishing provides these tools:

- `connections.list` reads connected accounts and their identifiers.
- `connections.add` starts authorization for a social network account using a network ID and account type. Profiles, pages, and groups are represented by account type IDs.
- `connections.remove` deletes an existing connection and requires its `client_user_network_id`.
- `networks.list` lists available networks and supported account types.
- `networks.list_properties` reports publishing formats, media support, character limits, and other network-specific requirements.
- `credits.balance` returns the authenticated Blog2Social API account’s current credit balance.
- `posts.create` publishes text, links, images, or videos to a connected account.
- `videos.check` checks a video publication using the token returned by video creation. Results can be pending, failed, or successful.

Use `networks.list` before adding an account, and inspect network properties before preparing content for a specific destination.

## Limitations and notes

Account connection, removal, and post creation change Blog2Social state. Account removal is destructive and should only follow an explicit user request. Video publishing may finish asynchronously, so a successful result may require a later `videos.check` call.

Pinterest connections may require custom application configuration instead of the standard authorization link. The material does not specify support for particular social networks beyond the discovery tools, so available destinations should be checked through `networks.list` rather than assumed. A client must support connecting to a remote MCP endpoint and completing OAuth authorization.

_Full upstream README: https://allmcps.com/mcp/blog2social-social-media-publishing/readme_