# Other Clients

# Connect Any Other MCP Client

Monad's MCP server is a standard remote endpoint. Any client that supports **remote MCP servers over HTTP with OAuth** can connect — the guides in this section cover the ones we have verified, not the limit of what works.

```
https://app.monad.com/mcp
```

## What a client needs to support

| Requirement | Why |
|---|---|
| **Streamable HTTP transport** | The server is remote. There is no local process to launch. |
| **OAuth 2.1 with dynamic client registration** | The client registers itself and runs the authorization flow. No client id or secret is issued to you by hand. |

If a client supports both, configuration is usually just the URL - there is no API key to paste anywhere. A client that does not support both cannot connect to Monad today.

## Typical configuration

Most clients use one of two JSON shapes. If the documentation does not say which, try the first:

```json
{
  "mcpServers": {
    "monad": {
      "url": "https://app.monad.com/mcp"
    }
  }
}
```

```json
{
  "servers": {
    "monad": {
      "type": "http",
      "url": "https://app.monad.com/mcp"
    }
  }
}
```

Whichever it uses, the client should open your browser to Monad's consent screen the first time it connects.

## Verifying any client

Whatever the client, the check is the same. Ask for something read-only:

> List my Monad pipelines

If you get your pipelines back, the connection is live. Then see **[Using the MCP](/guides/mcp-usage)**.

## Discovery endpoints

If a client asks for these directly rather than discovering them, or you are debugging a connection:

| | |
|---|---|
| MCP endpoint | `https://app.monad.com/mcp` |
| Protected resource metadata | `https://app.monad.com/.well-known/oauth-protected-resource/mcp` |
| Authorization server | `https://app.monad.com/api/v2/oauth` |

Well-behaved clients find all of this from the MCP endpoint alone.

## Troubleshooting

**The client connects but never prompts you to log in.**
It is probably treating the server as unauthenticated. Check it supports OAuth for remote MCP servers — not every client that supports remote servers does.

**The client wants an API key or bearer token.**
Monad's MCP server does not accept one - it is OAuth-only. A client that cannot run the OAuth flow cannot connect.

For anything not specific to your client — refused requests, missing organizations, writes being denied — see [Troubleshooting](/mcp/index#troubleshooting) on the overview page.