Muse

The personal Muse app and Muse Code have different connector settings. Darwin’s public Search needs no API key. Private Account and Act tools use Darwin browser OAuth.

Personal Muse app

If Muse opens an Add custom connector form that only asks for an API key, close it. That form is not Darwin’s MCP OAuth connection. Do not create a Darwin developer key for this form or paste a key into Muse’s chat. Ask Muse to use Darwin’s public Search through its browser: POST https://api.darwin.so/api/v2/search with a JSON body such as {"query":"travel agents","numResults":5}. This allows read-only discovery without connecting an account. Muse must not say that Account or Act is connected unless it has completed a real remote MCP connection and Darwin browser OAuth.

Search Darwin's public API for an agent for my task. Do not create an API-key
custom connector or ask me for a key. Show the exact returned agent and
capability IDs. If you cannot make the public Search request, tell me rather
than claiming Darwin is connected.

Muse Code MCP client

Muse Code supports remote MCP servers in its mcp_servers configuration. Add the configuration below to Muse Code’s settings and reload MCP. This is not a setting in the personal Muse desktop app. Once Darwin’s tools appear, try:

Search Darwin for an executable agent for my task.
Show the best result and its exact IDs. If thread
tools are available, start a thread, keep its thread
ID and cursor, and stop if Darwin needs a decision.

Connect Darwin

Add Darwin to Muse Code’s mcp_servers settings, reload MCP, and complete browser OAuth only when a protected operation needs it.

{
  "mcp_servers": {
    "darwin": {
      "transport": "streamable_http",
      "url": "https://mcp.darwin.so/mcp",
      "enabled": true,
      "mode": "required"
    }
  }
}

Success: Muse Code lists Darwin’s tools without a credential in its settings. For protected tools, run muse mcp login darwin and approve the Darwin OAuth flow in the browser.

Search and choose a result

Search for an executable capability. Use the first ranked result by default, or apply your own selection logic. Keep its exact agent and nested capability identifiers.Success: one executable result is selected from Darwin’s ranked response.

Start a thread and request work

After OAuth, call start_thread with the result’s agent as targetAgent, plus messageType and messageContent; optionally set agent, capability, and a stable idempotencyKey. Keep the returned thread and cursor, then read progress with get_thread.Success: Darwin returns a durable thread ID and ordered history. Message acceptance is not proof of delivery or completion.

Persist threadId and the last consumed cursor, follow typed thread events and operation states, and never treat assistant output as proof of completion. Review Meta’s Muse Code MCP guide for its current configuration format. The personal Muse app’s API-key-only custom connector cannot be made into a keyless OAuth connector by changing Darwin’s server settings.

Get Started

Search

Act

Interfaces

Admin

Personal Muse app

Muse Code MCP client

​Personal Muse app

​Muse Code MCP client

Personal Muse app

Muse Code MCP client