# Why reShapr?

> For AI agents: the complete documentation index is available at https://reshapr.io/llms.txt and the full documentation bundle at https://reshapr.io/llms-full.txt.

> Hey hey… wondering why we built reShapr? 🤔

# Why reShapr?

Hey hey… wondering why we built reShapr? 🤔

:::info
Check out our 👉 [**blog post**](/blog/why-reshapr) on that topic!
:::

***Building Your Own MCP Server Is a Trap!***

*At first glance, building an MCP Server may seem straightforward. But very quickly, most teams realize:*

- **It’s more than OpenAPI**: You need translation layers, prompt guards, retries, rate limiting, and grounding logic.
- **Security gets messy fast**: How do you avoid exposing credentials in LLM prompts? How do you enforce identity, scope, and input validation?
- **Fragility creeps in**: Most DIY solutions end up as brittle pipelines of JSON transforms, hardcoded logic, and embedded hacks that fall apart under load or, worse, leak data.

This approach often duplicates your API logic into a parallel, standalone MCP layer, creating unnecessary complexity, increased maintenance overhead, and misalignment between your API and its AI-facing interface.

> **A smarter approach** is to **extend your existing API** infrastructure, not **reinvent it** !

**reShapr exists to solve this exact problem!**

Rather than building an MCP server from scratch, you can use reShapr to **instantly translate your existing APIs (REST, gRPC, GraphQL) into AI-native endpoints.**

- **Zero** code
- **No** rewrites
- **No** custom Agents
- **No** vendor lock-in