Blog
Let your coding agent read and manage blog posts on lazy-mac.com infrastructure without you wiring a custom REST client.
Overview
io.github.lazymac2x/blog is a MCP server for the Grow phase that exposes blog API operations to AI coding agents over streamable-http.
What is this MCP server?
- Remote streamable-http MCP endpoint at api.lazy-mac.com/blog/mcp
- Hosted on Cloudflare Workers with server schema 2025-09-29
- Open-source API repo lazymac2x/blog-api on GitHub
- Agent-callable blog operations without local MCP process
- Version 1.0.0 published package io.github.lazymac2x/blog
- 1 streamable-http remote endpoint
- Server version 1.0.0
- MCP schema dated 2025-09-29
What problem does it solve?
Solo builders waste time copying blog admin tasks between a browser dashboard and the agent session instead of one MCP connection.
Who is it for?
Indie hackers who host or integrate with the lazy-mac blog API and want agent-driven content maintenance.
Skip if: Teams that need a full headless CMS with no tie-in to api.lazy-mac.com or self-hosted MCP.
What do I get? / Deliverables
After you register the remote MCP URL, your agent can call blog tools in the same thread where you ship features and draft posts.
- Registered remote MCP connection for blog operations
- Agent-invokable blog tools via the published MCP schema
- Traceable integration path to lazymac2x/blog-api source repo
Recommended MCP Servers
Journey fit
How it compares
MCP integration to a blog API, not a copywriting or SEO agent skill.
Common Questions / FAQ
Who is io.github.lazymac2x/blog for?
Solo builders and small teams who use Claude Code or similar agents and want MCP access to blog endpoints on Cloudflare Workers.
When should I use io.github.lazymac2x/blog?
Use it during Grow when you are updating posts, syncing changelog content, or automating blog reads and writes from your agent workflow.
How do I add io.github.lazymac2x/blog to my agent?
Add the remote MCP server URL https://api.lazy-mac.com/blog/mcp with transport type streamable-http in your client’s MCP server configuration.