linkedin-mcplisted

# LinkedIn MCP Driven by the `linkedin` MCP server (registered globally as `uvx linkedin-scraper-mcp@latest`). All tools are exposed under the `mcp__linkedin__*` namespace and operate on a real authenticated browser session for the signed-in account. The signed-in user is **Magnus Rødseth** — LinkedIn username `magnus-rodseth` (https://www.linkedin.com/in/magnus-rodseth/). When the user says "my profile", "me", "my inbox", or "my messages", that's this account. ## Quick start - Read recent DMs: `mcp__linkedin__get_inbox` (defaults to 20 most recent threads). - Open a thread by participant name/handle: `mcp__linkedin__get_conversation` with `linkedin_username`. - Find a thread by content: `mcp__linkedin__search_conversations` with `keywords`, then open via returned `thread_id`. - Look up a profile: `mcp__linkedin__get_person_profile` with `linkedin_username` (and optional `sections`). - Look up a company: `mcp__linkedin__get_company_profile` with `company_name`. ## Workflows ### Reading DMs (the main use case) 1. Default to `get_inbox` (limit 5–20) for "what's in my inbox" type asks. Don't go above 20 unless the user wants a backlog scan. 2. To open a specific thread: - If the user names a person (e.g. "the thread with Jane Doe"): pass their handle as `linkedin_username` to `get_conversation`. If they have multiple threads (e.g. organic + InMail), use `search_conversations` first to enumerate `thread_id`s, then call `get_conversation` with the right `thread_id`. -