flin-linkedin-posts-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| LINKEDIN_SCOPES | No | r_dma_portability_self_serve | |
| LINKEDIN_CLIENT_ID | Yes | LinkedIn Developer app client ID | |
| LINKEDIN_OAUTH_FLOW | No | OAuth flow type | |
| LINKEDIN_TOKEN_FILE | No | ~/.flin-linkedin-posts-mcp/tokens.json | |
| LINKEDIN_API_VERSION | No | 202312 | |
| LINKEDIN_MAX_RETRIES | No | 3 | |
| LINKEDIN_REDIRECT_URI | No | Local callback URI registered in LinkedIn app | |
| LINKEDIN_CLIENT_SECRET | No | LinkedIn Developer app client secret for 3-legged OAuth | |
| LINKEDIN_TIMEOUT_SECONDS | No | 30 | |
| LINKEDIN_OAUTH_TIMEOUT_SECONDS | No | 300 | |
| LINKEDIN_RESTLI_PROTOCOL_VERSION | No | 2.0.0 |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": false
} |
| experimental | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| auth_statusA | Check whether the local MCP has a usable LinkedIn OAuth token |
| loginA | Start browser-based LinkedIn OAuth login and store the token locally |
| logoutA | Delete the locally stored LinkedIn OAuth token |
| list_snapshot_domainsB | List available LinkedIn Member Data Portability snapshot domains and item counts |
| list_member_postsC | List posts/share records for the authenticated LinkedIn member |
| analyze_member_postsD | Analyze the authenticated member's LinkedIn posts/share records |
| match_drafts_to_member_postsC | Match draft post texts against the authenticated member's published LinkedIn posts |
| get_post_social_metadataC | Fetch comment and reaction summary data for a single LinkedIn post |
| get_member_post_analyticsC | Fetch LinkedIn analytics metrics for a single member-owned post |
| enrich_member_posts_with_engagementC | Enrich exported member posts with LinkedIn social metadata and analytics when scopes are available |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
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.