Connect a client - doola Developers

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. 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.

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. Capture the Mcp-Session-Id header from initialize and echo it on every later request; attach Authorization: Bearer <token> to every call.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": {} }
  }'

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.

​What the agent does next

What the agent does next