Channels
agent-kit is one project published through four channels. Each one points to the others, so you — or your agent — can start from any of them.
| Channel | Where | What it is for |
|---|---|---|
| Documentation | https://razcue.github.io/agent-kit/ | Everything, in English and Spanish: installation, concepts, guides, reference. Also llms.txt and llms-full.txt for agents. |
| Docs for agents (MCP) | https://razcue-agent-kit.vercel.app/mcp | The same documentation as an MCP server: list-pages and get-page. |
| Claude Code plugin | /plugin install agent-kit --marketplace razcue/agent-kit | Skills, hooks, the reviewer agent and the scripts, from this repository's marketplace. Soon also in Anthropic's directory on claude.ai. |
| npm CLI | npx @razcue/agent-kit init my-project | Asks the setup questions and writes the project; upgrade, doctor, uninstall and the other commands. |
How they fit together
The CLI sets a project up
npx @razcue/agent-kit init writes agent-kit.json, the managed block in AGENTS.md, and .claude/settings.json, which declares the marketplace and turns the plugin on. Its help and its final output name the documentation and the MCP server.
Claude Code installs the plugin
Open Claude Code in the project and accept the plugin. To install it in another project by hand:
/plugin install agent-kit --marketplace razcue/agent-kit
The plugin uses the CLI and the docs
The plugin's skills call the CLI pinned to the plugin's own version (for example npx @razcue/agent-kit@0.14.1 upgrade), and the plugin declares the docs MCP server as agent-kit-docs, so Claude can look up a page while it works.
The docs describe all of them
This site documents every channel, and its reference pages are generated from the CLI and the plugin, so they can't drift.
Use the MCP server without the plugin
claude mcp add --transport http agent-kit-docs https://razcue-agent-kit.vercel.app/mcp
Any MCP client that speaks streamable HTTP works the same way. See Docs for agents.