LinkedIn MCP

Use the bundled linkedin MCP server only when the user explicitly asks for LinkedIn data or an action on LinkedIn. Do not call LinkedIn tools for unrelated work, health checks, or background maintenance.

Operating rules

• Start with the smallest read operation that can answer the request.
• Treat profile, company, job, post, feed, and message results as live LinkedIn evidence. Distinguish retrieved facts from inference.
• Keep searches and result pages modest. Do not collect data in bulk or spam.
• Never enable the plugin or its MCP server, edit the host's plugin configuration, or start a login flow merely because LinkedIn might be useful. If either component is disabled, explain that state and stop.
• send_message and connect_with_person are write actions. Use them only when the user explicitly authorizes the exact recipient and action. Confirm the final message or connection note unless the user has already supplied it.
• archive_conversation is a write action too: it moves a thread out of the user's inbox. Use it only when the user explicitly asks to archive that thread.
• dismiss_job hides a job from every later search and cannot be undone. Use it only for jobs the user asked to dismiss.
• Do not retry a failed write action unless the result proves it was not sent.

Browser and authentication

The server uses a managed Chromium browser and the user's own LinkedIn session. Installing or enabling the plugin does not sign in. The first LinkedIn data request may prepare the browser, import an existing local session, or require a visible login window. If LinkedIn presents a captcha, two-factor prompt, or other user-owned authentication step, stop and ask the user to complete it.

If browser setup or authentication is still in progress, report that exact state and retry once after it finishes. Do not loop, launch extra browser instances, clear profiles, or replace the user's browser session.

Tool selection