Use BlogSphere with Claude

BlogSphere has a connector for Claude that works through the Model Context Protocol (MCP). Once connected, you can ask Claude to work on your websites in plain language: write and schedule posts, organise media, moderate comments and read analytics. You choose which websites Claude can use and what it may do, and you can disconnect it at any time.

What you need

A BlogSphere account with at least one website. Sign in or create one first.
A Claude account. Custom connectors are available on Claude Free, Pro, Max, Team and Enterprise.
The connector address: https://blogs-mcp.metalinxinnovations.com/mcp

Connect from Claude (claude.ai, desktop and mobile)

In Claude open Settings, then Connectors.
Choose Add custom connector.
Name it BlogSphere and paste the address https://blogs-mcp.metalinxinnovations.com/mcp, then choose Add.
Choose Connect. Claude opens the BlogSphere sign-in. Sign in to your account.
On the Connect an app page choose the workspace, tick the websites Claude may use, and choose an access level (see below). Then choose Allow.
Back in Claude, the connector shows as connected. Turn it on for the conversation from the tools menu.

There is nothing else to paste: no client ID and no secret. Claude registers itself and signs in with OAuth.

Team and Enterprise: an organisation Owner adds the connector once under Organization settings, Connectors. Each member then connects it with their own BlogSphere account.

Connect from Claude Code

claude mcp add --transport http blogsphere https://blogs-mcp.metalinxinnovations.com/mcp

Then run /mcp inside Claude Code, choose blogsphere and choose Authenticate. A browser window opens for the same sign-in and access page as above.

Access levels

Read only: Claude can look at your content, comments and analytics but cannot change anything.
Editor: Claude can also create and edit posts, pages, media, categories and tags, and moderate comments. Posts stay as drafts unless you ask Claude to publish.
Full: everything Editor can do, plus broader changes such as store and settings tools, and deleting content.

Claude never gets more access than your own account has. Actions that delete something ask for an explicit confirmation first.

What to ask

"Which websites can you work on?"
"How did my blog do in the last 30 days, and which post is my best?"
"Draft a post about your topic and keep it as a draft."
"Schedule my draft for Friday at 9 am."
"Show the comments waiting for approval and tell me which to approve."
"Which images in my media library are not used anywhere?"
"Which channels and campaigns brought the most visitors this month?"

Your data and privacy

Claude only receives what the tools return for the websites and access level you chose.
Personal data is minimised by default: customer, subscriber and commenter emails are masked, phone numbers and street addresses are left out unless you explicitly ask, and IP addresses and browser details are never returned.
We log each tool call (the tool, the website, the time and the result) for security. We do not log your content.
Content you ask Claude to process is handled by Anthropic under its own terms and privacy policy.

Read the full Privacy Policy and Terms.

Change or remove the connection

Change the websites or the level: in the BlogSphere admin open Account, then Connected apps, and edit or revoke the connection. A connector cannot be edited inside Claude: remove it in Claude and add it again to choose new settings.
Disconnect: revoke it under Connected apps in BlogSphere, and remove it under Settings, Connectors in Claude. Access stops immediately.

Troubleshooting

"Couldn't reach" the connector: check that the address is exactly https://blogs-mcp.metalinxinnovations.com/mcp, including /mcp at the end.
Claude says it cannot see a website: that website was not ticked when you connected. Edit the connection under Connected apps, or reconnect.
Claude cannot change anything: the access level is Read only. Reconnect and choose Editor or Full.
Sign-in loops: sign in to BlogSphere in the same browser first, then connect again.

Support

Questions or problems: [email protected] or the contact page.