Connect a client

The doola MCP server lives at one URL:

https://mcp.doola.com

In many clients doola is a searchable app or connector — find it by name. In others, paste the URL above. In Claude Code and Grok Build it installs as a plugin, no URL needed. Either way, complete the OAuth sign-in, then prompt the agent: “Create a US LLC for me.”

Every client uses the same OAuth flow: find or add doola, then sign in to your existing doola account (or create one) and authorize. New users sign up during the flow. See Authentication for what happens under the hood.

Open Claude → Settings → Connectors.
Click Add custom connector.
Enter Name doola and MCP Server URL https://mcp.doola.com.
Click Add connector, then sign in to (or create) your doola account and complete the OAuth flow.
Start a new conversation — the doola tools are available.

Custom MCP connectors are available on supported Claude plans and workspaces.

doola ships an installable plugin, so there’s no URL to paste.

claude plugin marketplace add doolahq/plugins
claude plugin install doola@doola

Then run /reload-plugins, or restart Claude Code. The plugin’s MCP server is only registered when plugins load, so the doola tools won’t appear in the session you installed from until you do one of the two.The first doola tool call then triggers the OAuth flow: sign in to (or create) your doola account and authorize. Run /mcp to see the doola server and its connection state.

The same two commands work as slash commands inside the TUI: /plugin marketplace add doolahq/plugins, then /plugin install doola@doola.

To give a whole team the plugin without each person adding the marketplace, commit this to the project’s .claude/settings.json:

{
  "extraKnownMarketplaces": {
    "doola": {
      "source": { "source": "github", "repo": "doolahq/plugins" }
    }
  },
  "enabledPlugins": { "doola@doola": true }
}

Prefer not to install a plugin? Declare the server in the project’s .mcp.json instead, same shape as the Cursor tab, pointing at the URL at the top of this page.

doola ships as an installable plugin here too.

grok plugin marketplace add doolahq/plugins
grok plugin install doola@doola --trust

--trust is required. Grok refuses the install without it, because a plugin can run hooks, MCP servers and skills on your machine.Confirm it registered with grok inspect, which lists the server under MCP Servers as doola (http) plugin: doola. The first doola tool call triggers the OAuth flow: sign in to (or create) your doola account and authorize.

Grok Build reads Claude Code’s plugin configuration. If you already added the doola marketplace in Claude Code, grok plugin marketplace add reports it as already configured and you can go straight to the install.

You can also browse and install from inside the TUI with /marketplace.

Add to ~/.cursor/mcp.json:

{
  "mcpServers": {
    "doola": {
      "url": "https://mcp.doola.com"
    }
  }
}

Restart Cursor. doola appears in the MCP panel with a login / authorize prompt — click it, sign in to (or create) your doola account, and complete OAuth. The tools then appear under doola.

Open your Lovable project → Connectors → Add Custom Connector.
Select Add MCP Server and enter Name doola, MCP Server URL https://mcp.doola.com, Authentication OAuth.
Click Add & Authorize, then sign in to (or create) your doola account and complete the OAuth flow.
Return to your project — doola is available to the Lovable agent.

MCP support is available on supported Lovable Pro and Teams workspaces.

Open v0 → Settings → Integrations → Add MCP.
Select Custom MCP Server and enter Name doola and MCP Server URL https://mcp.doola.com.
Choose OAuth as the authentication method and click Add.
Sign in to (or create) your doola account and complete the OAuth flow.
Start a new conversation — doola is available in v0.

Every POST / requires a bearer token. The example below uses the initialize handshake of 2025-06-18; on 2026-07-28 there is no handshake and no session header, and each request instead carries its own _meta and request-metadata headers (see Authentication).1. Authenticate. A POST / without a token returns 401 with a WWW-Authenticate challenge pointing at the OAuth metadata — that’s what bootstraps discovery. Complete the OAuth flow (authorization code + PKCE, or client credentials) to get a bearer token; MCP clients do this for you. See Authentication.2. Initialize (with the bearer — mints a session ID):

curl -i -X POST https://mcp.doola.com/ \
  -H "Content-Type: application/json" \
  -H "Authorization: Bearer <token>" \
  -d '{
    "jsonrpc": "2.0",
    "id": 1,
    "method": "initialize",
    "params": {
      "protocolVersion": "2025-06-18",
      "capabilities": {},
      "clientInfo": { "name": "my-client", "version": "0.1" }
    }
  }'

3. List tools (echo the session ID + bearer):

curl -X POST https://mcp.doola.com/ \
  -H "Content-Type: application/json" \
  -H "Mcp-Session-Id: <uuid>" \
  -H "Authorization: Bearer <token>" \
  -d '{ "jsonrpc": "2.0", "id": 2, "method": "tools/list" }'

4. Call a tool — start every session with get_company_onboarding_status:

curl -X POST https://mcp.doola.com/ \
  -H "Content-Type: application/json" \
  -H "Mcp-Session-Id: <uuid>" \
  -H "Authorization: Bearer <token>" \
  -d '{
    "jsonrpc": "2.0",
    "id": 3,
    "method": "tools/call",
    "params": { "name": "get_company_onboarding_status", "arguments": {} }
  }'

Point your own agent at it

Agents and developers wiring up a custom client can read a compact reference straight off the server:

https://mcp.doola.com/.well-known/agents.md

It covers the connection details, what the server will and won’t do, and the full tool surface. No token needed. The tool section is generated from the server’s live tools/list contract, so it always matches what your client receives at runtime.

What the agent does next

The initialize response includes an instructions block telling the agent how to drive the flow. From there the agent calls get_company_onboarding_status, then loops on advance_company_onboarding, following the nextAction and nextActionInput on each response. See the end-to-end flow.

Get started

Tools

Reference

Point your own agent at it

What the agent does next

​Point your own agent at it

​What the agent does next

Point your own agent at it

What the agent does next