Connect Mida to your AI agent

The server

One remote MCP server, authorized in your browser with your Mida account. No API keys to paste, no separate seat to buy.

Most clients take a small block of JSON. If yours does, this is it:

Transport is streamable HTTP. Auth is standard MCP OAuth with dynamic client registration, so your client registers itself and opens a browser the first time you connect. Nothing is stored on your machine.

Before you start

Three things worth knowing, in the order they bite.

1. 1. The tag has to be on your site

   Mida assigns visitors to variants from a small script on your pages. Nothing runs until it is installed. Ask your agent for the snippet with get_install_snippet, or grab it from your Mida dashboard. If a live test reports no visitors at all, check the tag before you check the targeting.

2. 2. Pick the right project first

   One Mida login can own several organizations and projects, and the session opens on a default project that is often not the one you mean. Tell your agent to run list_projects and select_project before anything else. A test in another project comes back as 404: Experiment not found, which reads like a deleted test when it is really a scoping miss.

3. 3. Your agent can write, not just read

   59 tools cover the whole loop: create experiments and goals, generate a preview URL, launch, read results with Mida's own statistics, conclude a test with a written conclusion, and serve the winner. New tests are created as drafts, so nothing reaches your visitors until you say so.