LinkDrop
AboutConnectPricing
← All clients

MCP guide

How to connect Grok to LinkDrop

Add LinkDrop as a tool from Grok's settings. No terminal needed.

Last updated: September 28, 2026

  1. 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. Open Tools

    In Grok, open Settings, then Tools, then Add MCP server.

  3. Enter the server details

    Enter a name for the connection, the URL below as the server address, and your key as a bearer token.

    nameLinkDrop
    urlhttps://mcp.lnkdrp.com/mcp
    authBearer lnk_your_key_here

    LinkDrop is just the name Grok lists this connection under. Change it to whatever you like, and use the same name in every step that mentions it.

    Replace lnk_your_key_here with your key.

  4. Restart and verify

    Restart Grok so it picks up the new server, then 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"

    Or ask your agent: “Which LinkDrop workspace are you connected to?”

    Back on Agents, the status turns to Connected once the key has been used.

Change the key or remove LinkDrop

Open Grok › Settings › Tools, pick LinkDrop, and either paste the new token or remove the tool.

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.

Grok › Settings › Tools › Add MCP server
nameLinkDrop Acme
urlhttps://mcp.lnkdrp.com/mcp
authBearer lnk_your_key_here

Replace lnk_your_key_here with a key created in that workspace. 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