MCP
Connect external MCP servers to extend your agent with third-party tools and data.
Location: Workspace Settings → MCP Servers
MCP (Model Context Protocol) is an open standard for connecting AI assistants to external tools and data. Jean2 can connect to any MCP server, giving your agent access to APIs, databases, and services from the community. Configuration is per-workspace.
Configuration
MCP servers are configured in .jean2/mcp.json inside your workspace directory. Create the file if it doesn't exist.
{
"servers": {
"vaadin": {
"type": "remote",
"enabled": true,
"url": "https://mcp.vaadin.com/docs"
}
}
}
Each server has a unique name (the key under servers). Set enabled to false to disable a server without removing its config.
Local servers (stdio)
local spawns a child process on the server.
| Field | Required | Description |
|---|---|---|
command | Yes | Array of command + args, e.g. ["npx", "-y", "@some/mcp-server"] |
env | No | Environment variables for the process |
timeout | No | Timeout in milliseconds |
enabled | No | Default true |
Remote servers (HTTP)
remote connects over HTTP.
| Field | Required | Description |
|---|---|---|
url | Yes | The server URL |
headers | No | Custom headers |
oauth | No | OAuth configuration |
timeout | No | Timeout in milliseconds |
enabled | No | Default true |
Connect
Open Workspace Settings → MCP Servers. You'll see all configured servers with their status badges:
| Status | Meaning |
|---|---|
| Connected | Server is live and its tools are available |
| Disabled | Config exists but enabled is false |
| Failed | Connection attempt failed. Check the URL or command |
| Needs Auth | OAuth required. Click to start the auth flow |
| Needs Registration | Server requires client registration first |
Click Connect to establish a connection. Jean2 validates it on the spot. Click Disconnect to drop a connection without removing the config.
OAuth
Some remote MCP servers require OAuth. When you click Connect on a server that needs auth, Jean2 starts the OAuth flow. A browser tab opens for you to log in and approve. The token is stored server-side.
If the server needs client registration first, Jean2 handles that automatically. You'll see a Needs Registration badge until it completes.
How it works
Once connected, the server's tools appear alongside your built-in tools. The agent sees them in the tool list and can call them like any other tool. MCP servers run as child processes of Jean2. They start and stop with the server.
What's next
- Workspace Settings: other workspace config options
- Preconfigs: control which tools (including MCP) each agent can use