INSIDE Graftcode

Turn your backend into an MCP server without writing MCP server code

Graftcode is coming to WeAreDevelopers as a Bronze Partner, and you can attend our workshops on Day 0 and visit us in Hall A, opposite Stage 11.

With Graftcode Gateway, developers can expose backend methods directly to LLM agents through MCP - without adding a separate MCP layer, wrapper file, decorators, or protocol-specific code.

Run your application with Graftcode Gateway, and it automatically detects your public backend methods and exposes them as tools that agents can call. Your business logic stays clean. Your code does not need to know it is being used by an LLM agent.

One of our users recently wrote about this exact experience: after removing 30 lines of MCP server code, their Claude Desktop agent still worked.

The reason is simple: Graftcode Gateway handles the MCP exposure outside your application code.

We believe this is the right direction for agent-ready software:
less boilerplate, fewer duplicate interfaces, and one clean source of truth - your actual backend code.

Meet us at our booth and see how Graftcode lets LLM agents talk to your code directly.

ABOUT THE COMPANY

Graftcode

Warsaw, Poland

The future of Software Development is quite clear

Seeing Cursor 3 introduce a new agentic workflow really reinforces something we (and IT market) have been thinking about for a while:
Developers are gradually becoming orchestrators.

Not in the sense that they stop building, but in the sense that more of the job becomes guiding, reviewing, connecting, and shaping what agents produce.

And we think that changes a lot about how we should write software.

If developers are going to spend more time reading code generated by agents than writing every line themselves, then readability becomes much more important than before. The code has to be easy to follow, easy to reason about, and easy to verify.

Honestly, the same is true for AI. The clearer the codebase is, the easier it is for agents to work inside it without creating unnecessary mess.

That’s also one of the reasons we’re building Graftcode the way we are.

We want code to stay focused on business logic, not get buried under all the complexity of how services talk to each other. When that communication layer is less intrusive, the result is simply easier to understand - both for developers and for AI.

We think this will matter more and more over time.

The future is probably not just developers writing code.
It’s developers directing systems of agents.
And in that world, clear code is a huge advantage.

Check out link in the comment, and see how Graftcode can help you and AI focus on the business logic.