Browse a registry of pre-built agents. Install one with a single command. It lands in your instance, uses your connections, and its commands become MCP tools.
An agent is a folder. The entry point is index.md, a markdown file with YAML frontmatter that declares id, name, description, parameters, connections, and tags.
The commands/ subfolder holds slash commands. Each command is a markdown file exposed as an MCP tool. Optional subfolders: scripts/ for executable code, data/ for configuration and state, steps/ for multi-step workflows.
The registry lists all available agents. Browse them on the web at gcontext.ai/agents/browse or search from your MCP client. Each listing shows the name, description, required connections, and tags.
Pick an agent that matches what you need. The listing tells you which capabilities it requires before you install it.
Run gcontext add with the agent ID from your instance directory. The command pulls the agent folder from the registry and copies it into agents/browser-cookbook/.
The agent is now part of your instance. You can read its files, edit its configuration, and inspect its commands before you run anything.
The agent folder contains the entry point, commands, and data. When you install an agent, the folder lands inside your instance's agents/ directory.
The agent runs with your connections and modules. It does not bring its own runtime or dependencies beyond what its connections declare.
Agents declare abstract capabilities, not specific services. The browser-cookbook agent needs a "browser" connection. It does not specify which browser tool you use.
During /setup, gcontext reads the agent's frontmatter, finds the capabilities it needs, then looks in your connections/ folder. Two users can install the same agent and bind it to different connections. The agent code stays the same.
The agent's commands become MCP tools. Your client calls them directly. The tool name follows a predictable pattern.
Each command runs in the context of your instance. It has access to the agent's data, your connections, and your modules.
The agent tool checks for updates from the registry. When a new version is available, it pulls the latest files into your local copy.
To remove an agent, delete the agents/name/folder. The agent's commands disappear from your MCP tools on the next server restart. Your connections and modules stay untouched.
See all available agents at /agents/browse.
The registry at github.com/bleak-ai/agents. Anyone can publish an agent by adding a folder with an index.md that follows the required frontmatter schema. The gcontext add command pulls from this repository.
Yes. Create a folder with index.md and commands/ inside your instance. The agent works locally right away. To publish it, add the folder to the registry repo and open a pull request.
No. Agents run inside your instance. They use your local connections and state. Nothing leaves your machine unless a connection you configured sends it.
Browse the registry. Pick an agent. Run gcontext add.