Jacky supports connecting external MCP (Model Context Protocol) servers to extend the LLM's available tools. This allows installing third-party tools — such as database access, external APIs, specialized file systems, etc. — and having Jacky use them natively within its agent loop.
Configuration
From the LLM tab, access the 🔌 MCP Servers sub-tab. From here you can:
- Add server: Create a new MCP server specifying name, transport (stdio / SSE / HTTP streamable), command or URL, and environment variables.
- Add from JSON: Import an existing MCP configuration in JSON format.
- Edit / Remove: Modify or delete existing servers.
- Reconnect all: Force reconnection of all servers.
Each server displays a status icon:
| Icon | Status |
|---|---|
| 🟢 | Connected |
| 🔴 | Error |
| ⚫ | Disabled |
| 🔑 | Missing auth token |
| 🔐 | Missing secret env var |
Supported transports
- stdio: Runs a local command on your machine. Ideal for MCP servers installed as npm/pip packages.
- SSE: Remote connection via Server-Sent Events.
- HTTP streamable: Remote connection via HTTP with streamable transport (the modern MCP standard).
Security
MCP servers can execute arbitrary code on your system. Only add servers you trust. Authentication tokens and environment variables marked as secret are stored in the system keyring, not in configuration files.
Tools from MCP servers are namespaced as mcp_<server_name>_<tool_name> to avoid collisions with Jacky's built-in tools.
Required permission
Using MCP tools requires the allow_mcp_tools permission, which is in the destructive permissions group and is disabled by default. You can enable it from the Permissions tab in settings.
When the permission is active and MCP servers are connected, MCP tools appear automatically in the tool catalog (visible in the 🛠️ Tools sub-tab) and work in both compact and normal mode.