Connect another MCP client

Kyno exposes a remote MCP endpoint at:

https://console.kyno.work/mcp

Use the Streamable HTTP transport and OAuth. A common configuration shape is:

{
  "mcpServers": {
    "kyno": {
      "url": "https://console.kyno.work/mcp"
    }
  }
}

The exact file name and sign-in button depend on the MCP client. After adding the server, complete the browser sign-in and confirm that the client can list Kyno’s tools.

Check before deploying

Your client must support:

• Remote Streamable HTTP MCP servers.
• OAuth for a protected MCP server.
• Tool calls with structured JSON arguments.

Important: Kyno uses MCP protocol version 2025-11-25. If a client cannot connect, confirm that it supports this protocol version and remote OAuth.