RedMate
Download

RedMate MCP

RedMate MCP

Learn how to connect AI agents to your RedMate workspace so they can read account context, manage drafts, organize projects, and arrange publishing queues with your authorization.

Connect clientsCopy the endpoint from the app and add it to Claude Code, Cursor, or .mcp.json.
Supported toolsAccounts, drafts, projects, images, and publishing queues are exposed as MCP tools.
Security boundaryCookies never appear in MCP responses; write tools carry side-effect annotations and idempotency support.
Local serverDefaults to 127.0.0.1:7654/mcp, with status and request logs visible in the app.
Documentation Index

Start with Overview to understand RedMate MCP boundaries. For first setup, read Connecting to RedMate MCP. Before letting AI perform writes, read Supported tools and Security best practices.

What is RedMate MCP?

RedMate MCP is the local MCP server that starts with the macOS app. It exposes drafts, projects, publishing queues, and account state as standard MCP tools for Claude Code, Cursor, Codex, or custom MCP clients. Real login sessions, cookies, and Xiaohongshu browser execution stay inside the local app.

MCP data flow
MCP clients
RedMate MCP server
RedMate app / Cloud service / XHS session
AI clients connect to the local MCP server. The server calls RedMate's draft, project, queue, and isolated browser-session capabilities. Account cookies are not returned to clients.

Why use RedMate MCP?

  • Fewer context switches: AI can read draft, project, and queue context without manual copy and paste.
  • Desktop boundary stays intact: real account sessions, cookies, and publishing execution remain inside the local RedMate app.
  • Agent-friendly responses: tools return structured JSON, and failures include error codes so AI can retry, adjust inputs, or ask for human handling.