Graftcode CLI

CLI installs Graftcode Gateway and coding-agent rules so methods of your own service can be exposed as MCP tools

  • 1,089 ★ on the repository
  • Last commit
CLI

Extended access

Why this level

  • The CLI downloads executables and can update its scripts before a command.
  • Rules can replace project files; exposed methods of your Gateway use permissions granted to that service.
All reasons and checks

grft-dev/graftcode

Install

Manual install

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

The README’s first user installer installs grft. Inspect the script and PATH changes first; we did not run commands. Start the Gateway separately with your own module.

Access and checks

How we review

Extended accessThe tool runs code or makes network calls and only reads external data.

  • The CLI downloads executables and can update its scripts before a command.
  • Rules can replace project files; exposed methods of your Gateway use permissions granted to that service.

This is third-party code. Review the repository files before installing.

What it does

Graftcode CLI prepares the Gateway and service-development instructions. `grft get gg` downloads a Gateway executable into the current directory. The same CLI installs rules for Claude Code, Cursor and other supported editors. The Gateway loads a module containing the user's business logic. Eligible public static methods become MCP tools when argument and result types are supported. The running service's portal provides client configuration. Your applications can call the same methods through generated client packages. The CLI prepares components; the service owner writes business logic and sets network permissions.

Who it is for. For developers exposing their own service methods to agents and installing Graftcode development rules.

Good fit when

  • Expose suitable methods from your own service as MCP tools
  • Download the platform-matched Gateway without selecting release assets manually
  • Add Graftcode instructions for a particular editor to a repository
  • Prepare a transport plugin such as RabbitMQ for your deployment

Not a fit when

  • You need ready-made tools for another service without a module of your own
  • Your methods do not fit the MCP publication type restrictions
  • Your project prohibits installers from replacing rule files or updating their own scripts automatically

Example request

Check whether my module fits Graftcode MCP. Show exposed methods and parameters first. Do not replace project rules; propose a separate Gateway test directory.

Limitations

Before connecting an agent, inspect the chosen methods of your Gateway and their permissions; exposed functions can change service data. Rule installation modifies the project; the Claude option can replace CLAUDE.md and .claude/rules/, so preserve custom edits first. The CLI checks its version and may update scripts before executing a command. The repository specifies no license; ask the author about use and copying rights, and inspect Gateway and package terms separately.

How to disable. `grft uninstall` removes the CLI from `~/.grft` and its PATH entry. Downloaded Gateway files, modules and project rules remain; stop processes and review them separately. Compare rules with your backup before removing them.

FAQ

How do I install the persistent CLI on macOS or Linux?

`curl -fsSL https://raw.githubusercontent.com/grft-dev/graftcode/refs/heads/main/cli/install.sh | sh` runs the installer. Read it first. It installs into the user's home directory and adds the command to PATH.

How do I download the Gateway?

Run `grft get gg` in a separate directory. It downloads the platform-matched executable there. Hosting business logic then requires starting the Gateway with your module.

How do I install Cursor rules?

Run `grft get rules cursor` from the intended project root. Other editors have their own selectors. Inspect and back up existing rules before writing.

Where do exact MCP settings come from?

Open Graftcode Vision on your running Gateway and copy its MCP configuration. The address and method list depend on your deployment and module. The project provides no universal hosted server with ready-made tools.

What does `grft` do without arguments?

It opens the component installation menu, as does `grft get`. `grft version` displays the installed version.

Discussion

No questions or reviews yet.

CLI tools

Kode CLI is a terminal coding agent that reads AGENTS.md and CLAUDE.md, connects MCP servers and works with many models.

CLIBroad access5.2KRepository stars

AI Code Toolkit

aicode-toolkit

Plugins and MCP servers for coding agents: template-based projects, patterns before a file edit and review against YAML rules.

PluginExtended access160Repository stars

An MCP server that lets an agent read files, search code and run commands in a workspace

MCP serverBroad access1.2KRepository stars

clihub turns any MCP server into a ready CLI: each tool becomes a subcommand and the result is one static binary with no runtime dependencies

CLIBroad access668Repository stars
Official

Official GitKraken MCP server from the gk CLI: git, pull requests and issues across GitHub, GitLab, Bitbucket and Jira

MCP serverBroad access465Repository stars

An MCP server that builds a code graph of functions, classes, calls and routes and answers the agent's structural queries locally

MCP serverExtended access48.5KRepository stars

README in short

The CLI also downloads RabbitMQ and Service Bus plugins. Applications can obtain typed client packages through their ecosystem’s package manager.

README badge

Report a problem