Blog MCP Server

Search and read the Radixia blog (enterprise AI, cloud, open source) via MCP. That is what the blog mcp server brings to an AI assistant: the same capability, reachable through the Model Context Protocol rather than a separate app or dashboard.

The short version

Public, read-only Model Context Protocol server for the Radixia blog. Runs on Cloudflare Workers (streamable HTTP).

The tools it exposes

The server publishes 8 tools. What each one is for:

• list_posts — recent posts (limit, tag)
• search_posts — full-text search (query, limit)
• get_post — full post by slug
• list_tags — tags with counts
• about_radixia — company profile
• search_isc2026_transcripts — full-text search across 147 auto-caption session transcripts from ISC High Performance 2026 (query, limit)
• get_isc2026_session — full transcript of one ISC 2026 session by title
• get_isc2026_agenda — the ISC 2026 program with times, halls and speakers (day)

Getting it running

Because this one is hosted, setup is mostly authentication — you point your client at the endpoint and approve access. Nothing runs on your machine, so there is no runtime to keep patched.

How it compares

Among the developer tooling options, the useful question is rarely "what can it do" but "what does it cost you to run" — permissions, credentials, and how much of your context its toolset consumes. Blog's toolset — list_posts, search_posts, get_post and 5 more — is a fair guide to whether it matches your workflow. It is maintained by ai.radixia; worth a glance at recent repository activity before you build anything load-bearing on it.

This entry was verified against Blog's own documentation before publication; SyncDev keeps the directory reviewed rather than auto-generated.

Things to watch

• Your data travels to the provider's service, so the usual questions apply about what you send and what they retain.
• Keep per-call confirmation enabled while you learn its behaviour; it is the cheapest safeguard you have.