Gixo MCP Server
Connect MCP-capable clients to Gixo for signed-in Lumen presentation generation and Quill drafting, business artifact routing, proposal analysis, content analysis, and authenticated execution.
| Tool surface | Current access | Current output |
|---|---|---|
| Five Lumen creation tools | Signed in, with Lumen access; deck generation follows the account's plan | Decks in the account's own Lumen workspace |
| Editable PowerPoint chart | Signed in, with a Prism trial or plan | Native, editable PowerPoint chart file |
| Four Quill tools | Signed in, with Quill access; drafting and publishing follow the account's plan | Quill drafts in the account's own workspace, checks on a saved draft, and a saved draft sent as a draft to a WordPress or Ghost site already connected in Gixo |
| Four analysis and routing tools | Anonymous | Read-only business, proposal, or content analysis |
| Business artifact execution | Authenticated and entitled | Executed business artifact workflow |
Tool Surface
Lumen (signed in)
create_pitch_deckcreate_board_presentationcreate_sales_presentationcreate_training_presentationcreate_presentation_from_url
Requires a bearer token for a Gixo account with Lumen access. Decks start through the same generation path as the Lumen create page, so the plan's limits apply. Each tool returns the deck's content id, its status and its link in Gixo straight away; generation continues in the background. A call without a signed-in account is refused with sign_in_required and starts nothing.
Prism (signed in)
create_editable_chart
Requires a bearer token for a Gixo account with an active Prism trial or plan.
Quill (signed in)
create_quill_draftget_quill_contentrun_quill_workbenchpublish_quill_content
Requires a bearer token for a Gixo account with Quill access. Drafts start through the same generation path as the Quill create page, so the plan's limits apply. publish_quill_content sends only as a draft on a WordPress or Ghost site already connected in Gixo; it never publishes live, schedules, or connects a site, and a workspace that requires approval needs an approved release.
Anonymous analysis tools
route_business_artifactrun_business_diagnosticanalyze_proposal_draftanalyze_content_workbench
Authenticated execution
execute_business_artifact
Requires a bearer token mapped to an entitled Gixo account.
Connect
Use the remote server URL in any MCP-capable client:
https://gixo.ai/mcp
For Claude API usage with mcp_servers, see Use Gixo via the Claude API MCP Connector.
Direct MCP Smoke Check
Initialize a session, send the initialized notification, then list tools.
curl -i -X POST https://gixo.ai/mcp \
-H "content-type: application/json" \
-H "accept: application/json, text/event-stream" \
-d '{"jsonrpc":"2.0","id":1,"method":"initialize","params":{"protocolVersion":"2024-11-05","capabilities":{},"clientInfo":{"name":"gixo-docs-smoke","version":"1.0.0"}}}'
The initialize response includes an mcp-session-id header. Send it back on later requests:
curl -X POST https://gixo.ai/mcp \
-H "content-type: application/json" \
-H "accept: application/json, text/event-stream" \
-H "mcp-session-id: $MCP_SESSION_ID" \
-d '{"jsonrpc":"2.0","method":"notifications/initialized","params":{}}'
curl -X POST https://gixo.ai/mcp \
-H "content-type: application/json" \
-H "accept: application/json, text/event-stream" \
-H "mcp-session-id: $MCP_SESSION_ID" \
-d '{"jsonrpc":"2.0","id":2,"method":"tools/list","params":{}}'
Authenticated Execution
Authenticated execution uses a bearer token and the same user, team, and entitlement checks as the Gixo web app.
Authorization: Bearer YOUR_ACCESS_TOKEN
Clients that support OAuth protected-resource metadata can discover Gixo MCP auth metadata at:
https://gixo.ai/.well-known/oauth-protected-resource
Operational Notes
- Use
https://gixo.ai/mcpas the MCP server URL. - Deck creation needs a signed-in account; without one, the Lumen tools answer
sign_in_required. - Keep prompts explicit about whether you want a generated Lumen deck, read-only analysis, or authenticated execution.
- For API examples specific to Anthropic's Messages API, use /docs/claude-api-mcp.