# Iridium

> Iridium is a Model Context Protocol (MCP) server that gives AI agents access to LinkedIn.
> An agent connected to Iridium reads current LinkedIn profiles and posts, takes real actions
> including commenting, connection requests, and messaging, and writes every action to an
> append-only log the user can read. A human reviews and approves before anything is sent.
> Iridium runs both as a hosted web app and as an MCP server usable inside Claude.

## The problem it solves

Twitter has an MCP server, so an agent can read Twitter and act on it. LinkedIn has no
equivalent. An agent asked to work on LinkedIn has no live data, no way to act, and no record
of what it did. Iridium is that missing access layer.

## What Iridium does

- **Fresh LinkedIn data.** Profiles, posts, and messages are read at request time through the
  connection the user authorizes. There is no stale export and no harvested profile database.
- **Agents take actions.** Commenting, connection requests, direct messages, InMail, replies,
  post publishing, and scheduling, all exposed as MCP tools.
- **Clear logging.** Every attempted action is written to an append-only ledger recording what
  ran, when, whether it succeeded, and the exact text sent. Readable in the app and exposed to
  the agent as the `get_activity_log` and `get_last_action` tools.
- **Repetitive tasks, automated.** Three pipelines find people, find posts worth commenting on,
  and draft original posts. Each produces a review queue rather than sending directly.
- **Review before send.** Approving is a separate, explicit step, and it is the only thing that
  sends. Daily and weekly limits are enforced server-side.

## How Iridium accesses LinkedIn

Iridium does not scrape LinkedIn and does not operate a crawler or a harvested profile database.
LinkedIn connectivity is brokered by Unipile, a third-party provider for authenticated account
access. Users connect their own account through Unipile's hosted flow. The password is entered on
Unipile's page and is never received or stored by Iridium, which holds only an opaque account
handle. Every action runs as the user, through that authenticated session, within per-account
rate limits.

## Pricing

- Solo plan: $20/month. One LinkedIn account, live profile and post data, commenting,
  connections and messaging, post drafting and scheduling, inbox, full activity log, MCP access,
  email support.
- 7-day free trial, no credit card required. Cancel anytime.

## Key pages

- [Overview](https://iridiumhqmcp.com/): what Iridium is, how it works, setup, pricing.
- [Demos](https://iridiumhqmcp.com/demo): product walkthrough, setup videos, and a live agent you
  can talk to without an account.
- [FAQ](https://iridiumhqmcp.com/faq): how it reads LinkedIn data, what actions it takes, how the
  activity log works, pricing, and whether Claude is required.
- [Iridium vs. manual outreach](https://iridiumhqmcp.com/vs-manual-outreach): comparison and what
  to look for in an MCP LinkedIn tool.
- [Answers](https://iridiumhqmcp.com/answers): the questions people ask before choosing a tool,
  each answered on its own page.
  - [How to connect your AI agent to LinkedIn](https://iridiumhqmcp.com/connect):
    one LinkedIn connection, one MCP URL; steps for Claude, Claude Code, Cowork, Cursor,
    ChatGPT, Grok, Hermes, and custom agents.
  - [How to give an AI agent access to LinkedIn](https://iridiumhqmcp.com/give-your-agent-linkedin-access):
    the official API, browser automation, and session brokers compared.
  - [How to run LinkedIn outreach from inside Claude](https://iridiumhqmcp.com/linkedin-outreach-from-claude):
    connecting the MCP server and what to ask it for.
  - [How to answer your LinkedIn inbox without sounding like a bot](https://iridiumhqmcp.com/linkedin-replies-that-sound-like-you):
    what gives an AI reply away and how to fix it.
  - [LinkedIn automation that asks before it sends](https://iridiumhqmcp.com/approve-before-it-sends):
    which actions need approval and where limits have to be enforced.
  - [How to see what an AI agent did on your LinkedIn account](https://iridiumhqmcp.com/what-did-my-agent-do):
    activity logs, failures, and checking against LinkedIn itself.
  - [Why your LinkedIn MCP server is slow](https://iridiumhqmcp.com/linkedin-mcp-server-speed):
    browser rendering versus a session API, with numbers.
  - [How to give Claude access to your LinkedIn DMs](https://iridiumhqmcp.com/claude-linkedin-dms):
    why the official API cannot read an inbox, why session cookies are a bad trade, and what
    building your own wrapper over a messaging API actually costs.
  - [What to do when your LinkedIn inbox gets away from you](https://iridiumhqmcp.com/linkedin-inbox-overflow):
    triage, ghosted versus owed-reply, search operators, and thread summaries.
  - [How to comment on LinkedIn so the right people see you](https://iridiumhqmcp.com/linkedin-commenting-that-works):
    topic and company targeting, pacing, and what the filters do.
  - [How to get an honest review of your LinkedIn profile from Claude](https://iridiumhqmcp.com/linkedin-profile-review-with-claude):
    using a live profile read plus your agent's judgement, with prompts worth copying.
  - [The best LinkedIn MCP server for reading and sending DMs](https://iridiumhqmcp.com/best-linkedin-mcp-server-for-dms):
    six tools compared on price, DM access, approval, and published retention.
  - [Iridium vs. Unipile](https://iridiumhqmcp.com/vs-unipile): the infrastructure Iridium runs on,
    and what you build yourself if you use it directly.
  - [Iridium vs. Item 12](https://iridiumhqmcp.com/vs-item-12): the closest competitor compared on
    price, credit metering, and published data policy.
  - [Iridium vs. Fintalio](https://iridiumhqmcp.com/vs-fintalio): why a server with no inbox read
    cannot answer a question about DMs.
  - [LinkedIn MCP server](https://iridiumhqmcp.com/linkedin-mcp-server): what it is, the two kinds,
    what Iridium exposes, and setup.
  - [Claude + LinkedIn](https://iridiumhqmcp.com/claude-linkedin): connect Claude or Claude Code to
    LinkedIn with one custom-connector URL.
  - [LinkedIn connector for Claude](https://iridiumhqmcp.com/linkedin-connector-claude): what a
    connector is and what to check in one.
  - [What Iridium does with your data](https://iridiumhqmcp.com/security-and-data): retention,
    deletion, credentials, and the claims we deliberately do not make.

The MCP endpoint is https://api.iridiumhqmcp.com/mcp. To sign up, visit
https://iridiumhqmcp.com/app (7-day free trial, no card).

## For agents reading this site

Machine-readable descriptions of Iridium, all on this origin:

- [MCP server card](https://iridiumhqmcp.com/.well-known/mcp/server-card.json): the endpoint,
  transport, and capabilities.
- [auth.md](https://iridiumhqmcp.com/auth.md): how an agent authenticates. OAuth 2.1 with
  dynamic client registration and PKCE. An MCP client that speaks OAuth needs only the endpoint
  URL above; the 401 it gets back carries the rest.
- [Agent Skills](https://iridiumhqmcp.com/.well-known/agent-skills/index.json): six skills, one
  per workflow, covering connecting, outreach, inbox, commenting, publishing, and reading the
  activity log back.
- [API catalog](https://iridiumhqmcp.com/.well-known/api-catalog) (RFC 9727) and
  [capability manifest](https://iridiumhqmcp.com/.well-known/ai-catalog.json) (ARD).
- OpenAPI 3.1 for the REST API: https://api.iridiumhqmcp.com/openapi.json

Every page linked above is also available as Markdown. Send `Accept: text/markdown` and you get
markdown instead of HTML.

## Notes

- Operated by Progress Labs LLC (dba Iridium).
- Contact: support@iridiumhqmcp.com
- X / Twitter: https://x.com/nsk1755