AI apps
Add Kin to Devin
Devin Desktop, formerly Windsurf, and Devin CLI.
Before you start
Sign in
CLI
In a terminal, add Kin to Devin CLI for every project:
devin mcp add -s user kin https://app.kinlab.ai/mcpStart the sign-in:
devin mcp login kinA Kin window opens in your browser. Kin cannot check who Devin is, so it starts read only. Check the connections ticked for it, choose Can read and change if it should make changes, then approve.
Check that
kinis listed:devin mcp list
Desktop
Open
~/.config/devin/mcp_config.json, creating it if needed, and add Kin undermcpServers:{ "mcpServers": { "kin": { "url": "https://app.kinlab.ai/mcp" } } }In Devin Desktop, open Customize from the Agents window and select MCPs. Under Install MCPs for, choose This computer, and turn on
kinif it is off.When
kinshows Needs auth, select Authenticate. A Kin window opens in your browser. Kin cannot check who Devin is, so it starts read only. Check the connections ticked for it, choose Can read and change if it should make changes, then approve.
After you connect
Ask the app to do something with an account you connected, such as "list my open Linear issues". The app searches Kin for a matching action and runs it if your rule allows it. An action set to Ask me waits for you. See Approvals and questions.
To change what this app may use, open AI apps in Kin. See What each AI app may use.
Use a profile's address
Kin's address for every AI app is https://app.kinlab.ai/mcp. A profile has its own address, shown on the profile. See Profiles.
Use a token instead
Use a token only when the app cannot sign in. Create one in Kin under AI apps, with Connect an AI app and then Paste a token (advanced). Kin shows it once. Replace YOUR_TOKEN with it. See Sign in, or use a token.
In a terminal, add Kin with your token:
devin mcp add -s user kin https://app.kinlab.ai/mcp \ -H "Authorization: Bearer YOUR_TOKEN"For Devin Desktop, put the same header in
~/.config/devin/mcp_config.json:{ "mcpServers": { "kin": { "url": "https://app.kinlab.ai/mcp", "headers": { "Authorization": "Bearer YOUR_TOKEN" } } } }
Good to know
- Devin Desktop uses the same configuration as Devin CLI, so Kin added in one shows up in the other.
- Leave out
-s userto add Kin to the current project only. - Devin asks before it calls any MCP tool unless you allow the tool or the server in its permissions.
How we checked this guide
These steps follow Devin CLI documentation as of October 31, 2026. We have not run every step.
Devin was not run here. Devin CLI 3000.11.234 registers itself with Kin and returns to an address on this computer, which Kin's own code accepts.
Source: Devin CLI documentation. These apps change their screens often, so check there if a step looks different.