Plugins (MCP)

Any MCP server is a jigbee plugin: your issue tracker, your calendar, a database, a home-automation bridge. Add it by its command line; jigbee starts it the first time a job needs it.

Adding one

Settings → Plugins → paste the command (for example npx -y @modelcontextprotocol/server-github) and a name. Environment values (tokens) go in the manifest at ~/Library/Application Support/jigbee/plugins.json; the app shows only their names afterwards and never sends them back to the page.

How the model sees it

One line per tool in the job prompt, nothing more. When the model picks a tool it fetches the schema on demand (plugin_describe), then calls it (plugin_call). That keeps a plugin with forty tools from costing forty schemas on every step.

The gate

Tools whose names say they change something (create, send, delete, pay, publish, deploy, run … in any case style) stop and ask you first, like everything irreversible in jigbee. Add your own patterns under irreversible in the manifest (* gates every tool of that plugin).

Limits

• Stdio servers only for now; HTTP and OAuth transports are on the list.
• A server that stops answering for two minutes is dropped and restarted on the next call.
• Servers never see your model keys or the Chrome pairing code.