See a style. Make it yours.

Settings → Connectors → Add custom connector

1. Open Settings → Connectors in Claude, on the web or in the desktop app.
2. Choose Add custom connector and paste the URL below. There is nothing else to fill in: no key, no token, no client id.
3. Claude opens this server’s sign-in page. Sign in, or create an account, and approve it.

https://ymotion.ai/mcp

Nothing else to fill in. Everything you make is filed under your own account.

Settings → Connectors → Advanced → Developer mode

1. Turn on Developer mode first, under Settings → Connectors → Advanced. Custom MCP connectors do not appear until you do.
2. Add a connector, paste the URL below, and give it a name.
3. It opens this server’s sign-in page. Sign in, or create an account, and approve it.

https://ymotion.ai/mcp

one command, from anywhere

1. Run the command below. No header and no key: the first call opens the sign-in page in your browser.
2. Add --scope user to have it in every project rather than this one.

claude mcp add --transport http ymotion https://ymotion.ai/mcp

Settings → MCP → Add new server, or ~/.cursor/mcp.json

1. Add the entry below to your MCP settings.
2. Cursor sends you to this server’s sign-in page the first time it connects.

{
  "mcpServers": {
    "ymotion": { "url": "https://ymotion.ai/mcp" }
  }
}

Copilot agent mode: .vscode/mcp.json, or the user-level mcp.json

1. Add the entry below. `"type": "http"` is what tells Copilot this is a remote server.
2. Start it from the MCP view and sign in when the browser opens.

{
  "servers": {
    "ymotion": { "type": "http", "url": "https://ymotion.ai/mcp" }
  }
}

~/.codeium/windsurf/mcp_config.json

1. Add the entry below and reload the MCP servers.
2. It sends you to this server’s sign-in page on the first call.

{
  "mcpServers": {
    "ymotion": { "serverUrl": "https://ymotion.ai/mcp" }
  }
}

Zed, Cline, or a script of your own that does not speak MCP

1. Any MCP client takes the same URL with no headers, and is sent to the sign-in page.
2. A plain HTTP caller can use `/tools` and `/call` instead, but that route needs a bearer token, and there is no self-service way to mint one yet: the OAuth flow hands its token to the client that walked it. On a hosted server, use an MCP client above.

https://ymotion.ai/mcp

GET  https://ymotion.ai/tools
POST https://ymotion.ai/call   {"name":"ymotion_help","arguments":{"topic":"overview"}}

The HTTP route needs a bearer token, and on a hosted server only whoever deployed it has one.