Import your saved posts
Add the LinkedMash extension. It imports your existing LinkedIn saved posts with the post text, author and media intact.
Not from LinkedIn. LinkedIn publishes no Model Context Protocol server and no saved-posts API, so an agent cannot reach your saves on its own. LinkedMash runs a hosted saved posts MCP server at mcp.linkedmash.com: the extension imports your LinkedIn saved posts once, then any MCP client can search, label, draft and schedule against your own library.
Add the LinkedMash extension. It imports your existing LinkedIn saved posts with the post text, author and media intact.
In LinkedMash, open Settings then Developer API and generate a token. It authenticates every MCP and REST call.
Add https://mcp.linkedmash.com/api/mcp?token=YOUR_TOKEN as an MCP server in your client config, restart it, and ask for your recent saved posts.
The MCP server is hosted, so there is nothing to clone, build or keep running. One URL and a token connect any client.
The server exposes your library as tools, not as a blob of text, so the agent queries it the way you would.

27 Claude shortcut hacks for faster prompts:

Don’t use Claude until you read this:
The same library is available over a documented REST API, so your own scripts and automations use the identical data.
Product details verified
No. LinkedIn publishes no Model Context Protocol server, and its public APIs cover marketing, talent and share use cases without exposing your saved posts. Any MCP access to a LinkedIn library today comes from a third-party tool that captures the posts from your own browser session first.
The hosted server is https://mcp.linkedmash.com/api/mcp. Clients authenticate with an API token generated in LinkedMash under Settings then Developer API, passed as a token query parameter in the server URL.
Any client that speaks MCP. That includes Claude and Claude Code, ChatGPT, Cursor, VS Code, Windsurf, Codex and Raycast. They all use the same hosted server URL, so there is no per-client build.
No. The server is hosted by LinkedMash, so there is no repository to clone and no process to keep alive. You add one URL to your client config and the connection works from any machine that has your token.
MCP and the Developer API are on the Creator plan, alongside the Composer, scheduling and analytics. Reader covers saving, search, labels and export. Lifetime holders keep API and MCP access as part of the plan.
Yes, on Creator. The scheduling tools put a draft into your queue and publish through LinkedIn official Posts API at the slot you picked, using the LinkedIn account you connected. Nothing automates the LinkedIn interface in your browser.
Import your saves, generate a token, and point your client at mcp.linkedmash.com.
Import your existing saved posts · Keep new saves moving automatically