Connect clients

Setup is the same in every client: enter the URL https://mcp.sinfonia.live/mcp and sign in through the browser. There is no token to generate and no key to copy.

How sign-in works

The first time the client accesses Sinfonia, it opens the browser with three screens:

Sign in

Enter your Sinfonia username (or e-mail) and password.

Verification code

Type the 6-digit code sent to your e-mail. It is valid for 90 seconds.

Authorization

Review the client requesting access, your Account, your Profile and the read and write permissions. Click Authorize to finish or Cancel to deny access.

Note

The session lasts 24 hours. After that, the client asks you to sign in again.

Setup per client

Add the server:

claude mcp add --transport http sinfonia https://mcp.sinfonia.live/mcp

Then, inside Claude Code, run /mcp, select sinfonia and choose Authenticate to open the sign-in page in the browser.

Add the server:

gemini mcp add --transport http sinfonia https://mcp.sinfonia.live/mcp

Or edit ~/.gemini/settings.json:

{
  "mcpServers": {
    "sinfonia": { "httpUrl": "https://mcp.sinfonia.live/mcp" }
  }
}

Then, inside Gemini CLI, run /mcp auth sinfonia to sign in.

Edit ~/.cursor/mcp.json (or .cursor/mcp.json in the project):

{
  "mcpServers": {
    "sinfonia": { "url": "https://mcp.sinfonia.live/mcp" }
  }
}

In Settings → MCP, click Connect next to sinfonia to sign in.

Create a .vscode/mcp.json file in the project (or use MCP: Add Server from the command palette):

{
  "servers": {
    "sinfonia": {
      "type": "http",
      "url": "https://mcp.sinfonia.live/mcp"
    }
  }
}

Start the server from the file itself and sign in when VS Code prompts you.

Warning

Command-line clients (Claude Code, Codex and Gemini CLI) open the browser on the local machine to sign in. Because of that, they don’t work over SSH sessions without port forwarding.

Other clients

Any client that supports remote MCP over Streamable HTTP with OAuth works. If you don’t know where to configure yours, paste the prompt below into the assistant itself and it will do the setup:

Configure Sinfonia's remote MCP server in my client. Sinfonia is an RPA automation orchestrator.

- Server name: sinfonia
- URL: https://mcp.sinfonia.live/mcp
- Transport: Streamable HTTP (not SSE or stdio)
- Authentication: OAuth 2.1 with PKCE and dynamic client registration (RFC 7591).
  There is no client_id, client secret, token or API key to configure: the client
  discovers the authorization server at
  https://mcp.sinfonia.live/.well-known/oauth-protected-resource, registers
  itself and opens the browser to sign in.

Steps:
1. Find out which client and version I use and where it stores MCP configuration
   (CLI command or configuration file). If you don't know, ask me.
2. Add the server with the details above, without fixed authorization headers.
3. Tell me how to start sign-in. In the browser, I will enter my Sinfonia
   username and password, the 6-digit code sent by e-mail and authorize access.
4. Confirm that the server's tools (listar_bots, listar_execucoes etc.)
   are available.

If the client does not support remote MCP over HTTP with OAuth, tell me instead
of improvising another authentication method.

Check the connection

After signing in, ask the assistant: “Which bots do I have in Sinfonia?”. If it replies with your bot list, the connection is working. See more ideas in Usage examples.

Last updated on 02/11/2026

Tools and permissions