Community · Official remote MCP server

The BlogCaster MCP MCP server,
connected in one click.

An MCP server for the BlogCaster project. Connect the official BlogCaster MCP MCP server to Claude, ChatGPT, or Cursor through gate — one gateway URL, no config files, security-checked.

Connect BlogCaster MCP free How it works

Free to start · No credit card · No hosting needed

Use this server

Add BlogCaster MCP to your AI in one minute

Pick your client. Copy, paste, done — or let gate handle sign-ins and policies for you.

claude mcp add --transport http blogcaster-mcp https://blogcaster-mcp.rrpb2580.workers.dev/mcp

Run in your terminal, then restart Claude Code.

BlogCaster MCP · https://blogcaster-mcp.rrpb2580.workers.dev/mcp

What you can do

What your AI can do with BlogCaster MCP

Real prompts you can type the moment it's connected — no setup, no docs to read.

“Use “getLoginLink”: Get a login link to authenticate and manage your tokens.”

“Use “whoami”: Check current authenticated user.”

“Use “logout”: Clear current authentication.”

“Use “publishPost”.”

Security check

How secure is the BlogCaster MCP MCP server?

Every server in the gate directory has to pass the same four checks before your AI can touch it. Here's how BlogCaster MCP holds up.

✓ Verified directory serverBlogCaster MCP · workers.dev

Official endpoint

Operated by BlogCaster MCP (workers.dev) at its documented MCP endpoint — not a third-party mirror or community re-host.

No sign-in needed

This server only exposes public data — no account and no credentials are involved when you connect.

Scanned before it goes live

gate checks every tool for prompt injection, hidden instructions, data-exfiltration hints, and over-broad permissions before the server is available through your gateway.

Watched for drift

If BlogCaster MCP adds or changes tools later, gate re-scans and alerts you — before your AI acts on the change.

Run the free scanner on BlogCaster MCP's server →

How it works

Connected in three steps

Connect your gate

Add one gateway URL to Claude, ChatGPT, or any MCP client. One-time setup, about two minutes.

Pick BlogCaster MCP

Choose BlogCaster MCP in the gate directory. No sign-in needed.

Use it anywhere

BlogCaster MCP's tools are live in every AI client you've connected — with rules and logging built in.

Connect BlogCaster MCP free

Free to start · No credit card · No hosting needed

Straight from the server

The actual tools BlogCaster MCP exposes

Fetched live from the official endpoint and re-checked daily by gate — not marketing copy.

getLoginLink — Get a login link to authenticate and manage your tokens

whoami — Check current authenticated user

logout — Clear current authentication

publishPost

updatePost

getBlogs

deletePost

Author

Who runs the BlogCaster MCP MCP server?

workers.dev

More servers from workers.dev →

Own this server? Claim the listing →

Server facts

The BlogCaster MCP MCP server at a glance

Endpointhttps://blogcaster-mcp.rrpb2580.workers.dev/mcp

Operated byBlogCaster MCP (workers.dev)

CategoryCommunity

Sign-inNone — public data only

Available in gateYes — one-click connect

Works withClaude, ChatGPT, Cursor & any MCP client

FAQ

Questions, answered

Is there an official BlogCaster MCP MCP server?

Yes — BlogCaster MCP operates its own remote MCP server at blogcaster-mcp.rrpb2580.workers.dev. gate connects you to that official endpoint and adds security scanning, per-tool access rules, and an activity log on top.

How do I connect BlogCaster MCP to Claude or ChatGPT?

Add gate's gateway URL to your AI client once, then pick BlogCaster MCP in the directory. No account or sign-in is needed. From then on, BlogCaster MCP's tools are available in every client you've connected to gate.

Do I need to host anything?

No. BlogCaster MCP runs the server, and gate is fully managed. You just connect one URL — there's nothing to install, deploy, or maintain.

Is the BlogCaster MCP MCP server safe to connect?

It's the vendor's official endpoint, and gate scans its tools for prompt injection and hidden instructions before it goes live, re-checks it whenever it changes, and lets you allow, block, or require approval for every single tool.