MCP server
user-majico-mcp exposes Majico project data as MCP tools so coding agents can read guidelines, tokens, logos, and studio canvas without custom HTTP code.
Requires: Majico Pro or Creator and a project API key.
Install (stdio — local Cursor)
Add to .cursor/mcp.json:
{
"mcpServers": {
"majico": {
"command": "npx",
"args": ["-y", "user-majico-mcp@0.5.0"],
"env": {
"MAJICO_API_URL": "https://api.majico.xyz",
"MAJICO_PROJECT_ID": "<your-project-uuid>",
"MAJICO_API_KEY": "<your-project-api-key>"
}
}
}
}Or use Add to Cursor on Account → Integrations when enabled.
Environment variables
Set once in MCP config — tools do not require projectId / apiKey on every call:
| Variable | Description |
|---|---|
MAJICO_API_URL | API base (default https://api.majico.xyz) |
MAJICO_PROJECT_ID | Project UUID |
MAJICO_API_KEY | Project API key |
Per-call overrides in tool arguments still work.
HTTP MCP (hosted)
Remote agents connect to https://api.majico.xyz/mcp with:
Authorization: Bearer <project_api_key>
X-Majico-Project-Id: <uuid>Tools (v0.5)
| Tool | Description |
|---|---|
get_brand_profile | Archetypes, niche intent |
get_design_tokens | Palette and fonts |
get_logo_svg | Selected logo SVG |
list_logo_candidates / select_logo | Logo picking |
list_palette_options / select_palette | Color schemes |
get_guidelines | Markdown + LLM prompt |
get_design_md | DESIGN.md markdown |
get_studio_canvas | Studio board snapshot |
update_studio_html_frame | Patch one htmlFrame (elementId, html) |
get_export_manifest | Export file list |
get_pulse_status / list_pulse_posts | Pulse / X analytics |
generate_tweet_drafts / select_tweet_draft | Tweet variants |
get_cursor_handoff / ack_cursor_handoff | Browser → chat handoff |
bootstrap_project | Create project (agent secret required) |
For interactive brand decisions (palette, logo, tweet draft), agents should list → user chooses → select — not auto-pick subjective options. See Cursor integration for the full handoff flow.
Relationship to @majico/sdk
The MCP server is built on @majico/sdk. Use the SDK directly in Node scripts; use MCP when your agent runtime speaks the Model Context Protocol.
Development
cd packages/user-majico-mcp
npm install
npm run build
npm testNext: Cursor integration · SDK overview