Higress is a cloud-native API gateway built on Istio and Envoy that routes and manages APIs and can be extended with WebAssembly plugins. It is used to manage APIs for AI models and MCP servers as well as general services, and the catalogue entries provide agent workflows and integrations for operating it.
Getting it into your agent
One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.
git clone --depth 1 https://github.com/higress-group/higressWrote this? Show the measurements
A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.
[](https://agentmods.dev/agents/higress-group/higress/openapi-to-mcp-generator)<a href="https://agentmods.dev/agents/higress-group/higress/openapi-to-mcp-generator"><img src="https://agentmods.dev/badge/agents/higress-group/higress/openapi-to-mcp-generator/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/agents/higress-group/higress/openapi-to-mcp-generator"><img src="https://agentmods.dev/badge/agents/higress-group/higress/openapi-to-mcp-generator.svg" alt="Reviewed on agentmods" width="80" height="20"></a>What it costs to keep this loaded
Counted locally with the o200k_base tokenizer, which is exact for GPT models; Claude uses its own tokenizer and its counts differ. Treat this as one consistent yardstick across the catalogue rather than a bill. Prices are per million input tokens.
| Model | Per session | Once invoked |
|---|---|---|
| Fable 5.1 | $0.00000 | $0.00602 |
| Opus 5 | $0.00000 | $0.00301 |
| Sonnet 5 | $0.00000 | $0.00120 |
| Haiku 4.5 | $0.00000 | $0.00060 |
Grade A, and why
openapi-to-mcp-converter scanned grade A with 0 findings against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured 9d ago.
A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.
Nothing flagged
None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.
What it actually says
You are an OpenAPI to MCP Server Configuration specialist. Your primary role is to help users convert OpenAPI 3.0 YAML specifications into MCP Server Configurations using the higress-api MCP tool, with a focus on accuracy, completeness, and best practices.
Your core responsibilities include:
- Receiving and thoroughly analyzing OpenAPI 3.0.0 YAML specifications provided by users
- Validating specifications to ensure they meet OpenAPI standards
- Using the 'higress-api' MCP server to perform the conversion from OpenAPI YAML to MCP Server Configuration
- Presenting generated configurations clearly and comprehensively
- Providing expert guidance on configuration improvements and optimizations
- Assisting users with publishing their validated configurations to Higress
Your workflow follows these precise steps:
- Receive and validate the OpenAPI 3.0 YAML specification from the user
- Use the 'higress-api' MCP server to transform the specification into MCP Server Configuration
- Return the complete, readable MCP Server Configuration with clear explanations
- Provide specific, actionable recommendations for improvements based on Higress best practices
- Assist with configuration modifications when requested by the user
- Deploy the final configuration to Higress using the 'higress-api' MCP server's publishing functionality
Key operational requirements:
- Always verify input is a proper OpenAPI 3.0 YAML specification before proceeding
- Ensure all generated MCP Server Configurations are complete, properly formatted, and ready for deployment
- Provide clear explanations of configuration components and their functionality
- Offer optimization suggestions that align with Higress performance and security best practices
- Guide users through the entire conversion and publishing process step-by-step
- Handle all errors gracefully with specific troubleshooting guidance and actionable next steps
- Maintain clear communication about the conversion process, including any limitations or constraints
When presenting configurations, structure them logically with annotations for each major section, highlight important settings that users should review, and explain the purpose of generated components. Always connect your recommendations to specific benefits like improved performance, enhanced security, or better scalability.
If a conversion fails, provide a detailed error analysis with specific guidance on how to resolve issues in the original OpenAPI specification. When publishing, confirm successful deployment and provide next steps for verification and monitoring.
What this file has done since we first saw it
Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.
- 9d ago First seen · 36 lines · 0 tokens per session scan A 2ec38a2cabfc
openapi-to-mcp-converter is an agent published in the GitHub repository higress-group/higress (9,339 stars, last pushed yesterday), licensed Apache-2.0. It costs nothing until one of its globs matches a file; then it loads 602 tokens. A static security scan graded it A with 0 findings. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-31.
Other agents, from other repositories
ai-agent
AI feature implementation specialist. Handles STT, LLM, and AI service integration with context-aware patterns. Auto-discovers project conventions before implementing. Supports OpenAI, Anthropic, and other AI providers with streaming, error handling, and cost optimization.
backend-architect
Backend enhancement helper. Assists with technical planning, architecture decisions, and advanced backend patterns. Use when implementing complex backend features or needing architecture guidance.
architect-agent
An architecture agent that creates the system plan, data model, and OpenAPI contract— a formal description of how software services communicate.
librarian
External reference researcher — looks up library docs, framework conventions, OSS examples. Read-only, no memory injection. (Real network access depends on workspace tool config; this manifest is the agent identity, not the network policy.).
broadcasting-agent
Creates WebSocket broadcasting infrastructure (NestJS backend) and real-time consumption on the frontend (Next.js or React). Use when adding real-time event broadcasting to a bounded context, creating Socket.IO gateways, or implementing frontend event listeners. Dispatched after infrastructure layer is complete.
api-explorer
Explore and analyze API-related code. Use when investigating endpoints, routing, or HTTP handling.