Connect Mirra to
any AI agent
The Model Context Protocol is the open standard for wiring AI agents to real tools. Connect Claude with the hosted OAuth URL, or install the local MCP server when you need desktop file uploads.
{
"mcpServers": {
"mirra": {
"command": "npx",
"args": ["-y", "@mirrai/mcp-server@latest"],
"env": {
"MIRRA_API_KEY": "your-api-key"
}
}
}
}https://www.mirra.my/api/mcp
OAuth
Step 1
Two install paths for different agent environments
Use Claude's custom connector with the hosted MCP URL and OAuth. Use the local @mirrai/mcp-server package when Claude Desktop, Cursor, or another desktop agent needs to read local files.
Step 2
39+ tools across six full-stack categories
Carousels, shorts, longform blog, scheduled publishing, social analytics, DM automation — almost every action in the Mirra dashboard is exposed as an MCP tool an agent can call.
"Draft and schedule a week of LinkedIn posts about our product launch"
Step 3
One prompt runs the whole workflow
"Draft and schedule a week of LinkedIn posts about our product launch" is enough. The agent composes the right tool calls — draft, image pull, schedule — end to end.
Local install
Claude remote connector
Step 4
OAuth for remote, API keys for local
Claude's hosted connector signs in through OAuth and receives a revocable Mirra token. Local MCP installs still use workspace API keys so desktop agents can keep file-path upload workflows.
AI agents drive Mirra end to end
MCP makes Mirra a first-class tool for any AI agent. A single prompt runs the full content workflow — plan, publish, analyze.
Connect Mirra to your AI agent
Use the hosted OAuth connector for Claude, or grab an API key for local agents that need desktop file access.