# Which LinkedIn MCP servers stop working after 60 days

> LinkedIn OAuth tokens last 60 days with no refresh token for most apps. Here is which MCP servers that kills, and what the survivors hold instead.

URL: https://voicemoat.com/blog/linkedin-mcp-60-day-token

## Key facts
- Published: 2026-09-08
- Category: Industry
- Read time: 9 minutes
- Author: Prateek Singh
- Publisher: VoiceMoat
- Topics: LinkedIn MCP; OAuth token expiry; Model Context Protocol; w_member_social; Session cookies

## Key points
- LinkedIn access tokens last 60 days. In LinkedIn's own words, it does not generate long-lived access tokens, and programmatic refresh tokens are available only to a limited set of partners.
- So a server built on the sanctioned route stops working roughly two months after you set it up, and the fix is a manual browser login, not a background refresh.
- Very few LinkedIn MCP servers use that route at all. Of the ones that do, most have not been touched since early 2025.
- The servers that never expire avoid the problem by holding a session cookie instead. LinkedIn's own cookie table gives that credential a duration of one year, with no scopes and no per-integration revoke.
- The sanctioned route also caps you at 150 member requests a day. That ceiling plus the 60-day expiry is the entire compliant envelope, and it explains why the category drifted away from it.
- The cleanest evidence that the official path is real but rationed is a hosted server that ships a tool whose only job is to tell you the gated product has not been granted to your workspace.

## Related articles
- Will a LinkedIn MCP get your account restricted? What the terms actually say: https://voicemoat.com/blog/is-linkedin-mcp-safe
- Does LinkedIn have an analytics API? Yes, and almost no guide mentions it: https://voicemoat.com/blog/linkedin-analytics-api
- What the X API actually costs in 2026: https://voicemoat.com/blog/x-api-pricing-2026

## FAQ
Q: Why did my LinkedIn MCP server stop working?
A: If it authenticates with LinkedIn OAuth, the most likely answer is token expiry. LinkedIn issues access tokens with a 60-day lifespan and does not provide programmatic refresh tokens outside a limited set of partners, so the connector cannot renew itself and needs you to log in again.

Q: Can a LinkedIn access token be refreshed automatically?
A: Not for most applications. LinkedIn can re-issue a token without showing the consent screen, but only while the member is still logged in to LinkedIn and the existing token has not yet expired. Once it lapses, the member goes through the full authorisation flow again.

Q: How long does the LinkedIn li_at cookie last?
A: LinkedIn's own cookie table gives it a duration of one year and describes it as the cookie used to authenticate members. It carries no scopes, so it permits anything the member can do, and there is no way to revoke it for one integration without ending your other sessions.

Q: Which LinkedIn MCP servers use official OAuth?
A: Very few. In our review of the field only a handful did, and two of those have not been updated since early 2025. The best-maintained official-API server has a small fraction of the stars of the most popular cookie-based one, so popularity rankings actively hide it.

Q: Is there a rate limit on posting to LinkedIn through the API?
A: Yes. LinkedIn documents a throttle of 150 requests per member per day for sharing, alongside 100,000 per day at application level. That ceiling and the 60-day token expiry together define what is practical on the sanctioned route.

Q: Does a LinkedIn MCP server that never expires mean it is better built?
A: No, it usually means it is not using OAuth. Servers that keep working indefinitely are generally holding a session credential rather than a token, which avoids expiry by taking on a year-long unscoped credential instead, and that is the credential type LinkedIn's user agreement names under prohibited use.

Source: https://voicemoat.com/blog/linkedin-mcp-60-day-token
Site overview: https://voicemoat.com/llms.txt. AI usage policy: https://voicemoat.com/ai.txt.