What connects to what
Keemate provides a local MCP server. A supported AI tool connects to that server to request capabilities such as reading selected text or interacting with a window. This is separate from choosing the model that runs Keemate’s own AI commands.
Keemate is the server in this connection. Adding a provider API key does not connect a desktop AI tool, and adding a client does not make Keemate a general-purpose MCP client.
Connect Claude Code
Open Connections in Keemate and make sure the local server is available.
Choose Claude Code from the supported clients.
Create the client connection and copy the exact setup command shown by Keemate.
Run that command in your terminal.
Restart Claude Code sessions that were already open, then make a small test request.
Use the command generated by your app. It contains the local server address and that client’s authorization details, so a command copied from someone else’s setup will not be correct.
Choose permissions
Review the capabilities offered to the client. Depending on the capability, you can allow it, require a decision each time, or block it. Some sensitive actions continue to require individual approval.
Begin with the access the task needs. Review the activity log to understand what was requested and what happened. Use the global stop control when you want to cut off client access.
The generated setup contains a private client token. Keep it out of screenshots, shared snippets, and support messages. Revoke the client connection if the token is exposed.
Other supported clients
Use the supported-client list in your installed build as the authority. The repository includes manual setup entries for clients such as Cursor, Claude Desktop, VS Code, and Codex; manual instructions are not the same as an end-to-end verified integration.
Follow the configuration format expected by your client and restart it after changing its setup. Do not assume that every product with an AI feature can act as an MCP client.
If a client cannot connect
Check that Keemate is running, the local server is enabled, the address and token are current, and the global stop control is not active. If you regenerated or revoked a key, update the client’s configuration.
Read the client’s error and Keemate’s activity log together. If no request reaches Keemate, focus on the connection setup before changing capability permissions.
