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 | |
| LINKEDIN_REDIRECT_URI | No | OAuth redirect URI (default: http://localhost:3000/callback) | http://localhost:3000/callback |
| LINKEDIN_CLIENT_SECRET | Yes | LinkedIn Developer App Client Secret |
Capabilities
Features and capabilities supported by this server
| Capability | Details |
|---|---|
| tools | {
"listChanged": true
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| linkedin_loginA | Authenticate with LinkedIn via OAuth. Opens a browser for the user to log in and grant permissions. Only needed once -- tokens persist across sessions -- unless the token has expired or |
| create_image_postA | Publish an image with text to the logged-in user's personal LinkedIn feed. Requires linkedin_login to have been run first. Provide exactly one of imagePath or imageUrl. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
Latest Blog Posts
- Why MCP Servers Need Execution Sandboxing (And Why Your Current Stack Isn't Enough)By Om-Shree-0709 on .Agentic AiPrompt InjectionWebAssembly
MCP directory API
We provide all the information about MCP servers via our MCP API.
curl -X GET 'https://glama.ai/api/mcp/v1/servers/egig/linkedin-mcp'
If you have feedback or need assistance with the MCP directory API, please join our Discord server