You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Describe the bug
Currently, fields that are specified as type integer will result in a text field being displayed and a string being passed to the MCP server, which is not compliant to the JSON schema spec. The number type seems to be supported.
To Reproduce
Steps to reproduce the behavior:
Create an MCP server that has a field of type integer somewhere in the inputSchema
Try to pass an integer in the inspector
Observe that a string has been passed
Expected behavior
Only integers that are valid according to the JSON schema spec can and will be passed to integer fields.
Describe the bug
Currently, fields that are specified as type
integer
will result in a text field being displayed and a string being passed to the MCP server, which is not compliant to the JSON schema spec. Thenumber
type seems to be supported.To Reproduce
Steps to reproduce the behavior:
integer
somewhere in the inputSchemaExpected behavior
Only integers that are valid according to the JSON schema spec can and will be passed to integer fields.
Logs
N/A
Additional context
https://json-schema.org/understanding-json-schema/reference/numeric#integer
The text was updated successfully, but these errors were encountered: