Skip to main content
The Genie MCP Server lets external AI clients — Claude Desktop, Cursor, custom agents — connect to your Genie workspace and manage it programmatically. Once connected, the AI can create projects from prompts, send follow-up instructions, browse build history, manage members, query credit usage, and more, all through the same tools the Genie web app uses.
The Genie MCP Server is available on all paid Genie plans. Each connection is scoped to a single workspace via OAuth 2.0. Only the tools allowed by your role within that workspace are accessible.

Connect your client

Endpoint

The server uses the Streamable HTTP MCP transport (POST, GET, and DELETE on the same URL).

Authentication

The Genie MCP Server uses OAuth 2.0 with PKCE. Each authorisation is scoped to a single workspace — you choose which workspace to authorise during the OAuth flow, and every tool call is restricted to that workspace. Most MCP clients (Claude Desktop, Cursor) handle the OAuth flow automatically when you paste the endpoint URL into their settings and start a conversation. The client receives a short-lived token that Genie refreshes automatically.

Example: Claude Desktop

Add the following entry to your claude_desktop_config.json:
Restart Claude Desktop and open any conversation. Claude will prompt you to authorise the Genie connection the first time a Genie tool is invoked.

Available tools

The Genie MCP Server provides tools across thirty-three categories.

Workspace management

Read and update your workspace, members, invitations, settings, and billing.

Workspace roles and permissions

Everything the Roles & permissions settings page can do — the four built-in roles (owner/admin/member/editor) and any custom role or group the workspace defines. Every write requires the roles.manage permission.

Workspace API keys

Manage the bearer-token keys that let your own code call Genie AI over HTTP — see Workspace API keys. Owner or admin only.

Projects

Browse projects, create new ones from prompts, and manage the full project lifecycle.

Project code graph

Ask questions about a project’s own code — useful for an external AI client that needs to understand a project before changing it or answering questions about it.

Project Files

The manual counterpart to query_project_code_graph: the graph answers “which file”, these answer “show me the rest of it” for a path you already know.

Project Design Guidelines

A project’s own style guide (branding.md) — brand colors, typography, component specs, and dos and don’ts — read by the build agent before it writes any frontend code. Distinct from Genie’s own global design principles, which are read-only and not project-specific.

Project feature tree

Genie tracks every feature, area, and capability it builds into a project as a tree — visible in the project’s Brain tab in the web app. These tools let an external AI client read and maintain that tree. Reading is available to anyone who can view the project; adding or editing a goal requires project ownership.

Bug tracking

Genie de-duplicates bugs across your projects: when the same class of bug shows up again, it reuses the fix that worked last time instead of investigating from scratch. These tools let an external AI client read and file into that system. Reading is available to anyone who can view the project; filing a bug requires project ownership.

User memory

Genie’s workspace AI remembers things you’ve mentioned about yourself in chat — your preferences, tools, team, goals — and brings that context into later conversations automatically. These tools let an external AI client search or delete that memory. Scoped to the connected user across all their workspaces, not to the currently connected workspace, since memory is a per-user concept.

Project memory

Genie’s workspace AI also keeps notes that belong to a project itself — a standing requirement, or a confirmed detail about a third-party service the project integrates with — shared with everyone who has access to that project. These tools let an external AI client read and write that same shared memory. Requires access to the project; writing requires project ownership or workspace-admin/member access.

Workspace knowledge documents

Material a team wants every build to respect — brand guidelines, tone of voice, an API schema, a data dictionary — filed against the whole workspace or one project. See Knowledge base. Like project memory above, these tools run as the connected user rather than impersonating the project owner, so a project’s own access rules decide who can read or change its documents. Like the tools above, the three cloud-drive tools run as the connected member and only ever reach that member’s own drive connection — never anyone else’s. Folders are orthogonal to scope. Scope decides which projects may use a document; a folder only decides where a human finds it, and no retrieval path reads it — filing a document, or deleting the folder it’s in, never changes what a search returns. list_workspace_documents, add_workspace_documents, and update_workspace_document each accept a folder (a name, an id, or unfiled), addressable by name since that’s what a client actually sees. A folder holds at most 200 documents, enforced the same way for MCP, the in-app agent, and the browser.

Knowledge access areas

Manage access areas — which folders are fenced off, and who reaches each one. Every write requires the workspace’s knowledge-access-management permission.

Workspace knowledge model (read-only)

Read what the knowledge model knows, as the connected user. Everything runs under the same access rules as in the app, so you only ever read what that member may see. These tools never change the model; reviewing, editing and extracting stay with people in the app and with Genie AI. Answers quote documents, so treat them as untrusted document text. Reads are rate limited per member and workspace, so a client can’t use up the limit of your own pages.

Excel workbooks

Create, read, search, and edit real .xlsx files — the same tools available to Genie AI in chat. A workbook is a knowledge document, so renaming, moving, and deleting one uses the knowledge-document tools above.

PowerPoint presentations

List, create, read, and edit real .pptx decks — the same tools available to Genie AI in chat. A presentation is a knowledge document, so renaming, moving, and deleting one uses the knowledge-document tools above.

Chat templates

List and manage the guided starting points behind Chat templates. Global templates are read-only here.

