Connect your agent

Start on the Agents page

The fastest way to connect is the Agents page in the app: click Agents in the left sidebar, or go to lnkdrp.com/agents. Choose Sign in from your agent, pick your client, and it shows the exact command or settings for your workspace, with the connection name LinkDrop filled in, which you can change before you copy. Copy it, run it, sign in when your client asks. The steps below are the same ones, written out for reference.

LinkDrop's MCP server is at https://mcp.lnkdrp.com/mcp. It is a remote server, so there is nothing to install locally. Once connected, your agent can upload PDFs, create and manage share links, set passwords, read stats and replace files in your workspace. Connecting an agent is available on every plan, Free included. Agents work under the same plan limits and credits as you do, and never take a seat; see Credits and plans.

The connection name

The connection name is what your client lists LinkDrop under, beside your other connectors such as Google Drive or Notion, and how your agent refers to it. Every command and setting on the Agents page starts with the name LinkDrop. To use another name, change it under Name this connection before you copy, and the commands follow it. Letters, digits, hyphens and underscores work in every client.

Whatever you choose, use the same name in every command for that connection, including /mcp auth <name> when you sign in and claude mcp remove <name> when you disconnect. The steps below use LinkDrop; if you chose another name, put yours in its place.

One connection is one workspace, so a second workspace needs a name of its own, such as LinkDrop Acme for a workspace called Acme (LinkDrop-Acme in a command, where spaces are not allowed). Add the server again under that name and pick that workspace when you sign in. Your agent sees every connection, and asking it "Which LinkDrop workspace is each connection on?" tells you which workspace each one acts on.

A connection you already added as lnkdrp, or under any other name, keeps working; use that name in its commands.

Connect by signing in

Signing in is the quickest way and needs no key. Claude Code, Cursor, Codex, Gemini CLI and Cowork all support it. Grok does not; use a key for Grok.

When you sign in, LinkDrop opens in your browser. Sign in if you are not already, pick the workspace the agent should work in, and click Allow. The agent then appears on the Agents page under Connected agents, named after its app (for example Claude Code) and marked "Signed in", with a Revoke button. Revoking stops it at once.

Viewers can connect an agent too. It can read but not change anything, matching their role. Roles are explained in Teams and workspaces.

Claude Code

In a terminal, run: claude mcp add --transport http --scope user LinkDrop https://mcp.lnkdrp.com/mcp
In Claude Code, run /mcp, pick LinkDrop, and choose Authenticate.
In the browser, sign in, pick the workspace and click Allow.

--scope user makes the connection available in every folder, not only the one you ran the command in.

Cursor

Add this to ~/.cursor/mcp.json (or .cursor/mcp.json inside a project), inside "mcpServers": "LinkDrop": { "url": "https://mcp.lnkdrp.com/mcp" }
Save. In Cursor's MCP settings, LinkDrop shows Needs login; click it.
In the browser, sign in, pick the workspace and click Allow.

Codex

In a terminal, run: codex mcp add LinkDrop --url https://mcp.lnkdrp.com/mcp
Then run: codex mcp login LinkDrop
In the browser, sign in, pick the workspace and click Allow.

Gemini CLI

In a terminal, run: gemini mcp add --transport http LinkDrop https://mcp.lnkdrp.com/mcp
In Gemini CLI, run: /mcp auth LinkDrop
In the browser, sign in, pick the workspace and click Allow.

Cowork

Open Cowork, then Settings, Connectors, Add MCP server.
Name: LinkDrop. URL: https://mcp.lnkdrp.com/mcp. Leave the authentication field empty.
Cowork opens LinkDrop in your browser: sign in, pick the workspace and click Allow.

Grok (key only)

Grok cannot sign in, so create a key first (see "Use an API key instead" below), then open Grok, Settings, Tools, Add MCP server. Name: LinkDrop. URL: https://mcp.lnkdrp.com/mcp. Auth: Bearer followed by your key.

Any other MCP client

Add a server named LinkDrop with the URL https://mcp.lnkdrp.com/mcp. If your client supports signing in (OAuth) for remote MCP servers, it will ask you to sign in. If it only accepts a header, use a key and send it as Authorization: Bearer followed by the key.

Full guides for each client: Claude Code, Cowork, Cursor, Codex, Gemini CLI, Grok, any MCP client. The overview is at /mcp.

Check it worked

Ask your agent: "Which LinkDrop workspace are you connected to?" It answers with the workspace name, plan and credits. If it names the wrong workspace, see "The agent sees the wrong workspace" below.

Use an API key instead

A key does everything signing in does. Use one for Grok, a script, a server, or any client that cannot open a browser.

Open the Agents page and choose Use an API key. If something is already connected, click Connect another agent first, or click Create key under Connected agents. Workspace owners and admins can create keys.
Give the key a name, such as the agent or machine it is for, and click Create.
The key is shown once. Copy it straight away; LinkDrop keeps only a hash.
A workspace can have up to 10 active keys. Use one per agent or machine so you can revoke a single one without touching the others.
The page then shows the command or settings for your client with the key filled in. It is added as a header: Authorization: Bearer followed by the key.
Revoke a key from the same page at any time. Revoke all stops every key at once.

