feat: mcp options

[Totorro35]

• Add option to enable transport config on MCP
• Use client name instead hand-crafted
• Add missing required args on server tool declaration
• Add missing import for custom mutator

Fix #2594

[Copilot]

Pull request overview

This PR adds MCP transport configuration options and fixes several issues in MCP-related code generation. The changes enable configuration of MCP transport (stdio vs http), properly handle custom mutators, use generated schema names instead of hand-crafted ones, and ensure all server tool declarations include required parameters.

Key Changes:

• Add MCP transport configuration option (stdio/http) in type definitions and normalization
• Fix server tool declarations to include required empty object parameter for tools without input schemas
• Add missing RequestInit options parameter to all handler types and implementations
• Fix custom mutator imports in http-client file generation

Reviewed changes

Copilot reviewed 5 out of 5 changed files in this pull request and generated 2 comments.

Show a summary per file

File	Description
packages/core/src/types.ts	Adds MCP options types with transport configuration
packages/orval/src/utils/options.ts	Normalizes MCP options with default stdio transport
packages/mcp/src/index.ts	Uses generated schema names, adds options parameter, conditionally generates server connect code based on transport, and adds mutator import handling
samples/mcp/petstore/src/server.ts	Adds required empty object parameter to tool declarations
samples/mcp/petstore/src/handlers.ts	Adds options parameter to all handler types and function calls

---

💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.

[Copilot]

The options parameter should be added conditionally only when handlerArgsTypes has other parameters. When there are no other parameters (e.g., for getInventory), the handler will have args as a parameter with only options, but the function call will always pass args.options, which could be undefined if no args are provided.

[Copilot]

This unconditionally pushes args.options to fetchParams, but when handlerArgsTypes is empty (no parameters), the handler function signature won't accept args, causing a mismatch between the handler signature and the fetch call parameters.

[soartec-lab]

@Totorro35

Thanks! could you also write the doc ?

https://github.com/orval-labs/orval/blob/master/docs/src/pages/reference/configuration/output.mdx

and ad test case

https://github.com/orval-labs/orval/blob/master/tests/configs/mcp.config.ts