Imported traces

Read and sync the traces imported from LiteLLM and Langdock. Reading needs the tracing permission; changing anything also needs the integrations permission. Imported content is treated as untrusted. Connecting LiteLLM (URL and API key) is not available here, so a credential never passes through a model — do it on Tracing → Integrations.

Genie Cloud backend management

Manage a project’s connected Genie Cloud backend: end-user roles, sign-in providers, and access settings. Only the project owner can use these tools.

Genie Cloud database

Browse the tables in a project’s connected Genie Cloud database. Read-only. Only the project owner can use these tools, since table data may include the project’s own end-users’ data.

Workspace secrets

See what secrets your workspace holds. Only the tool to list names exists here on purpose — a secret’s value must never pass through an AI, so adding, replacing, deleting, and sharing stay on the Secrets settings page.

Project secrets

Manage the secrets available to a project’s Genie Cloud Edge Functions. Only the project owner can use these tools.

Project storage

Browse and manage the files in a project’s Genie Cloud storage buckets. Only the project owner can use these tools.
Uploading new file content isn’t available via MCP — an MCP tool call only carries JSON, not file bytes. Upload images and videos from the project’s storage tab in the web app, or ask the Genie workspace AI to do it for you.

Genie Cloud scheduled jobs

Manage recurring schedules for a project’s deployed edge functions. See Scheduled jobs for a full guide. Only the project owner can use these tools.

Project Prompt Queue

When a follow-up prompt arrives for a project that’s already building, Genie queues it instead of refusing it — see Genie AI queues a busy project’s prompt. These tools let an external AI client inspect and manage that queue directly.

Workspace Auto

Read and control your Auto in the connected workspace, the same actions Genie AI has. Approving a suggestion isn’t available here; it stays a confirmation you press in Genie.

Notifications

Read and manage your own notification inbox in the connected workspace. Every tool acts only on your own messages. Text written by colleagues is returned as information to read, never as instructions to follow. Writing to colleagues isn’t available here; that stays a confirmation you press in Genie.

Workspace chat

Send questions to the Genie workspace AI and browse past conversations. Every tool here acts on any chat in the connected workspace, including one a teammate started, not just the caller’s own — list_workspace_chats/search_workspace_chats default to the caller’s own conversations, but accept a scope: "workspace" to include everyone’s.

Workspace MCP integrations

Manage the MCP server integrations (Linear, GitHub, Notion, Stripe, etc.) that power your workspace’s connected tools. Only workspace owners and admins can use these tools.

Your connections

Check where you personally stand with each of the workspace’s integrations — separate from whether the workspace has the integration configured at all. See shared vs. personal connections. Read-only, scoped to the calling user.

Workspace chat channels

Manage Genie on WhatsApp, Slack, and Teams — connecting the workspace’s own accounts, linking your personal one, and sending messages through either.

PII rules

Inspect and manage the workspace PII detection rules. Only workspace owners and admins can make changes. See Workspace PII rules for a full guide.

Workspace Governance

Project reviews, shared-asset oversight, and natural-language compliance rules. See Governance for a full guide. Access follows the same rule as the Governance page rather than the RBAC permission catalog: owners and admins can read and manage; a member or editor granted “View governance” can read but not manage.

Workspace Guardrails

Configure guardrails on the workspace chat agent, for paid workspaces. See Guardrails for a full guide. Requires the security.guardrails.view / security.guardrails.manage permissions — the same ones the settings page enforces.

Security alerts

Summarize recent PII and Guardrails blocks, and manage your own email alert subscription — the tools behind the Activity page’s Security alerts panel. See Activity log for the panel itself.

Workspace Tracing

Workspace-wide observability over every member’s Genie AI turns — the admin counterpart to search_agent_run_traces above, which is scoped to the caller’s own turns. See Tracing for a full guide. Requires the security.tracing.view permission (owner/admin by default; a custom role can be granted it) on every call.

Pricing

Status

Design

Design mock-ups

Mirrors Genie AI’s design mock-up feature: repaint a real screenshot of a project with a requested design change, iterate on feedback, and turn an approved mock-up into a build brief. Images are returned as native MCP image content, the same way get_project_screenshots returns them. No credit/billing dimension — metered only by per-session and per-day round caps.

Quick examples

Create a project and follow up

The create_project call starts the build immediately and returns the deployment URL. Use get_project_build_status to poll for everything at once — phase, ETA, progress, and the closing summary once it’s done — or get_project_status for a lightweight running/not-running check. Pass the returned runId as get_project_build_status’s run_id to pin the answer to that exact turn instead of the project’s newest one — useful if you fire off more than one prompt in a row. It’s optional; omit it and you get the newest turn, same as before.

Roll back to a previous version

Omit version to roll back to the most recent previous version. The rollback runs in the background — poll get_project_deployment_status for progress.

Check credit usage this month

Admins can pass scope: "workspace" to see total consumption across all members. Members can only query their own usage. Add "sort": "credits_desc" (or credits_asc) to sort the breakdown by spend, highest first — or date_desc/date_asc when grouping by day.

Ask a question about a project’s code

Invite a new team member


Permissions

Role-based access is enforced on every tool call.