A key belongs to the workspace it was created in. To connect another workspace with a key, switch to that workspace, create a key there, and add it under a name of its own.

Disconnect or reconnect

To disconnect, revoke the agent or key on the Agents page (it stops at once), then remove the server from your client, for example claude mcp remove LinkDrop, codex mcp remove LinkDrop or gemini mcp remove LinkDrop, or delete the LinkDrop entry from Cursor's mcp.json.
To connect again, add it again and sign in.
To change a key, remove the server from your client first, then add it again with the new key. Clients keep one server per name and refuse to add the same name twice.

What your agent can do

Share a PDF from your Google Drive once you connect it, a web link, a file on your computer, or a file in a cloud agent's own workspace, and get the link back, with an optional password and download setting. See Getting a file to your agent.
Replace the PDF on a document you already shared. Every link keeps working.
Create, list, search, update, disable and delete share links, each with its own label, audience, password and expiry. The settings are the same ones described in Share links.
Check or reveal a link's password so it can tell you what it is later.
Read stats: views, opens, downloads, pages viewed and time spent for a link or a document. Every reader with time per page, on every plan. Analytics explains each number.
List and search your documents, archive, star and tag them.
Create projects, add documents to them and manage project links, as described in Projects.
List, look up and add contacts, the people who have read your links. See Contacts.
Read a document's version history and what changed between versions.
Read the activity feed, including an audit trail of what agents did.
Report which workspace, plan and credits it is working with.

Agents do not receive or configure notification emails. You set those yourself; see Notifications and visit briefs.

Getting a file to your agent

Tell your agent where the file is and it picks the best way in. You never need to upload the file yourself. Best first:

In your Google Drive. Connect Drive on the Integrations page, then name the file or paste its Drive, Docs, Slides or Sheets link. LinkDrop fetches it from Google itself, turns Docs, Slides and Sheets into a PDF, and the document links back to the original. If Drive is not connected, your agent gives you the Integrations link and stops.
A public web link to the PDF.
A file on your computer, when LinkDrop runs on the same computer. Say where it is, or your agent asks.
A file in a cloud agent's own workspace, such as Cowork's: the agent uploads it to a one-time LinkDrop address, up to 50 MB, that expires after 15 minutes and works once. A connection that can only read cannot upload.
If your AI client blocks that upload, as Cowork can when your organization's network policy blocks uploads, your agent saves the PDF to your Downloads folder, tells you where it is, and stops. Put the file in Google Drive, or give your agent a public link, to share it.

Getting a file to your agent explains each route, and Google Drive covers connecting Drive. The connection is yours alone: an agent uses it only when it acts as you, in the workspace you connected it in.

LinkDrop writes the summary

LinkDrop writes the summary and key points for every PDF your agent shares or replaces, and it costs 1 credit like any upload. Your agent cannot supply its own summary in its place. Documents shared before September 30, 2026 with a summary written by an agent keep it, and still show which agent wrote it.

Destructive actions ask first

Deleting a share link, a document, a project or a project link always asks you first. The agent shows what would be affected, such as how many recipients opened the link and when, and will not go ahead without your yes. Archiving a document asks first only when a recipient has already opened or downloaded it; archiving is reversible and keeps the analytics. Disabling a link or removing a document from a project is reversible, so those do not ask.

Agent status in the dashboard

The left sidebar, next to Agents, shows how many are connected, such as "2 connected", or "Not connected". Clicking it opens what your agents did, or the Agents page if none is connected.
The Agents page lists your signed-in agents and keys under Connected agents, each with when it connected and when it was last used.
The activity feed attributes agent actions to the client, for example "Claude Code created a link". LinkDrop added from claude.ai, the Claude app or Cowork shows as Claude.

Troubleshooting

The client says LinkDrop "needs authentication": the server is added but the sign-in step has not been done. In Claude Code run /mcp, pick the server and choose Authenticate. In Gemini CLI run /mcp auth LinkDrop. In Codex run codex mcp login LinkDrop. In Cursor click Needs login next to the server. Then sign in in the browser, pick the workspace and click Allow.
The sign-in page never opened: your client may not support signing in for remote MCP servers. Look for Authenticate, Needs login or /mcp auth next to the server. If there is nothing like it, use a key instead.
Signed in, but the agent says unauthorized: the connection was revoked on the Agents page. Remove the server from your client, add it again and sign in.
"LinkDrop already exists": your client keeps one server per name. If you are changing the key, remove the old entry first, then add it again. If the new key is for a different workspace, do not remove anything: add it under a different name, such as LinkDrop-Acme.
401 unauthorized with a key: the key was revoked, or it was pasted with a space or line break. Keys start with lnk_ and are 36 characters long. Create a new one if in doubt; revoking the old one is safe.
The agent sees the wrong workspace: a connection belongs to one workspace, the one you picked when you signed in or the one the key was created in. Add the server again under a different name, such as LinkDrop-Acme, and pick that workspace when you sign in, so it sits next to your existing connection instead of replacing it.
Still stuck: open the Agents page to get the exact steps for your client and workspace, or contact support and a person will help.