Google Search Console integration for Model Context Protocol (MCP)
Blog2Social - Social Media Publishing is installed from its publisher's own source and answers where it runs, so this marketplace is not in the path of a single call. There is no address here to send one to, and a panel that pretended otherwise would be showing you an answer we made up. Install it and call it from your own client — the Installation tab has the entry for each one.
What it does
Connect AI agents to Blog2Social and automate social media content workflows via MCP.
Quickstart
# 1 — add it to Claude Code
claude mcp add --scope user --transport http blog2social-social-media-publishing-mcp https://api.blog2social.com/mcp
# 2 — ask your agent for something these tools do
# networks.list, connections.list, networks.properties and 6 more
Blog2Social - Social Media Publishing costs nothing on mcprush: there is no plan to choose here, no cap to set and nothing mcprush can bill you for.
Collected from a public index. Nobody has claimed this account, so nothing here was written by its author — claim it if it is yours.
Where are you running it?
Every route below installs the same thing and ends at the same approval screen. Nothing here runs on your machine and nothing runs on ours: this server answers at its publisher’s own address, and what you install is the connection straight to it.
This is a public server: it answers at its publisher’s own address and this marketplace is not in the path. Claude Code registers it in one command; --scope user makes it available in every project. The transport below is http, as the publisher's own manifest declares it.
claude mcp add --scope user --transport http blog2social-social-media-publishing-mcp https://api.blog2social.com/mcpReconnect, or start a new session, and the tools appear in the model’s tool list.
One config entry pointing straight at the publisher’s own address — this marketplace is not in the path, and nothing from this listing executes on your machine.
9 tools, with what each one reads, writes and reaches shown before you agree — the same list on every route above. Read the tool surface.
Tool surface
What the model actually sees. Descriptions are diffed on every release — see version history.
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.
No parameter schema on file.
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.
No parameter schema on file.
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.
No parameter schema on file.
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.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| client_user_network_id | integer | yes | Connected social media account ID returned by connections.list. |
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. For Pinterest, an active custom app must be configured in the Blog2Social Developer Console and assigned to the API service; the assigned app is sele
| Parameter | Type | Required | Notes |
|---|---|---|---|
| network_id | integer | yes | Social media network ID returned by the networks.list tool. |
| network_type_id | integer | yes | Connection type: 0 = profile, 1 = page, 2 = group. |
| language | string | no | Optional language for the authorization flow, for example en or de. |
Publishes a post to the connected account identified by client_user_network_id. Use networks.properties to retrieve network-specific posting requirements before preparing the post. 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 ret
| Parameter | Type | Required | Notes |
|---|---|---|---|
| client_user_network_id | integer | yes | Connected social media account ID returned by connections.list. All posts in b2s_posts are published to this account. |
| b2s_posts | array | yes | One or more posts to publish to the selected account. Use postFormat 0 for text or links, 1 for images, and 2 for videos; image and video posts require mediaObjects. |
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.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| video_token | string | yes | Video token returned when the video upload was created. |
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.
No parameter schema on file.
Returns the current credit balance and daily credit usage grouped by endpoint and network. Optionally set days to a value from 1 to 30; when omitted, the endpoint default is used.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| days | integer | no | Number of calendar days to include, from 1 to 30. |
- Every tool — any call limit is its publisher’s, not ours
- No card, and mcprush charges nothing for it
- Runs at its publisher’s own address — this marketplace is not in the path
- Nothing to cap, because mcprush bills nothing
What counts against your monthly calls
| Tool | Unit | Calls used | Out of the allowance |
|---|
Nothing here is billable: mcprush charges nothing to install Blog2Social - Social Media Publishing or to call it, at any volume.
Two independent axes, because powerful and malicious are different questions. The grade is threat only. The capability level is blast radius, and it is never a penalty on the grade — it is priced as one subtract-only term in the score, where you can see it.
This listing is an address its publisher runs, and you connect to it directly — this marketplace is not in the path. The scanner reads packages and public source, and an address is neither: the repository linked on this page is where this record was collected from, not a copy of what the address serves, so it is not graded in its place. So there is no grade — not a withheld one, an unmeasured one.
Release history
This is an address its publisher runs: which release it serves is theirs to choose, so there is nothing here to pin. The history below is for reading; the current release on file is 1.0.0.
No release note was published with this version.
One review per account, from a signed-in account that does not publish this listing. Nothing else is asked — you can say what you think before you install it. Publishers can reply once per review, and a review can be edited or deleted by whoever wrote it.
Any signed-in account that does not publish Blog2Social - Social Media Publishing can review it, once — before installing it or after. A review from an account that has installed it is marked as one.
Nobody has reviewed this listing. The rating on the card is the mean of the reviews written here and nothing else, so there is no rating until somebody writes the first — which takes a signed-in account that does not publish it, and nothing else.