MCP server
REM Blogs' MCP server for writers' AI clients - seven tools, drafts only, every write reviewed by a person.
REM Blogs has an MCP server so an AI client (Claude Code, Claude Desktop or any MCP client) can draft posts in the house format. It can never publish or delete: every post it creates or changes goes to a human reviewer.
Connect
Make a token on Account > AI Clients in the admin (it needs the content-admin or seo team in REM Auth) and paste the MCP Configuration block it shows into your client. The token is personal, lasts 90 days, and carries scopes posts:read, posts:write and media:write as you choose.
Tools
Tool | Needs | What |
|---|---|---|
| posts:read | The rules and the node vocabulary; call it before writing |
| posts:read | Find posts by title or topic (authors see their own) |
| posts:read | A post with its Markdown and metadata |
| posts:read | The products a post can be shown in |
| posts:write | A new draft from Markdown |
| posts:write | Change a draft; the previous version is kept |
| media:write | Upload an image file from your machine; returns the URL to use |
The server lists only the tools your token may use (GET /api/mcp/tools).
House rules (enforced)
The body is Markdown; it is parsed into the editor's blocks and raw HTML is dropped. Directives exist for calls to action, callouts, embeds and chips (
:::cta{variant="banner" href="/x" label="Go"}).Headings start at level 2; the title is rendered separately.
Code blocks name their language.
Every image needs alt text, and its URL must come from
upload_image. Generating images with AI is prohibited; ask the person for a folder of real images.Topics are the sections readers subscribe to: pick existing ones.
meta_keywordsare extra SEO words for one post.Nothing is ever deleted; each save keeps the previous version. Every write is in the Audit Log with the token's prefix.
Last updated 18 Nov 2026