Coding-agent setup

Give your coding agent the public World ID integration guides to help implement your integration. The guides are available directly, without sign-in, a plugin, or an MCP connection. Add the developer MCP server when you want the agent to register or manage your application through tools.

Give your coding agent the guide

Copy this prompt into your coding agent:

Read https://auth.world.org/docs/guides/coding-agent-setup.md and follow its instructions to integrate World ID into this project.

Connect your coding agent

For optional app management through tools, add https://auth.world.org/mcp/developer in Codex, Claude Code, or another coding agent's MCP settings as a Streamable HTTP server with OAuth. Configure this developer connection separately from the consumer World ID plugin. Use a separate connection name for each environment:

The coding agent must support Client ID Metadata Documents (CIMD): it publishes and supplies its own metadata URL. Connecting the coding agent requires no portal OIDC registration or client secret. Dynamic client registration (DCR) is not implemented. If your host does not support this connection, use the public guides and portal directly.

Keep the connection, guides, app registration, and credentials in the same production or sandbox environment. Before authorizing, confirm that the current session lists the developer MCP server at https://auth.world.org/mcp/developer. Call list_idp_guides to check the connection; it requires no authorization.

The commands below use this page's environment. For sandbox, replace world-id-developer with world-id-developer-sandbox in every command. When switching environments, use both the matching name and URL from the table.

Codex CLI

Run codex mcp list in the environment where your coding session runs. If the developer endpoint is already configured, use its existing name. Otherwise add it:

codex mcp add world-id-developer --url https://auth.world.org/mcp/developer

For app management, authorize only the developer scope:

codex mcp login world-id-developer --scopes developer-portal:manage

Claude Code

Run claude mcp list to check for an existing connection. If it is missing, add it:

claude mcp add --transport http --scope user world-id-developer https://auth.world.org/mcp/developer

For app management, start Claude Code and run /mcp. Select the configured server and follow the browser sign-in flow. The --scope user option controls where Claude Code stores the configuration; portal access uses the separate OAuth permission developer-portal:manage.

Check the connection

Complete Google sign-in and consent in the browser when authorizing portal access.

If the tools are unavailable, first check whether the developer server is listed and enabled in the active host. Add it only if it is missing; otherwise use the host's refresh controls. Start a new coding session if the host needs one to load new tools. A desktop or workspace host manages its own connection; configuring a separate CLI does not establish that the active chat can use it.

Ask the agent to list the World ID integration guides to confirm the connection. Reading guides requires no authorization. For app management, ask the agent to check developer access and follow the Google sign-in and portal consent prompt.