graftcode README

The project's README from github.com/grft-dev/graftcode. As one markdown file: README.md.

graftcode

Graftcode

Roadmap Quick Start Stars

WeAreDevelopers 2026 — Berlin

We are at WeAreDevelopers World Congress 2026 in Berlin. If our session or product caught your interest, star this repo — it helps us a lot.

Conference demo repositories:

Call remote code like local dependencies.

Graftcode is the integration-layer-free development framework that lets you call methods across any language and runtime as if they were local, without writing integration code, SDKs, or client layers.

Supported Languages
.NET Java Python Node.js Go PHP C++ Ruby

Platforms & OS
Windows Linux macOS Android

Cloud Ready
Azure AWS GCP Docker

Call remote code like local dependencies. Let package managers keep them fresh.

Graftcode is the integration-free development layer that lets you call methods across languages and runtimes as native dependencies: no integration layer code, no SDKs, no client code.

Turn your public methods into instantly consumable, strongly-typed clients in any technology using regular package managers.

Access your remote services from web, mobile, and edge clients. Seamlessly connect microservices and expose business logic the way it was always meant to be clean, type-safe, and effortless.

Imagine a world where you can share business logic across any technology as easily as publishing a package to a public repository. With Graftcode, you simply write public methods, communicate errors through exceptions, and call them like local code.

Graftcode removes the need to hand-write REST, gRPC, or Thrift integration layers, or to couple your code to message buses and event systems. It reduces your codebase by up to 50%, dramatically improves AI-assisted development (lower token usage, higher efficiency, and simpler code reviews), and makes every backend immediately MCP-compatible for AI agents.

It also enables true modular monoliths you can decompose and recombine modules at will, switch communication channels (WebSocket, HTTP/2, RabbitMQ, Kafka, Service Bus, SQS, Pub/Sub, etc.) without changing a single line of code, and build truly polyglot systems with zero integration overhead.

What is Graftcode?

Instead of building and maintaining APIs, DTOs, clients, and integration layers, Graftcode lets you:

No controllers. No OpenAPI. No client code. No IDL.

Graftcode works with monoliths, microservices, and everything in between — and comes with built-in MCP support for AI agents.

Quick Start

1. Host your service

# 1. Build/package your library
# 2. Navigate to the output folder
# 3. Download Graftcode Gateway

# Windows
iwr https://grft.dev/get | iex

# Linux / macOS
curl -fsSL https://grft.dev/get | sh

# Run the Gateway with your module:
# Example with .NET
gg --modules ./MyService.dll

2. Consume it from anywhere

Install a Graft using your package manager (example for npm):

npm install --registry https://grft.dev/YOUR_PROJECT_ID @graft/your-service-name

Graft installed command can be obtained by navigating to your service hosted on Graftcode Gateway i.e. http://localhost if executed locally.

3. Call it like local code

Once you install Graft in client project of your choice, just import classes replicating your remote API and call the methods as if they where available as local module.

import { EnergyPriceCalculator } from '@graft/...';

const price = await EnergyPriceCalculator.GetPrice();

Whenever API evolves, graftcode will take care to inform your package manager that new version of dependency is available.

Interactive Quick-Start Journey

The best way to get started with Graftcode is our hands-on tutorial series.

→ Open Quick Start Guide

It contains step-by-step tutorials such as:

Core Repositories

Repository Purpose
graftcode-gateway Core multi-runtime host (the engine)
graftcode-demos Live demos + performance comparisons
graftcode-quick-start-guide Hands-on tutorials
graftcode-documentation Full documentation
graftcode-docker-images Official Docker images
graftcode-plugins Official Open Source plugins for any communication channel (ServiceBus, RabbitMQ, Kafka etc..)

Key Features

Exposing your methods for AI Agents (MCP)

Graftcode has native support for Model Context Protocol (MCP). Any public static methods with value type arguments and results become callable as MCP tools. Run your module on Graftcode Gateway, enter the service address and copy MCP configuration from Graftcode Vision portal exposed by Graftcode Gateway.

Ready to use AI Agent rules

