# Quarkus Insights #259: MCP Servers Without the Boilerplate -- Introducing reShapr

DevFeed: [Quarkus Insights #259: MCP Servers Without the Boilerplate -- Introducing reShapr](<https://devfeed.tech/articles/quarkus-insights-259-mcp-servers-without-the-boilerplate-introducing-reshapr-43887.md>)

Original publisher: [Read original article](<https://quarkus.io/blog/quarkus-insights-259-reshapr/>)

Author: James Cobb (https://twitter.com/insectengine)

Published: 2026-09-14T00:00:00Z

Content type: article

Language: en

Sources: [Quarkus - Supersonic Subatomic Java](<https://devfeed.tech/sources/quarkus-supersonic-subatomic-java.md>)

Topics: [MCP](<https://devfeed.tech/topics/mcp.md>), [MCP Server](<https://devfeed.tech/topics/mcp-server.md>), [Model Context Protocol](<https://devfeed.tech/topics/model-context-protocol.md>), [API](<https://devfeed.tech/topics/api.md>), [GraphQL](<https://devfeed.tech/topics/graphql.md>), [OpenAPI Specification](<https://devfeed.tech/topics/openapi.md>), [gRPC](<https://devfeed.tech/topics/grpc.md>), [Quarkus](<https://devfeed.tech/topics/quarkus.md>), [Orchestration](<https://devfeed.tech/topics/orchestration.md>), [Security](<https://devfeed.tech/topics/security.md>), [Large Language Model](<https://devfeed.tech/topics/llm.md>)

Tags: [apis](<https://devfeed.tech/tags/apis.md>), [graphql](<https://devfeed.tech/tags/graphql.md>), [hallucinations](<https://devfeed.tech/tags/hallucinations.md>), [integration](<https://devfeed.tech/tags/integration.md>), [mcp](<https://devfeed.tech/tags/mcp.md>), [mcp-server](<https://devfeed.tech/tags/mcp-server.md>), [news](<https://devfeed.tech/tags/news.md>), [quarkus](<https://devfeed.tech/tags/quarkus.md>), [security](<https://devfeed.tech/tags/security.md>), [time](<https://devfeed.tech/tags/time.md>)

## AI overview

Episode 259 introduces reShapr, a declarative platform approach for turning existing OpenAPI, GraphQL, or gRPC APIs into production-grade MCP servers without rewriting them. It also discusses the engineering, security, and context-management problems caused by proliferating hand-built MCP servers.

## Source excerpt

This summary was generated using AI, reviewed by humans - watch the video for the full story. Quarkus Insights #259: MCP Servers Without the Boilerplate -- Introducing reShapr As the MCP ecosystem matures, a new pain point has emerged: teams are building a sprawling, inconsistent collection of hand-crafted MCP servers -- one per use case, each with its own security model, its own stack, and its own operational burden. Laurent Broudoux, co-founder of the Microcks CNCF incubating project and member of the Open Innovation and AI team at Postman, joins hosts Eric Deandrea and Holly Cummins in episode 259 to introduce reShapr: a declarative, platform-level approach to turning existing APIs into production-grade MCP servers -- without rewriting them. Quarkus News Eric opened with a brief news round: work on Quarkus 4 is actively progressing. The working group board is the best place to follow along. A candidate release for Quarkus 3.40 is expected this week, which is intended to be the last LTS on the 3.x stream. Eric will also be at Developers North America in San Jose, California the following week, demoing testing of non-deterministic things with Langfuse and the Quarkus integration. The MCP Server Problem at Scale Laurent framed the talk with a recurring observation from large enterprise Microcks adopters: MCP servers are proliferating rapidly, but not in a healthy way. Every new use case spawns a new hand-built MCP server, each one consuming engineering time, requiring deep knowledge of a fast-moving protocol (major versions every six months), and inevitably implementing security in a subtly different way from the one built the sprint before. The protocol itself is broad and does not enforce consistent usage, so even experienced engineers can produce servers that flood an LLM with far too many tools and far too much context -- the exact condition that causes hallucinations and failed orchestration. Laurent showed a concrete example: importing the full GitHub GraphQL sche