# Add Mosyn to Any MCP client

MCP URL: https://mosyn.lycatra.com/mcp

## Who can use it

The client must support remote MCP over HTTPS (Streamable HTTP) with OAuth sign-in. Clients that only run local (stdio) servers can use the mcp-remote bridge with Node.js 18 or newer.

## Steps

1. If the client asks for a remote MCP server URL, paste the Mosyn MCP URL and choose OAuth if it asks.
2. If it only runs local commands, use the mcp-remote entry below.

## Commands

Bridge for local-only clients:

```sh
npx -y mcp-remote https://mosyn.lycatra.com/mcp
```

## Config file

`Your client's MCP config`:

```json
{
  "mcpServers": {
    "mosyn": {
      "command": "npx",
      "args": [
        "-y",
        "mcp-remote",
        "https://mosyn.lycatra.com/mcp"
      ]
    }
  }
}
```

## Sign in

The client (or mcp-remote) opens Mosyn's approval page in the browser. If the client shows an eight-character code instead, type it in the Mosyn app under Settings → Connect an assistant → Have a code?

## Approve on your phone

A browser page from Mosyn opens with an eight-character code and a QR code. Open the Mosyn app on your phone and approve the request there (scan the QR code, tap the link on the phone, or type the code in Settings → Connect an assistant → Have a code?).

Never paste the code into a chat; it goes into the Mosyn app only.

## Check that it worked

The client lists Mosyn's tools; ask it to list your Mosyn sets.

## If something goes wrong

| What you see | What to do |
| --- | --- |
| mcp-remote keeps failing to sign in. | Delete ~/.mcp-auth and try again. |
| The client needs a fixed callback port. | Add a port after the URL: `npx -y mcp-remote https://mosyn.lycatra.com/mcp 9696`. |

## Sources

- https://modelcontextprotocol.io/specification/2025-06-18/basic/authorization
- https://github.com/geelen/mcp-remote

Last checked 2026-09-26. All assistants: https://mosyn.lycatra.com/connect.md