Adding graftcode rules to your repository allows you to build entire monolith or distributed systems based on graftcode using pure prompts — the AI agent reads the rules and can easily build new systems in greenfield project, migrate existing solutions to graftcode, and evolve your solution with significantly higher context efficiency and lower token usage.

Use command below in your project root directly to download rules for any IDE Agent.

# PowerShell
iwr grft.dev/get | iex

# Linux / macOS
curl -fsSL grft.dev/get | sh

# Alternative with wget
wget -qO- grft.dev/get | sh

AI Agent Rules Raw Files

If you want to access the raw files of our ready-to-use rules and instructions for AI coding agents that are getting installed when you call abovementioned one-liner command, check the folder below:

→ /rules

These files help AI agents (Cursor, Claude, etc.) understand and effectively use Graftcode when generating or refactoring code.

Used by

Graftcode is already trusted by innovative teams at:

Total TRUMPF Siemens IQVIA Breas

(and many more engineering teams building the future of software)

⭐ Star us if you like the project

If Graftcode helps you ship faster and cleaner or just inspire you with its bold vision — please star the repository.
It really helps the project grow and motivates the team.

Star

Contributing

We welcome contributions! Please read our Contributing Guide and feel free to open issues or PRs.

Made with ❤️ for developers who want to focus on business logic instead of integration layers.

Join the Community

Join other Grafters building the future of software integration.

Join Discord

Chat with the team, get help, share ideas, and stay up to date with the latest developments.

graftcode (grft-dev/graftcode)

integration
Searching Database…

927 ·GitHub
Graftcode
What is this?Graftcode is an integration-free development layer: you call methods across any language and runtime on remote services as if they were local dependencies — no hand-written REST/gRPC layers, SDKs, or client code.
Is it a framework I run myself, or a hosted cloud service?It is a framework, not a hosted service. You run your public methods on the Graftcode Gateway — a multi-runtime host you deploy yourself — and other projects consume them through auto-generated typed clients.
How do I get it running end to end?Host your service on the Graftcode Gateway, install the auto-generated strongly-typed Graft in any client project via your regular package manager (npm, dotnet, pip and more), then import its classes and call methods like local code. A hands-on Quick Start Guide walks through each step.
Which languages and package managers does it work with?It works with 20+ languages and 10+ package managers — README examples include npm, dotnet, and pip — so service and client sides can each be in a different stack without integration glue.
Does every method automatically become available to AI agents?No — only public static methods with value type arguments and results become callable as MCP tools. More broadly, every call goes through the Gateway, which you have to host and keep running yourself.
Where does the Gateway run, and what can consume my services?The Gateway runs on cloud instances, bare metal, containers (official Docker images are published), or your local machine. Clients range from web and mobile to edge.
What exactly is a Graft?The auto-generated, strongly-typed client package Graftcode produces from your service. You install it in a consuming project with a regular package manager (npm, dotnet, pip, etc.), import the classes, and call them as if the remote API were a local module.
What performance gains does it claim over REST and gRPC?Up to 70% faster calls with significantly lower CPU usage than REST/gRPC, up to 50% reduction in codebase volume, and 30-70% lower token cost for AI-assisted changes. Live demos with performance comparisons live in the graftcode-demos repository.
Can I switch between monolith and microservices without rewriting code?Yes — Graftcode advertises monolith-to-microservices switching with zero code changes, and communication channels (WebSocket, HTTP/2, RabbitMQ, Kafka, Service Bus, SQS, Pub/Sub and others) can be swapped via official plugins without changing a single line.
How does it help when building with AI coding agents?Beyond native MCP support, Graftcode ships ready-to-use agent rules (Cursor, Claude, etc.) installed with a one-liner command in your project root. Agents read the rules and can build new Graftcode systems or migrate existing ones, with claimed 30-70% lower token usage.
What are similar projects?go-zero, encore, kratos, JeecgBoot, morloc, brpc, open-im-server, gin-vue-admin
Which topics is it in?polyglot, developer-experience, integration, gateway, rpc, powershell, devtools, code-generation, package-manager, microservices, distributed-systems, backend
Creator
grft-dev
Size
0.4 MB
Stars
927
Updated
CommitSep 24
Age
3mo
Commits · 90 Days