flin-linkedin-posts-mcp
Click on "Deploy Server".
Wait a few minutes for the server to deploy. Once ready, it will show a "Started" state.
In the chat, type
@followed by the MCP server name and your instructions, e.g., "@flin-linkedin-posts-mcp list my recent LinkedIn posts"
That's it! The server will respond to your query, and you can continue using it as needed.
Here is a step-by-step guide with screenshots.
flin-linkedin-posts-mcp
flin-linkedin-posts-mcp is a local MCP server for reading and analyzing the authenticated member's own LinkedIn post/share data.
It uses LinkedIn member OAuth login and the Member Data Portability API. Each user runs the MCP locally, signs into their own LinkedIn account in the system browser, and stores their token on their own machine.
The MCP supports two login flows:
Regular 3-legged OAuth with a client secret. This is the recommended local setup for most LinkedIn Developer apps.
Native OAuth PKCE. This does not require a client secret, but LinkedIn must explicitly enable the Native PKCE protocol for your app.
Important Access Requirement
This MCP does not bypass LinkedIn API approval. Each user should create their own LinkedIn Developer app with access to Member Data Portability API (Member) and the r_dma_portability_self_serve permission. Without that product/scope, LinkedIn returns 403 ACCESS_DENIED for memberSnapshotData.
Native PKCE is a separate LinkedIn app capability. If LinkedIn shows Not enough permissions to access Native PKCE protocol, use the regular 3-legged OAuth setup below or ask LinkedIn to enable Native PKCE for the app.
Relevant LinkedIn docs:
3-legged OAuth: https://learn.microsoft.com/en-us/linkedin/shared/authentication/authorization-code-flow
Native OAuth PKCE: https://learn.microsoft.com/en-us/linkedin/shared/authentication/authorization-code-flow-native
Member Snapshot API: https://learn.microsoft.com/en-us/linkedin/dma/member-data-portability/shared/member-snapshot-api
Snapshot domains: https://learn.microsoft.com/en-us/linkedin/dma/member-data-portability/shared/snapshot-domain
API access overview: https://learn.microsoft.com/en-us/linkedin/shared/authentication/getting-access
Related MCP server: LinkedIn MCP Server
Features
Browser-based LinkedIn login with regular OAuth or native PKCE
Local token storage outside the repository
Auth status and logout tools
Snapshot domain count/debug tool
Authenticated member post/share listing from
MEMBER_SHARE_INFOPost analysis for counts, text length, hashtags, mentions, and top terms
Best-effort extraction of engagement counters when they are present in snapshot rows
Draft-to-published matching based on provided draft texts
Optional engagement enrichment via LinkedIn
socialMetadataandmemberCreatorPostAnalytics
MCP Tools
auth_statusloginlogoutlist_snapshot_domainslist_member_postsanalyze_member_postsmatch_drafts_to_member_postsget_post_social_metadataget_member_post_analyticsenrich_member_posts_with_engagement
Configuration
Required for login:
LINKEDIN_CLIENT_ID: LinkedIn Developer app client ID
Recommended for regular 3-legged OAuth:
LINKEDIN_CLIENT_SECRET: LinkedIn Developer app client secret. If set,LINKEDIN_OAUTH_FLOWdefaults toauthorization_code.LINKEDIN_REDIRECT_URI: exact local callback URI registered in the LinkedIn app, for examplehttp://127.0.0.1:63141/callback.
Optional:
LINKEDIN_OAUTH_FLOW:authorization_codeornative_pkce. Defaults toauthorization_codewhenLINKEDIN_CLIENT_SECRETis set, otherwisenative_pkce.LINKEDIN_SCOPES: defaults tor_dma_portability_self_serveLINKEDIN_API_VERSION: defaults to202610for Marketing API requests; engagement requests use at least202610. Member Snapshot requests always use202312.LINKEDIN_RESTLI_PROTOCOL_VERSION: defaults to2.0.0LINKEDIN_TIMEOUT_SECONDS: defaults to30LINKEDIN_MAX_RETRIES: defaults to3LINKEDIN_OAUTH_TIMEOUT_SECONDS: defaults to300LINKEDIN_TOKEN_FILE: defaults to~/.flin-linkedin-posts-mcp/tokens.json
Additional LinkedIn access may be required for engagement enrichment:
socialMetadataaccess for comment and reaction summariesr_member_postAnalyticsfor member post impressions, reach, reactions, comments, and reshares
The Marketing API default is LinkedIn's October 2026 version, the latest release as of October 16, 2026.
The Member Snapshot API
only supports 202312. Post listing, analysis, draft matching, and snapshot-domain discovery
always use that version, regardless of LINKEDIN_API_VERSION. The Marketing API version
calendar does not apply to this endpoint. Engagement requests use 202610 when configured
with an older version, and preserve newer explicit versions.
Check the LinkedIn migration table
when upgrading. API version updates do not grant additional OAuth permissions.
See docs/linkedin-analytics-access-application.md for Community Management API application steps,
request copy, privacy-policy notes, and the MCP configuration to use after LinkedIn approves
r_member_postAnalytics.
The MCP intentionally does not require LINKEDIN_ACCESS_TOKEN anymore. Tokens are created through the login tool.
LinkedIn Developer App Setup
Create or open a LinkedIn Developer app.
Add/obtain access to
Member Data Portability API (Member).Make sure the app can request
r_dma_portability_self_serve.For regular 3-legged OAuth, add an exact loopback redirect URL in the app's Auth tab, for example
http://127.0.0.1:63141/callback.Set
LINKEDIN_CLIENT_ID,LINKEDIN_CLIENT_SECRET, andLINKEDIN_REDIRECT_URIto the same redirect URL.For native PKCE only, ask LinkedIn to enable Native PKCE OAuth for the app, omit
LINKEDIN_CLIENT_SECRET, and configure loopback redirect URIs as LinkedIn requires.
Claude Desktop on macOS: installable extension
Download the .mcpb file from GitHub Releases and install it in Claude Desktop's Extensions settings. The extension prompts for your LinkedIn app credentials; the client secret is marked sensitive. A current Claude Desktop with MCPB 0.4 / UV support manages Python and the locked dependencies on first start.
Schritt-für-Schritt-Anleitung auf Deutsch · Security review · Security model
The LinkedIn API approval described above is still required. Releases include SHA256SUMS; the bundle is unsigned.
Claude Desktop Configuration (manual alternative)
For the hardened wheel attached to the GitHub release (requires uv):
{
"mcpServers": {
"flin-linkedin-posts-mcp": {
"command": "uvx",
"args": ["--from", "https://github.com/flin-agency/flin-linkedin-posts-mcp/releases/download/v0.3.0/flin_linkedin_posts_mcp-0.3.0-py3-none-any.whl", "flin-linkedin-posts-mcp"],
"env": {
"LINKEDIN_CLIENT_ID": "<YOUR_LINKEDIN_CLIENT_ID>",
"LINKEDIN_CLIENT_SECRET": "<YOUR_LINKEDIN_CLIENT_SECRET>",
"LINKEDIN_REDIRECT_URI": "http://127.0.0.1:63141/callback",
"LINKEDIN_SCOPES": "r_dma_portability_self_serve",
"LINKEDIN_API_VERSION": "202610"
}
}
}
}For local development from this repository:
{
"mcpServers": {
"flin-linkedin-posts-mcp": {
"command": "uv",
"args": ["run", "flin-linkedin-posts-mcp"],
"cwd": "/path/to/flin-linkedin-posts-mcp",
"env": {
"LINKEDIN_CLIENT_ID": "<YOUR_LINKEDIN_CLIENT_ID>",
"LINKEDIN_CLIENT_SECRET": "<YOUR_LINKEDIN_CLIENT_SECRET>",
"LINKEDIN_REDIRECT_URI": "http://127.0.0.1:63141/callback",
"LINKEDIN_SCOPES": "r_dma_portability_self_serve",
"LINKEDIN_API_VERSION": "202610"
}
}
}
}After adding the config, restart the MCP host and call:
auth_statusloginlist_snapshot_domainslist_member_postsoranalyze_member_postsmatch_drafts_to_member_postsif you want to compare draft text to published postsget_post_social_metadata,get_member_post_analytics, orenrich_member_posts_with_engagementif your LinkedIn app has the required engagement scopes
Local Development
python3 -m pip install -e '.[dev]'
pytest -q
ruff check .Packaging
Build the desktop bundle with python scripts/build_mcpb.py after uv lock --check. Only explicitly allowlisted files enter dist/desktop/; the archive includes uv.lock and a SHA-256 checksum.
python3 -m buildThe package entry point is:
flin-linkedin-posts-mcpTroubleshooting
LINKEDIN_CLIENT_ID is required before running login: setLINKEDIN_CLIENT_IDin the MCP config.Not enough permissions to access Native PKCE protocol: the LinkedIn app does not have Native PKCE enabled. SetLINKEDIN_CLIENT_SECRETandLINKEDIN_REDIRECT_URIto use regular 3-legged OAuth, or ask LinkedIn to enable Native PKCE for the app.LINKEDIN_REDIRECT_URI is required when LINKEDIN_OAUTH_FLOW=authorization_code: add the same exact local callback URL to the LinkedIn app's Auth tab and to the MCP config.403 ACCESS_DENIEDforpartnerApiMemberSnapshotData: the LinkedIn Developer app/token likely does not have Member Data Portability API access orr_dma_portability_self_serve.LinkedIn token has expired: runloginagain. If LinkedIn issued a refresh token, the MCP attempts a refresh automatically before requiring login.Timed out waiting for LinkedIn OAuth callback: rerunloginand complete the browser flow withinLINKEDIN_OAUTH_TIMEOUT_SECONDS.403 ACCESS_DENIEDonsocialMetadataormemberCreatorPostAnalytics: the LinkedIn app/token does not have the extra engagement permissions needed for those tools.426 NONEXISTENT_VERSIONonmemberSnapshotData: upgrade to0.2.9or later and restart the MCP host. Version0.2.8incorrectly sent the Marketing API version to the snapshot endpoint; the fix pins snapshot requests to202312.
Notes
The MCP reads only the authenticated member's own snapshot data.
It does not support arbitrary-author LinkedIn post lookup.
MEMBER_SHARE_INFOis snapshot/export-style data, so field names can vary. The normalizer is intentionally tolerant and keepsinclude_raw=trueavailable for debugging.LinkedIn's portability data for
Sharesis documented around fields like date, link, commentary, media URL, and visibility. Likes, comments, and impressions are exposed only if they appear in the snapshot payload returned for that member.Saved LinkedIn drafts are not exposed as a documented portability snapshot domain here.
match_drafts_to_member_postscompares draft texts you already have against published posts; it does not fetch drafts from LinkedIn.analyze_member_postscan return very large payloads wheninclude_posts=true. Usepost_limitto cap the embeddedpostslist, or setinclude_posts=falsewhen you only need aggregate metrics.enrich_member_posts_with_engagementkeeps export discovery and engagement lookup separate. It fetches exported posts first, derives post URNs, then merges insocialMetadataand analytics where available.Bulk enrichment is intentionally bounded. Use
limitto keep the number of analytics calls under control and expect per-postengagement_errorswhen a URN cannot be derived or LinkedIn denies a lookup.
Available Tools
10 toolsanalyze_member_postsD
Analyze the authenticated member's LinkedIn posts/share records
Inputs: top_n, page_size, post_limit, include_posts, +1 more.
auth_statusA
Check whether the local MCP has a usable LinkedIn OAuth token
Inputs: no named parameters.
enrich_member_posts_with_engagementC
Enrich exported member posts with LinkedIn social metadata and analytics when scopes are available
Inputs: limit, page_size, published_after, analytics_metric_types, +2 more.
get_member_post_analyticsC
Fetch LinkedIn analytics metrics for a single member-owned post
Inputs: post_url, post_urn, metric_types.
get_post_social_metadataC
Fetch comment and reaction summary data for a single LinkedIn post
Inputs: post_url, post_urn.
list_member_postsC
List posts/share records for the authenticated LinkedIn member
Inputs: limit, page_size, include_raw, published_after.
list_snapshot_domainsB
List available LinkedIn Member Data Portability snapshot domains and item counts
Inputs: page_size.
loginA
Start browser-based LinkedIn OAuth login and store the token locally
Inputs: no named parameters.
logoutA
Delete the locally stored LinkedIn OAuth token
Inputs: no named parameters.
match_drafts_to_member_postsC
Match draft post texts against the authenticated member's published LinkedIn posts
Inputs: drafts (required), page_size, post_limit, published_after, +1 more.
Tool Schema Changelog
Recent tool additions, removals, and schema changes observed during successful MCP inspections.
Loading tool schema changelog…
TDQS
Scored across 10 tools
Each tool has a clearly distinct purpose: authentication (login, logout, auth_status), post listing and analysis (list_member_posts, analyze_member_posts), enrichment and analytics (enrich_member_posts_with_engagement, get_member_post_analytics, get_post_social_metadata), snapshot domains (list_snapshot_domains), and draft matching (match_drafts_to_member_posts). No two tools overlap functionally.
Most tools use a consistent snake_case verb_noun pattern (e.g., list_member_posts, get_member_post_analytics). The exceptions are 'login' and 'logout', which are single verbs but still clear and follow conventional auth naming. The overall pattern is predictable and readable.
With 10 tools, the server is well-scoped for its purpose of analyzing LinkedIn posts and managing authentication. Each tool serves a distinct function without redundancy, and the count is neither too sparse nor overwhelming for the domain.
The tool set covers core workflows: authentication, listing, analysis, enrichment, and analytics. Missing is a direct 'get post by ID' tool, but that functionality is partially covered by analytic and metadata tools that require a post identifier. The snapshot domain tool adds breadth. Overall, the surface is nearly complete for analyzing member posts.
Maintenance
Related MCP Connectors
LinkedIn intelligence: post analytics and research for public profiles and company pages.
Search, label and export your LinkedIn saved posts, then draft, schedule and publish from them.
Read-only access to your what2post LinkedIn data: posts, profile stats, follower growth and goals.
Draft LinkedIn posts in your voice, then schedule or publish them through LinkedIn's official API.
Related MCP Servers
- AlicenseNot gradedqualityDmaintenanceEnables users to fetch, analyze, and manage LinkedIn posts data through tools that retrieve profiles, search posts by keywords, filter by date, and identify top-performing content based on engagement metrics.MIT
- FlicenseNot gradedqualityDmaintenanceEnables users to search for jobs, retrieve profiles, and fetch feed posts through the LinkedIn API. It also provides tools for analyzing and extracting data from PDF resumes.-
- AlicenseAqualityDmaintenanceEnables posting content, sharing articles, and managing LinkedIn profile through natural language using the official LinkedIn REST API with OAuth 2.0.79 npmMIT
- AlicenseNot gradedqualityDmaintenanceEnables reading your own LinkedIn posts and articles inside Claude Desktop via LinkedIn's official OAuth 2.0 API.MIT