Plugins

A plugin bundles reusable capability — skills and MCP servers — into a single installable package. Where a lone skill is one Markdown file and a lone MCP server is one mcp.json entry, a plugin lets you ship both together, version them, and distribute them from a local path, a ZIP URL, or a GitHub repository.

Managing plugins

Plugins are managed from inside the TUI with the /plugins slash command. Run /plugins with no arguments to open the interactive picker, or use a subcommand directly:

Command	What it does
`/plugins list`	List installed plugins.
`/plugins install <source>`	Install from a local path or ZIP URL.
`/plugins info <id>`	Show details for a plugin.
`/plugins enable <id>` / `/plugins disable <id>`	Toggle a plugin without removing it.
`/plugins mcp enable\|disable <id> <server>`	Toggle a single MCP server provided by a plugin.
`/plugins remove <id>`	Uninstall a plugin (leaves the files in place).
`/plugins reload`	Re-scan installed plugins.
`/plugins marketplace`	Browse the plugin marketplace.

Install sources

/plugins install ./my-plugin                  # local directory
/plugins install https://example.com/p.zip    # ZIP URL
/plugins install https://github.com/org/repo  # GitHub repository

Installed plugins live under ~/.geoff and are referenced by their id (the lowercased plugin name).

Plugins load at session start. After installing, enabling, or toggling a plugin’s MCP server, run /new or restart geoff for the change to take effect.

Plugin structure

A plugin is a directory containing a manifest. Geoff Code recognizes two layouts:

Root manifest — a geoff.plugin.json at the directory root.
Dir manifest — a .geoff-plugin/plugin.json inside the directory.

my-plugin/
├── geoff.plugin.json      # the manifest
├── skills/                # skills shipped by the plugin
│   └── my-skill/
│       └── SKILL.md
└── ...

The manifest

geoff.plugin.json declares metadata plus the capabilities the plugin provides:

{
  "name": "my-plugin",
  "version": "1.0.0",
  "description": "Internal tooling for the platform team.",
  "author": { "name": "Platform Team", "email": "platform@example.com" },
  "homepage": "https://github.com/geoff-ai/my-plugin",
  "license": "MIT",
  "skills": ["skills/my-skill"],
  "mcpServers": {
    "internal-api": {
      "url": "https://mcp.internal.example.com/mcp",
      "bearerTokenEnvVar": "INTERNAL_MCP_TOKEN"
    }
  }
}

Key fields:

Field	Description
`name`	Required. Lowercase letters, numbers, `-`, `_` (1–64 chars).
`version`, `description`, `keywords`, `homepage`, `license`, `author`	Optional metadata.
`skills`	A path (or array of paths) to skill directories shipped by the plugin. If a `SKILL.md` sits at the plugin root, it is used automatically.
`mcpServers`	A map of MCP server entries, using the same shape as `mcp.json`.
`sessionStart`	A skill to activate automatically when a session starts.
`interface`	Display metadata (name, descriptions) for marketplace/listings.

The MCP entries follow the same schema as standalone MCP servers — see MCP for the stdio and HTTP field reference. Each server can be toggled per-plugin with /plugins mcp enable|disable.

Skills

The knowledge files plugins package and ship.

MCP

The server format plugins reuse for tools.

Getting Started

Extending

Reference

Managing plugins

Install sources

Plugin structure

The manifest

Skills

MCP

​Managing plugins

​Install sources

​Plugin structure

​The manifest

​Related

Skills

MCP

Managing plugins

Install sources

Plugin structure

The manifest

Related