LinkedIn Actions MCP
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| LINKEDIN_HOST | No | Host/IP to bind when LINKEDIN_TRANSPORT=http (e.g., a Tailscale IP). Keep it off the public internet. | |
| LINKEDIN_TRANSPORT | No | Transport mode. Set to 'http' for Streamable HTTP on a private Tailnet; the default is 'stdio'. | stdio |
| LINKEDIN_AUTHOR_URN | No | LinkedIn Author URN required to publish posts via the official API. | |
| LINKEDIN_ACCESS_TOKEN | No | Access token for the official LinkedIn API, required to publish posts via the `publish_linkedin_post` tool. |
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
} |
| logging | {} |
| prompts | {
"listChanged": false
} |
| resources | {
"subscribe": false,
"listChanged": false
} |
| extensions | {
"io.modelcontextprotocol/ui": {}
} |
| experimental | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| publish_linkedin_postC | Cria uma prévia ou publica texto e imagem no LinkedIn pela API oficial. |
| apply_to_linkedin_jobC | Abre uma vaga, anexa o currículo e envia somente quando o formulário estiver completo. |
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 2 tools
publish_linkedin_post and apply_to_linkedin_job target completely different workflows: content publishing versus job applications. There is no overlap in purpose, inputs, or side effects, so an agent can confidently select the right tool.
Both tools follow the same verb_noun pattern with consistent snake_case naming: publish_linkedin_post and apply_to_linkedin_job. The LinkedIn domain is uniformly reflected in each name.
Two tools feels thin for a server labeled LinkedIn Actions, but each tool covers a meaningful high-level action. The count is on the borderline rather than clearly over- or under-scoped.
The two core actions are present, but notable gaps remain: there is no way to search or list jobs before applying, and no update/delete/get for published posts. Agents can complete basic workflows but cannot manage or extend them.