Blog MCP server
{
"mcpServers": {
"radixia-blog": {
"type": "http",
"url": "https://mcp.radixia.ai/mcp"
}
}
}{
"mcpServers": {
"radixia-blog": {
"type": "http",
"url": "https://mcp.radixia.ai/mcp"
}
}
}{
"mcpServers": {
"radixia-blog": {
"type": "http",
"url": "https://mcp.radixia.ai/mcp"
}
}
}{
"servers": {
"radixia-blog": {
"type": "http",
"url": "https://mcp.radixia.ai/mcp"
}
}
}{
"mcpServers": {
"radixia-blog": {
"type": "http",
"url": "https://mcp.radixia.ai/mcp"
}
}
}file .mcp.json (in your project root)file claude_desktop_config.jsonfile ~/.cursor/mcp.jsonfile .vscode/mcp.jsonfile ~/.codeium/windsurf/mcp_config.jsonversion 1.0.0
What it does
Read-only MCP server exposing the Radixia blog and ISC High Performance 2026 conference transcripts. Intended for developers and AI assistants that need to query blog posts or search session transcripts programmatically.
- Search and retrieve Radixia blog posts by keyword or tag to pull relevant articles into an AI workflow.
- Search across 147 auto-captioned session transcripts from ISC High Performance 2026 to find specific talks or topics.
- Fetch the full ISC 2026 conference agenda, including session times, halls, and speakers, for a given day.
Tools this server exposes
| Tool | Does |
|---|---|
| list_posts | Returns recent blog posts, optionally filtered by tag and result limit. |
| search_posts | Full-text search across blog posts by query string. |
| get_post | Retrieves the full content of a blog post by its slug. |
| list_tags | Lists all blog tags along with their post counts. |
| about_radixia | Returns a company profile for Radixia. |
| search_isc2026_transcripts | Full-text search across 147 auto-captioned ISC High Performance 2026 session transcripts. |
| get_isc2026_session | Retrieves the full transcript of a single ISC 2026 session by title. |
| get_isc2026_agenda | Returns the ISC 2026 program with session times, halls, and speakers, optionally filtered by day. |
Before you enable it
An MCP server runs with whatever access you give it. Start with a development account rather than production, and check which tools the server exposes before you let an agent call them unattended.