MCP Servers
Jan supports the Model Context Protocol (opens in a new tab), letting you connect any MCP-compatible server to extend what your AI can do — web search, browser control, code execution, databases, and more.
Settings
- Allow All MCP Tool Permissions — When enabled, all MCP tool calls are automatically approved without showing permission dialogs. Applies globally to all conversations.
- Tool call timeout — Maximum time (in seconds) to wait for an MCP tool response before timing out. Default is 30 seconds.
- Smart MCP tool routing — When enabled, Jan narrows which MCP servers are queried for tools on each turn when you have more than a small number of connected servers, reducing context size. You can optionally use a dedicated lightweight model for that routing step.
- Routing model — Single picker for provider + model; only lightweight models are listed. Requires smart routing and “Use a dedicated model for routing” to be on.
For developers tuning routing behavior (latency, fallbacks, token usage), see MCP routing.
Add an MCP Server
Open Settings
Go to Settings → MCP Servers.
Add server
Click + Add MCP Server in the top right corner.
Configure
Enter the server details:
- Transport:
STDIO(local process),HTTP(Streamable HTTP), orSSE(Server-Sent Events) - Command / URL: the command to run or the server endpoint
- Args: any arguments to pass
- Env: environment variables (e.g. API keys)
Enable
Toggle the server on. It will appear in the list with a green indicator when active.
Find more MCP servers at mcp.so (opens in a new tab).