Bug Description
When trying to connect Cursor (or Windsurf) as an MCP client to the openclaw-mcp bridge, the connection fails with:
\
Incompatible auth server: does not support dynamic client registration
\\
Steps to Reproduce
- Run openclaw-mcp with docker:
- Image: ghcr.io/freema/openclaw-mcp:latest
- AUTH_ENABLED=false
- Port 3000 exposed
- Configure Cursor MCP with: url: http://localhost:3000/mcp
- See connection error in Cursor logs
Expected Behavior
Cursor should be able to connect to the MCP server without OAuth Dynamic Client Registration, or with a way to fully disable auth for local development.
Environment
- openclaw-mcp: v1.3.1
- Docker: 29.3.1
- Cursor: latest (MCP client)
Error Logs
\
[V2] Handling CreateClient action
Using OAuth scopes: mcp:tools
No stored client information found
Using redirect URL
Transient error connecting to streamableHttp server: Incompatible auth server: does not support dynamic client registration
Connection failed: Incompatible auth server: does not support dynamic client registration
\\
Workaround Attempted
Setting AUTH_ENABLED=false still results in OAuth authentication being enforced. The bridge appears to require OAuth regardless of this setting.
Bug Description
When trying to connect Cursor (or Windsurf) as an MCP client to the openclaw-mcp bridge, the connection fails with:
\
Incompatible auth server: does not support dynamic client registration
\\
Steps to Reproduce
Expected Behavior
Cursor should be able to connect to the MCP server without OAuth Dynamic Client Registration, or with a way to fully disable auth for local development.
Environment
Error Logs
\
[V2] Handling CreateClient action
Using OAuth scopes: mcp:tools
No stored client information found
Using redirect URL
Transient error connecting to streamableHttp server: Incompatible auth server: does not support dynamic client registration
Connection failed: Incompatible auth server: does not support dynamic client registration
\\
Workaround Attempted
Setting AUTH_ENABLED=false still results in OAuth authentication being enforced. The bridge appears to require OAuth regardless of this setting.