Model Context Protocol (MCP)
Model Context Protocol (MCP) is an open standard that allows AI models to connect to external tools and data sources. Kognar Chat supports MCP servers, letting you extend what the AI can do without writing custom code.
What is an MCP server?
An MCP server is a program that exposes tools — functions the AI can call during a conversation. When connected, those tools become available to any AI model in Kognar Chat, just like built-in agents.
Examples of what MCP servers can expose:
- Query a database
- Read or write files on your computer
- Call third-party APIs
- Interact with local development tools
Connecting an MCP server
- Click the Power Tools button (sliders icon) in the action bar below the message input
- Go to the MCPs tab
- Click Add Server
- Fill in the configuration:
| Field | Description |
|---|---|
| Name | A friendly label for this server |
| Transport | Local (runs a command on your machine) or Remote (connects to an HTTP URL) |
| Command / URL | For Local: the command to start the server (e.g. npx my-mcp-server). For Remote: the server URL |
| Environment variables | Optional key-value pairs passed to the server process |
| Auto-connect | Automatically connect this server when Kognar starts |
- Click Test to verify the connection works before saving
- Click Connect
Managing connections
From the MCPs tab in Power Tools, each server shows its status, the tools it exposes, and buttons to:
- Connect / Sign in — Start the connection. Remote servers that require login open your browser once; after you authorize, Kognar finishes the connection automatically.
- Disconnect — Stop the connection (keeps a saved login when applicable)
- Sign out — Clears the saved login for that remote server
- Reconnect — Disconnect and reconnect (useful after server updates)
Status Sign-in required means the server needs authorization and no browser was opened yet (for example after app startup). Click Sign in to complete it.
The connection timeout is 60 seconds for the MCP handshake. Browser authorization can take up to a few minutes.
Using MCP tools in conversations
Once connected, MCP server tools appear automatically in conversations. You don't need to do anything special — just chat normally and the AI will use the available tools when they're relevant.
Tool results appear as tool cards in the chat thread, showing:
- The tool name
- The result returned by the server
- Whether the tool is currently running or complete
Quick access from the conversation
The MCPs tab in the Power Tools panel shows every configured server at a glance, with its status and tool count. You can connect, sign in or disconnect servers there without leaving the conversation.
MCP servers used to be managed in Settings → Agents & MCP → MCPs. That Settings section is not available in the current build — use Power Tools instead.
Binding servers to agents
By default every connected server's tools are offered to the model. If you link MCPs to specific agents in Power Tools → Agents, only the servers bound to the agents you have enabled are used. See Power Tools.
Troubleshooting
Server won't connect:
- Check that the command or URL is correct
- Make sure required dependencies are installed (e.g.,
node,npx) - Check the environment variables are set correctly
- For remote servers that need login, complete the browser authorization window
- Try clicking Test to see a detailed error message
Sign-in required after startup:
- Auto-connect does not open the browser by itself. Click Sign in on the server card.
Tools not appearing:
- Disconnect and reconnect the server
- Make sure the server is running and responding
Connection drops during a conversation:
- The server may have timed out or crashed
- Reconnect from the Power Tools → MCPs tab and continue your conversation