Developer documentation

Connect to Meeem with MCP.

Connect an MCP-compatible assistant to Meeem. Learn OAuth permissions, available tools, Build Credits, progress polling and troubleshooting.

Using ChatGPT? Start with the account connection guide.

Endpoint and authorization

MCP (Model Context Protocol) lets a compatible assistant call Meeem tools on behalf of the connected account. Use a remote MCP client with OAuth support.

https://www.meeem.ai/mcp

Transport: Streamable HTTP. Authentication: OAuth authorization code with PKCE (S256). Add the endpoint in your client, select OAuth and complete Meeem sign-in and consent. Do not paste API keys or access tokens into a conversation.

Discovery metadata: Protected resource · Authorization server.

Available tools

Tool	Permission	Purpose
`get_profile`	`meeem:read`	Check the connected account.
`get_quota`	`meeem:read`	Read plan, Build Credits, app slots and build costs.
`list_projects`	`meeem:read`	List your owned apps, with pagination.
`get_project`	`meeem:read`	Read an app’s current version, links and recent operations.
`create_project`	`meeem:build`	Start a website, web app or browser game build.
`edit_project`	`meeem:build`	Edit an owned app at its expected version.
`get_operation`	`meeem:read`	Check build progress; optionally wait up to 20 seconds.
`set_feed_visibility`	`meeem:publish`	Publish or unpublish in the community feed.

Use your MCP client’s tools/list response for the full current input schemas. This connector does not expose project deletion or arbitrary server commands.

Create, wait, then edit

Call get_quota before starting a build and confirm the requested mode.
Call create_project with a unique requestId and a prompt. Quick is the default; use Studio only when explicitly requested.
Share progressUrl and poll get_operation using operationId. waitSeconds can be 0–20. An accepted operation is not yet a finished app: wait for succeeded, failed or interrupted.
Before editing, call get_project and pass its current version as expectedVersion. Reuse the same requestId and arguments when retrying the same action; use a new ID for a new action.
Call set_feed_visibility only when the user asks to publish or unpublish. It costs no Build Credits.

Example create_project arguments:

{
  "requestId": "create-vocabulary-001",
  "prompt": "Build an Arabic vocabulary game with five questions and a score.",
  "mode": "quick",
  "lang": "ar"
}

Prompts and edit instructions support up to 4,000 characters. Keep the returned operationId for progress and support requests.

Build Credits and limits

Quick builds and edits cost 1 Build Credit. Studio costs 5 Build Credits, requires Pro and is used only when you request it. Checking your account, credits and progress does not spend Build Credits.

Your Meeem saved-app allowance still applies. A ChatGPT subscription does not include Meeem Build Credits. See Meeem plans and credits.

Permissions, visibility and revocation

The assistant can access your account and owned projects within the permissions you approve. Read access includes your name, email, plan, credits and project details. Build access allows creation and editing; publishing access controls community-feed visibility.

A hosted app can be opened by anyone with its link while it is active under your plan. Keeping it out of the community feed does not make its link private. Publishing to the feed is a separate request.

Manage or disconnect assistants. Disconnecting stops future access; builds already started may finish. Privacy policy.

Troubleshooting

RECONNECT_REQUIRED — Reconnect the intended Meeem account.
INSUFFICIENT_SCOPE — Reconnect and approve the permission needed for this action.
STALE_VERSION — Read get_project again before submitting a new edit or visibility change.
RATE_LIMIT — Wait a minute, then retry. Keep the requestId unchanged for the same action.
Credit or saved-app limit errors: inspect get_quota and resolve the reported allowance before retrying.
Failed build: inspect get_operation for its error and credit status. Do not report success until status is succeeded.

Contact support with the project or operation ID. Never send passwords or authorization tokens.