Use a personal key with Gemini CLI, Cursor and other tools

Some tools take an address and a key instead of a sign-in. A personal key acts as you, with the permissions you choose when you create it, for 90 days. A key that can make changes or reach your organizations asks for your second factor first.

**Create the key**

1. Open **Connect an assistant** (/connect) and choose **Create a personal key**.
2. Pick what it may do and which organizations it can include, then choose **Create key**. A key that can make changes asks you to sign in again first.
3. Copy the key. It is shown once. Turtini keeps only a fingerprint of it.

**Gemini CLI**: add this to ~/.gemini/settings.json under "mcpServers":
"turtini": { "httpUrl": "<the Turtini MCP address>", "headers": { "Authorization": "Bearer <your key>" } }

**Cursor**: signing in is simpler: add "turtini": { "url": "<the Turtini MCP address>" } under "mcpServers" in ~/.cursor/mcp.json and choose Connect. With a key instead:
"turtini": { "url": "<the Turtini MCP address>", "headers": { "Authorization": "Bearer <your key>" } }

**VS Code**: add "turtini": { "type": "http", "url": "<the Turtini MCP address>" } under "servers" in .vscode/mcp.json and sign in when VS Code asks.

**Any other MCP client**: use the address with Streamable HTTP and send the header Authorization: Bearer <your key>.

Keep the key out of shared files and repositories. If it leaks, remove it in **Settings > Connected AI apps**; it stops working on its next request.