MeroFoundry Quick Start

This is the initial setup for a new user who has registered, confirmed their email address, and wants an interactive agent to build their first MeroFoundry application. The hosted MCP uses OAuth; you do not need to create or copy an API key.

Connect your agent

Install the connector for supported local agents with npx @merofoundry/connect.

Add a custom remote MCP connector named MeroFoundry with this server URL:

https://platform.merofoundry.com/mcp

Leave optional OAuth client ID, client secret, and static bearer-token fields blank. Select Connect, then sign in to MeroFoundry in the browser and review the client name, workspace, requested permissions, and token lifetime before approving consent.

If the workspace has no applications, consent explains that the connector can create exactly one first application. That bootstrap grant cannot author models, pages, records, domains, or other application resources.

Create your first application

After connecting, enable the MeroFoundry connector for the conversation and ask the agent to create an application. Give it a name and a URL-safe slug. For example:

Use MeroFoundry to create my first application. Name it Customer Portal and use
customer-portal as its slug.

Complete the second MeroFoundry authorization when prompted. This second exchange is expected: the first application consumes the one-use workspace bootstrap grant, and reauthorization gives the agent a normal grant bound to the new application. If the client does not prompt automatically, disconnect and reconnect the MeroFoundry connector.

You can now ask the agent to build, style, publish, and verify the application. Ask it to finish by reporting the assigned public URL and checking that URL without an authenticated session.

Verify the published site visually

After building and publishing, capture the home page and the whole published site, inspect the screenshots and their diagnostics, repair, and recapture until the evidence is clean. The canonical build -> capture -> inspect -> repair loop, its executable examples, and the diagnostic remediation guide live in the MCP tool reference.

a successful authoring API response is not visual evidence

screenshots do not replace keyboard, accessibility, form-submission, or navigation tests

Claude

In Claude, open Customize > Connectors, select + > Add custom connector, enter MeroFoundry and the /mcp URL above, leave Advanced settings empty, and select Connect. Complete MeroFoundry login and consent, then enable the connector from the conversation’s + > Connectors menu.

For Claude Team or Enterprise, an Owner or Primary Owner must first add the custom web connector in the organization’s connector settings. Each member connects it using their own MeroFoundry account.

Codex

Add the Streamable HTTP server and start OAuth from the Codex CLI:

codex mcp add merofoundry --url https://platform.merofoundry.com/mcp
codex mcp login merofoundry --oauth-client-registration dcr

The login command opens the MeroFoundry browser flow. Use /mcp in the Codex TUI to inspect the connection, and run the login command again after the first application is created. Do not use --bearer-token-env-var with a MeroFoundry API key.

In the ChatGPT desktop app or Codex IDE extension, add a Streamable HTTP server with the same URL, restart when asked, and select Authenticate.

Agy

Add the hosted server to ~/.gemini/config/mcp_config.json:

{
  "mcpServers": {
    "merofoundry": {
      "serverUrl": "https://platform.merofoundry.com/mcp"
    }
  }
}

Restart Agy, open its MCP server panel, and select Authenticate for merofoundry. Authenticate again after first-application creation consumes the bootstrap credential.

Credentials and packages

The hosted interactive MCP sends its OAuth access token as Authorization: Bearer .... It never needs to see or store an application API key.

The merofoundry-client package, which is the basis of the SDK, is a headless integration surface and continues to use an application API key in X-API-Key. The separately operated merofoundry-mcp package is deprecated as of 2026-09-02; use the hosted MCP above instead. Do not put an application API key in an OAuth bearer-token field, and do not put an OAuth access token in X-API-Key.

See Connect an agent for discovery URLs, client compatibility rules, and troubleshooting.