LinkedIn MCP
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| LINKEDIN_CLIENT_ID | Yes | LinkedIn Developer App client ID. Required for OAuth 2.0 connection. | |
| LINKEDIN_REDIRECT_URI | Yes | The exact Authorized redirect URL: http://127.0.0.1:8787/callback | http://127.0.0.1:8787/callback |
| LINKEDIN_CLIENT_SECRET | Yes | LinkedIn Developer App client secret. Never commit the secret. |
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": true
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| linkedin_connection_statusA | Check LinkedIn publishing configuration without exposing credentials. |
| start_linkedin_connectionA | Start LinkedIn OAuth and return the authorization URL. |
| complete_linkedin_connectionB | Complete LinkedIn OAuth after authorization in the browser. |
| prepare_linkedin_postA | Prepare a LinkedIn post for human review. This never publishes. |
| publish_linkedin_postA | Publish an already-reviewed LinkedIn post only after explicit human approval. |
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 5 tools
Each tool has a clearly distinct purpose: connection status, OAuth start, OAuth completion, post preparation, and post publishing. There is no overlap between these operations, and the prepare/publish distinction is explicit. An agent can easily select the right tool for each step.
All tool names are snake_case and share the 'linkedin_' prefix, and four use a verb_noun pattern (start/complete/prepare/publish). The one exception is 'linkedin_connection_status', which uses a noun phrase instead of 'get_connection_status', a minor deviation. Overall the pattern is predictable and readable.
With 5 tools, the set is well-scoped for a LinkedIn publishing/OAuth workflow. It covers the essential steps without unnecessary redundancy, and the count is typical for a focused integration server.
The tools cover the full intended workflow: connection status, OAuth initiation/completion, post preparation, and post publishing. Minor gaps exist (e.g., no explicit disconnect or post-history tool), but these do not break the core human-in-the-loop publishing flow the server is designed for.