Technically this isn't a bug.
But the landscape is wide, most MCP implementations are for Claude, and this behaves differently from Claude in an unimportant but RFC-compliant way.
However, if it behaved more like Claude in its RFC-compliant way, it would be compatible with more tools.
Which version of LM Studio Bionic?
Example: LM Studio 1.1.1+5
Which operating system?
macOS
What is the bug?
MCP registration doesn't specify { "grant_types": ["authorization_code"], "response_types": ["code"] }, but it could which would be more clear and more compatible - because that's what Claude does.
Screenshots
N/A
Logs
N/A
To Reproduce
Steps to reproduce the behavior:
- Go to 'Settings'
- Click on 'Connected Apps'
- Scroll down to 'Manual MCP server setup'
+ Add Custom MCP
- Connect to an MCP that's only been tested against Claude's MCP and follows that rather than a perfect RFC implementation, see error about grant_types.
Technically this isn't a bug.
But the landscape is wide, most MCP implementations are for Claude, and this behaves differently from Claude in an unimportant but RFC-compliant way.
However, if it behaved more like Claude in its RFC-compliant way, it would be compatible with more tools.
Which version of LM Studio Bionic?
Example: LM Studio 1.1.1+5
Which operating system?
macOS
What is the bug?
MCP registration doesn't specify
{ "grant_types": ["authorization_code"], "response_types": ["code"] }, but it could which would be more clear and more compatible - because that's what Claude does.Screenshots
N/A
Logs
N/A
To Reproduce
Steps to reproduce the behavior:
+ Add Custom MCP