MCP guide

How to connect Gemini CLI to LinkDrop

One command in a terminal, then sign in with /mcp auth.

Last updated: September 28, 2026

1
Add LinkDrop to Gemini CLI
Run this in a terminal. No key and no header. Gemini CLI stores the server in ~/.gemini/settings.json.
```
gemini mcp add --transport http LinkDrop https://mcp.lnkdrp.com/mcp
```
LinkDrop is just the name Gemini CLI lists this connection under. Change it to whatever you like, and use the same name in every step that mentions it.
2
Sign in
Start Gemini CLI and run /mcp auth LinkDrop. LinkDrop opens in your browser: sign in if you are not already, pick the workspace this agent should work in, and click Allow.
```
/mcp auth LinkDrop
```
Verify
Ask your agent: “Which LinkDrop workspace are you connected to?”
Back on Agents, the agent is listed as Signed in, and the status turns to Connected on its first call. Revoke it there at any time.

Using a key instead

For a script, a server, or a machine with no browser. A key does everything signing in does; it just has to be pasted, and kept.

Create a key
Sign in and open Agents, then create a key named for this machine. It is shown once, so copy it right away. Keys start with lnk_ and belong to one workspace.
2
Add LinkDrop to Gemini CLI
Run this in a terminal. Gemini CLI stores the server in ~/.gemini/settings.json.
```
gemini mcp add --transport http LinkDrop https://mcp.lnkdrp.com/mcp \  --header "Authorization: Bearer lnk_your_key_here"
```
Replace lnk_your_key_here with your key.
3
Check it registered
Run gemini mcp list, or /mcp inside a session, and look for LinkDrop.
```
gemini mcp list
```

Verify the key

Check the key itself from a terminal:

curl -s https://www.lnkdrp.com/api/agent/whoami \  -H "Authorization: Bearer lnk_your_key_here" \  -H "x-lnkdrp-agent: curl/1"

Disconnect or reconnect

To disconnect, revoke the agent on the Agents page and remove LinkDrop from Gemini CLI. To connect again, add it and run /mcp auth.

gemini mcp remove LinkDrop

More than one workspace

A connection belongs to one workspace, and your client keeps one server per name. To connect another workspace, add LinkDrop again under a different name, any name you will recognize, such as LinkDrop Acme (LinkDrop-Acme in a command), and pick that workspace when you sign in, or use a key created there. Existing connections keep working, and your agent sees them all; lnkdrp_whoami on each says which workspace it acts on.

gemini mcp add --transport http LinkDrop-Acme https://mcp.lnkdrp.com/mcp

Pick that workspace when you sign in. Any name works, as long as each workspace has its own.

Troubleshooting

My client never opened the sign-in page.: Look for Authenticate, Login or /mcp auth next to LinkDrop in your client. No such option? Use an API key instead.
I signed in but the agent says unauthorized.: It was revoked, or you signed in to another workspace. Remove LinkDrop, add it again and sign in.
My client says LinkDrop already exists.: Changing the key? Remove the old entry, then add it again. Another workspace? Add it under a different name, such as LinkDrop-Acme.
I get 401 unauthorized.: The key was revoked or pasted with a stray space. Create a new one; revoking the old one is safe.
The agent sees the wrong workspace.: Each connection is tied to one workspace. Add LinkDrop again under a name of its own, such as LinkDrop-Acme, for that workspace.
How does LinkDrop know which client connected?: Your agent's app tells LinkDrop its name when it connects.
Can I have more than one key?: Yes, up to 10. One per agent lets you revoke one without touching the rest.

Still stuck? Connect your agent walks through it in full, and How LinkDrop Works covers the rest.

Open Agents →Other clients Gemini CLI MCP docs

How to connect Gemini CLI to LinkDrop

Add LinkDrop to Gemini CLI

Sign in

Verify