feat(router): typed custom scalars in MCP tool schemas with scalar_mappings overrides

docs-website/router/mcp/configuration.mdx

@@ -39,6 +39,7 @@ storage_providers:
 | `enable_arbitrary_operations` | Enables the `execute_graphql` built-in tool, allowing clients to run arbitrary GraphQL operations beyond the pre-defined operation set.                                                                                                                                      | `false`          |
 | `expose_schema`               | Enables the `get_schema` built-in tool, exposing the full GraphQL schema to MCP clients.                                                                                                                                                                                     | `false`          |
 | `omit_tool_name_prefix`       | When enabled, MCP tool names omit the `execute_operation_` prefix. For example, `GetUser` becomes `get_user` instead of `execute_operation_get_user`. See [Operations - Omitting the Tool Name Prefix](/router/mcp/operations#omitting-the-tool-name-prefix).                | `false`          |
+| `scalar_mappings`             | Maps custom scalar type names to the JSON Schema type advertised in MCP tool input schemas. Allowed values: `string`, `integer`, `number`, `boolean`, `object`, `array`. Custom scalars without a mapping default to `string`. See [Custom Scalar Mappings](#custom-scalar-mappings). | -                |
 
 For OAuth-specific configuration, see [OAuth 2.1 Authorization](/router/mcp/oauth/overview).
 
@@ -59,9 +60,35 @@ All MCP options can also be set via environment variables:
 | `MCP_ENABLE_ARBITRARY_OPERATIONS` | `mcp.enable_arbitrary_operations` |
 | `MCP_EXPOSE_SCHEMA`               | `mcp.expose_schema`               |
 | `MCP_OMIT_TOOL_NAME_PREFIX`       | `mcp.omit_tool_name_prefix`       |
+| `MCP_SCALAR_MAPPINGS`             | `mcp.scalar_mappings`             |
+
+Map-valued options use comma-separated `key:value` pairs. For example: `MCP_SCALAR_MAPPINGS=JSON:object,BigInt:integer`.
 
 For OAuth-related environment variables, see [OAuth Configuration Reference](/router/mcp/oauth/configuration#environment-variables).
 
+## Custom Scalar Mappings
+
+The router generates each tool's input schema from the variables of the GraphQL operation. Custom scalars are opaque to JSON Schema, but MCP clients require every property to declare a type. The router therefore advertises custom scalar variables as `string` by default. This matches the wire format of most opaque scalars, such as cursors, IDs, and timestamps.
+
+Use `scalar_mappings` for custom scalars whose wire format is not a string:
+
+```yaml
+mcp:
+  enabled: true
+  scalar_mappings:
+    JSON: object
+    BigInt: integer
+```
+
+Two behaviors help you keep mappings correct:
+
+- On startup, the router logs a warning that lists every custom scalar that fell back to the `string` default. Non-string arguments for these scalars are rejected by input validation, so add a mapping for any scalar with a different wire format.
+- A mapping with a value outside the allowed set fails router startup. A wrong schema contract is a configuration error, not a warning.
+
+<Note>
+  Top-level variables with an `object` type are always advertised as non-nullable in the generated schema. A nullable variable mapped to `object` therefore loses its `null` union in the tool's input schema.
+</Note>
+
 ## Storage Providers
 
 MCP loads operations from a configured storage provider. Currently, only the `file_system` provider is supported:
@@ -112,6 +139,9 @@ mcp:
   enable_arbitrary_operations: false
   expose_schema: false
   omit_tool_name_prefix: false
+  scalar_mappings:
+    JSON: object
+    BigInt: integer
   storage:
     provider_id: 'mcp'
 

docs-website/router/mcp/operations.mdx

@@ -102,6 +102,8 @@ Operations are converted to `snake_case` for tool naming consistency.
 
 The tool's input schema is automatically generated from your GraphQL operation's variables, ensuring type safety. AI models use this schema to understand what parameters are required and their types.
 
+Custom scalar variables are advertised as `string` by default. See [Custom Scalar Mappings](/router/mcp/configuration#custom-scalar-mappings) to map scalars with a different wire format.
+
 ### Omitting the Tool Name Prefix
 
 By default, all operation tools include the `execute_operation_` prefix. You can enable `omit_tool_name_prefix` to generate shorter tool names:

router-tests/protocol/mcp_test.go

@@ -242,6 +242,72 @@ func TestMCP(t *testing.T) {
 				})
 			})
 
+			t.Run("Custom scalar variables carry a JSON Schema type in tool input schemas", func(t *testing.T) {
+				testenv.Run(t, &testenv.Config{
+					MCPOperationsPath: "testdata/mcp_operations_custom_scalar",
+					MCP: config.MCPConfiguration{
+						Enabled: true,
+					},
+				}, func(t *testing.T, xEnv *testenv.Environment) {
+
+					toolsRequest := mcp.ListToolsRequest{}
+					resp, err := xEnv.MCPClient.ListTools(xEnv.Context, toolsRequest)
+					require.NoError(t, err)
+					require.NotNil(t, resp)
+
+					var tool *mcp.Tool
+					for i := range resp.Tools {
+						if resp.Tools[i].Name == "execute_operation_upload_file" {
+							tool = &resp.Tools[i]
+							break
+						}
+					}
+					require.NotNil(t, tool, "expected the UploadFile operation to be registered as a tool")
+
+					fileSchema, ok := tool.InputSchema.Properties["file"].(map[string]any)
+					require.True(t, ok, "expected a schema object for the 'file' variable, got: %#v", tool.InputSchema.Properties)
+
+					actual, err := json.Marshal(fileSchema)
+					require.NoError(t, err)
+
+					// Custom scalars are opaque to JSON Schema, but MCP tool consumers
+					// (Anthropic directory validation, OpenAI strict mode) reject input
+					// schema properties that declare no "type". Opaque scalars must carry
+					// a best-effort primitive type: string.
+					require.Contains(t, fileSchema, "type", "custom scalar variable 'file' must declare a JSON Schema type, got: %s", actual)
+					assert.Equal(t, "string", fileSchema["type"], "custom scalar variable 'file' should be typed as a string, got: %s", actual)
+				})
+			})
+
+			t.Run("Scalar mapping overrides the string default for a mapped custom scalar", func(t *testing.T) {
+				testenv.Run(t, &testenv.Config{
+					MCPOperationsPath: "testdata/mcp_operations_custom_scalar",
+					MCP: config.MCPConfiguration{
+						Enabled:        true,
+						ScalarMappings: map[string]string{"Upload": "object"},
+					},
+				}, func(t *testing.T, xEnv *testenv.Environment) {
+					toolsRequest := mcp.ListToolsRequest{}
+					resp, err := xEnv.MCPClient.ListTools(xEnv.Context, toolsRequest)
+					require.NoError(t, err)
+
+					var tool *mcp.Tool
+					for i := range resp.Tools {
+						if resp.Tools[i].Name == "execute_operation_upload_file" {
+							tool = &resp.Tools[i]
+							break
+						}
+					}
+					require.NotNil(t, tool, "expected the UploadFile operation to be registered as a tool")
+
+					fileSchema, ok := tool.InputSchema.Properties["file"].(map[string]any)
+					require.True(t, ok, "expected a schema object for the 'file' variable")
+
+					// The mapping replaces the string default; Upload! is non-null so no null union.
+					require.Equal(t, "object", fileSchema["type"], "mapped custom scalar should carry the configured type")
+				})
+			})
+
 			t.Run("List user Operations / Static operations of type mutation aren't exposed when excludeMutations is set", func(t *testing.T) {
 				testenv.Run(t, &testenv.Config{
 					MCP: config.MCPConfiguration{

router-tests/protocol/testdata/mcp_operations_custom_scalar/UploadFile.graphql

@@ -0,0 +1,4 @@
+# This mutation uploads a single file.
+mutation UploadFile($file: Upload!) {
+  singleUpload(file: $file)
+}

router/core/router.go

@@ -1200,6 +1200,7 @@ func (r *Router) startMCPServer(ctx context.Context) error {
 		mcpserver.WithEnableArbitraryOperations(r.mcp.EnableArbitraryOperations),
 		mcpserver.WithExposeSchema(r.mcp.ExposeSchema),
 		mcpserver.WithOmitToolNamePrefix(r.mcp.OmitToolNamePrefix),
+		mcpserver.WithScalarMappings(r.mcp.ScalarMappings),
 		mcpserver.WithStateless(r.mcp.Session.Stateless),
 	}
 

router/go.mod

@@ -80,6 +80,7 @@ require (
 	github.com/posthog/posthog-go v1.5.5
 	github.com/pquerna/cachecontrol v0.2.0
 	github.com/prometheus/otlptranslator v1.0.0
+	github.com/santhosh-tekuri/jsonschema/v5 v5.3.1
 	github.com/santhosh-tekuri/jsonschema/v6 v6.0.1
 	github.com/tonglil/opentelemetry-go-datadog-propagator v0.1.3
 	github.com/wundergraph/astjson v1.1.0

router/internal/jsonschema/nullable_2020_12_test.go

@@ -0,0 +1,103 @@
+package jsonschema
+
+import (
+	"encoding/json"
+	"testing"
+
+	"github.com/santhosh-tekuri/jsonschema/v5"
+	"github.com/stretchr/testify/require"
+
+	"github.com/wundergraph/graphql-go-tools/v2/pkg/astparser"
+)
+
+// TestNullableFieldsAreJSONSchema2020_12 verifies that the generator expresses
+// nullability in the JSON Schema 2020-12 form rather than the OpenAPI 3.0
+// keyword `"nullable": true` (which standard validators silently ignore).
+//
+// Concretely: a payload that contains explicit `null` values for nullable
+// scalar, enum, and recursive-ref fields must validate cleanly against the
+// generated schema using a strict standard JSON Schema validator.
+func TestNullableFieldsAreJSONSchema2020_12(t *testing.T) {
+	schemaSDL := scalarDefinitions + `
+		schema { query: Query }
+
+		type Query {
+			processFormula(tree: FormulaNodeInput): Boolean
+			doThing(input: ThingInput): Boolean
+		}
+
+		input ThingInput {
+			name: String
+			count: Int
+			rating: Float
+			active: Boolean
+			status: Status
+		}
+
+		enum Status { ACTIVE INACTIVE }
+
+		input FormulaNodeInput {
+			nodeType: NodeType!
+			left:  FormulaNodeInput
+			right: FormulaNodeInput
+			value: Float
+		}
+
+		enum NodeType { CONSTANT BINARY_OPERATION }
+	`
+
+	operationSDL := `
+		query Run($tree: FormulaNodeInput, $input: ThingInput) {
+			processFormula(tree: $tree)
+			doThing(input: $input)
+		}
+	`
+
+	definitionDoc, report := astparser.ParseGraphqlDocumentString(schemaSDL)
+	require.False(t, report.HasErrors(), "schema parsing failed: %s", report.Error())
+
+	operationDoc, report := astparser.ParseGraphqlDocumentString(operationSDL)
+	require.False(t, report.HasErrors(), "operation parsing failed: %s", report.Error())
+
+	schema, err := BuildJsonSchema(&operationDoc, &definitionDoc)
+	require.NoError(t, err)
+
+	schemaJSON, err := json.Marshal(schema)
+	require.NoError(t, err)
+
+	compiled, err := jsonschema.CompileString("schema.json", string(schemaJSON))
+	require.NoError(t, err, "generated JSON schema should compile")
+
+	// Nullable scalars and enum: explicit null values must be accepted.
+	t.Run("explicit nulls accepted for nullable scalar and enum fields", func(t *testing.T) {
+		const payloadJSON = `{
+			"input": {
+				"name":   null,
+				"count":  null,
+				"rating": null,
+				"active": null,
+				"status": null
+			}
+		}`
+		var payload any
+		require.NoError(t, json.Unmarshal([]byte(payloadJSON), &payload))
+		require.NoError(t, compiled.Validate(payload),
+			"nullable scalar/enum fields must accept explicit null per JSON Schema 2020-12")
+	})
+
+	// Nullable recursive $ref: a leaf may explicitly set left/right to null
+	// (rather than omitting them) and the schema must accept it.
+	t.Run("explicit nulls accepted for nullable recursive ref fields", func(t *testing.T) {
+		const payloadJSON = `{
+			"tree": {
+				"nodeType": "BINARY_OPERATION",
+				"left":  { "nodeType": "CONSTANT", "value": 1, "left": null, "right": null },
+				"right": null
+			}
+		}`
+		var payload any
+		require.NoError(t, json.Unmarshal([]byte(payloadJSON), &payload))
+		require.NoError(t, compiled.Validate(payload),
+			"nullable recursive ref fields must accept explicit null per JSON Schema 2020-12")
+	})
+}

router/internal/jsonschema/recursive_input_test.go

@@ -0,0 +1,89 @@
+package jsonschema
+
+import (
+	"encoding/json"
+	"testing"
+
+	"github.com/santhosh-tekuri/jsonschema/v5"
+	"github.com/stretchr/testify/require"
+
+	"github.com/wundergraph/graphql-go-tools/v2/pkg/astparser"
+)
+
+// TestRecursiveInputAcceptsNestedPayload verifies that a self-recursive GraphQL
+// input type produces a JSON Schema that accepts arbitrarily nested payloads.
+//
+// A self-recursive input type cannot be represented by inlining and truncating
+// at a fixed recursion depth: the recursive fields get dropped from the schema,
+// and because every object is emitted with `additionalProperties: false`, a
+// valid nested payload is then rejected at the validation boundary with
+// "additional properties '...' not allowed". The schema must instead reference
+// the recursive type so that nesting is permitted to any depth.
+func TestRecursiveInputAcceptsNestedPayload(t *testing.T) {
+	schemaSDL := scalarDefinitions + `
+		schema { query: Query }
+
+		type Query {
+			createColumn(input: ColumnInput!): Boolean
+		}
+
+		input ColumnInput {
+			node: FormulaNodeInput!
+		}
+
+		input FormulaNodeInput {
+			nodeType: NodeType!
+			left: FormulaNodeInput
+			right: FormulaNodeInput
+			value: Float
+		}
+
+		enum NodeType {
+			CONSTANT
+			BINARY_OPERATION
+		}
+	`
+
+	operationSDL := `
+		query CreateColumn($input: ColumnInput!) {
+			createColumn(input: $input)
+		}
+	`
+
+	definitionDoc, report := astparser.ParseGraphqlDocumentString(schemaSDL)
+	require.False(t, report.HasErrors(), "schema parsing failed: %s", report.Error())
+
+	operationDoc, report := astparser.ParseGraphqlDocumentString(operationSDL)
+	require.False(t, report.HasErrors(), "operation parsing failed: %s", report.Error())
+
+	schema, err := BuildJsonSchema(&operationDoc, &definitionDoc)
+	require.NoError(t, err)
+
+	schemaJSON, err := json.Marshal(schema)
+	require.NoError(t, err)
+
+	compiled, err := jsonschema.CompileString("schema.json", string(schemaJSON))
+	require.NoError(t, err, "generated JSON schema should compile")
+
+	// A depth-2 expression tree: the inner BINARY_OPERATION node has its own
+	// left/right children, exercising recursion beyond a single level.
+	const payloadJSON = `{
+		"input": {
+			"node": {
+				"nodeType": "BINARY_OPERATION",
+				"left": {
+					"nodeType": "BINARY_OPERATION",
+					"left":  { "nodeType": "CONSTANT", "value": 1 },
+					"right": { "nodeType": "CONSTANT", "value": 2 }
+				},
+				"right": { "nodeType": "CONSTANT", "value": 3 }
+			}
+		}
+	}`
+
+	var payload any
+	require.NoError(t, json.Unmarshal([]byte(payloadJSON), &payload))
+
+	err = compiled.Validate(payload)
+	require.NoError(t, err, "valid nested recursive payload must be accepted by the generated schema")
+}