You are working on the hyperswitch repository (Rust payment processing system).…
- User
You are working on the hyperswitch repository (Rust payment processing system).
REPOSITORY SETUP:
- Repository: juspay/hyperswitch
- Working directory: ./repos/hyperswitch_pool_6 (already cloned)
- Base commit: bc767b9131e2637ce90997da9018085d2dadb80b
- Task ID: juspay__hyperswitch-8442
- Version: v1.114.0
TASK DESCRIPTION: Bug: [FEATURE] Add x-mcp extension to OpenAPI schema
Mintlify supports extracting API endpoints from openAPI json into MCP servers: https://mintlify.com/docs/mcp
We need to add:
"x-mcp": { "enabled": true },at the top level of our OpenAPI schema to enable this functionality
DETAILED CONTEXT & HINTS:
Type of Change
- Bugfix
- New feature
- Enhancement
- Refactoring
- Dependency updates
- Documentation
- CI/CD
Description
Modified
openapi/src/main.rsto appendx-mcpextension to v1 OpenAPI schemaAdditional Changes
- This PR modifies the API contract
- This PR modifies the database schema
- This PR modifies application configuration/environment variables
Motivation and Context
Closes #8442
How did you test it?
Verified using:
mintlify openapi-check api-reference/v1/openapi_spec_v1.jsonTested mintlify's mcp server generation functionality by deploying the updated OpenAPI spec file on a custom mintlify account. Used the generated mcp server to do payments - create in cursor.
[image: image] open
Checklist
- I formatted the code
cargo +nightly fmt --all - I addressed lints thrown by
cargo clippy - I reviewed the submitted code
- I added unit tests for my changes where possible
CRITICAL INSTRUCTIONS - WORK FAST AND EFFICIENTLY:
-
Create DENSE, ACTION-FOCUSED todos IMMEDIATELY
- Make todos specific and actionable
- Focus on HIGH-IMPACT actions only
- 5-8 todos maximum - be surgical, not exhaustive
-
Execute aggressively:
- Use bash commands to search efficiently
- Read multiple related files in quick succession
- Make ALL related changes in one edit
- Skip unnecessary exploration
-
File operations:
- All repo files: './repos/hyperswitch_pool_6/'
- Use targeted edits over whole file rewrites
-
NO TESTING UNLESS CRITICAL:
- Focus on making the actual code changes
- Only test if explicitly required
-
Maximize information density:
- Each turn should accomplish significant work
- Batch file reads when examining related code
- Use search commands to locate code quickly
EFFICIENCY IS CRITICAL. Make substantial progress every turn.
Assistant
I'll work on adding the x-mcp extension to the OpenAPI schema as requested. Let me start by understanding the current OpenAPI setup and locating the relevant files.
First, I'll examine the OpenAPI schema files to understand the current structure:
Assistant
Let me examine the main OpenAPI file mentioned in the task description:
Assistant
Now let me look at the openapi.rs file to understand how the OpenAPI specification is defined:
Assistant
Let me also check if there's an existing openapi_v2.rs file to understand the structure:
Assistant
Let me create a clear action plan to address the task of adding the x-mcp extension to the OpenAPI schema:
Assistant
Let me look at the OpenAPI structure more closely. Based on the code, I can see that both v1 and v2 versions use the utoipa crate to generate OpenAPI specs. The extensions need to be added to the top-level OpenAPI specification. Looking at the
main.rsfile, I can see it generates the OpenAPI specs usingopenapi.to_pretty_json().I need to examine how utoipa handles custom extensions. Let me check the documentation approach and understand where to inject the x-mcp extension. Based on the requirement, I need to add this at the top level of the OpenAPI schema:
"x-mcp": { "enabled": true }Looking at the utoipa documentation, I can see that
utoipa::Modifytrait allows modification of the generated OpenAPI specification. Let me add the x-mcp extension to both v1 and v2 OpenAPI specifications:Assistant
Let me first create a plan for the implementation and then make the necessary changes. I need to modify both the v1 and v2 OpenAPI specification definitions to add the x-mcp extension.
Assistant
Now I'll modify the v1 OpenAPI specification to add the x-mcp extension. Looking at the structure, I need to use the
utoipa::Modifytrait to add the extension to the generated OpenAPI specification.Assistant
Let me first read the current structure of the v1 OpenAPI spec file again and then make the proper edits:
Assistant
Let me now modify the v1 OpenAPI specification to add the x-mcp extension. I'll need to add a new modifier to the OpenAPI spec that adds the x-mcp extension at the top level:
Assistant
I'll modify the file using the proper tool syntax. Let me make the change to add the x-mcp extension to the v1 OpenAPI specification:
Assistant
I need to actually edit the file using the right parameters. Let me do this step by step. First, I'll create a helper function to add the x-mcp extension to the OpenAPI specification.
Let me approach this differently by first looking at what imports are needed and then modifying the file properly:
Assistant
Let me create the correct Edit operation to add the x-mcp extension to the OpenAPI specification:
Other models, same or similar prompt
Responses were produced in different, uncontrolled contexts (system prompts, settings, prior turns). This is not a benchmark.
Identical first prompt
claude-sonnet-4-5-20250929Compare side by side →
claude-sonnet-4-5-20250929Compare side by side →
claude-sonnet-4-5-20250929Compare side by side →
claude-sonnet-4-5-20250929Compare side by side →
claude-sonnet-4-5-20250929Compare side by side →
claude-sonnet-4-5-20250929Compare side by side →
claude-sonnet-4-5-20250929Compare side by side →
claude-sonnet-4-5-20250929Compare side by side →
claude-sonnet-4-5-20250929Compare side by side →
claude-sonnet-4-5-20250929Compare side by side →
claude-sonnet-4-5-20250929Compare side by side →