linkedin-safe-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
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
} |
| prompts | {
"listChanged": false
} |
| resources | {
"subscribe": false,
"listChanged": false
} |
| experimental | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| auth_statusA | Check LinkedIn authentication state. Call this before posting tools; if it reports not configured/authenticated it includes exactly what to do next. Job-search tools never need authentication. |
| loginA | Start the LinkedIn OAuth login. Returns an authorization URL — show it to the user and ask them to open it in a browser (it may also open automatically); the local callback completes the flow. Afterwards, call auth_status to confirm. |
| logoutA | Delete the stored LinkedIn tokens for this machine. |
| get_my_profileA | Get the authenticated user's LinkedIn identity (name, email, person URN). Requires login. |
| create_postA | Publish a LinkedIn post as the authenticated user. IMPORTANT: posts are
public professional content — confirm the final text with the user before
calling this. Hashtags (#likeThis) work in |
| delete_postA | Delete one of the user's own posts. |
| comment_on_postA | Comment on a LinkedIn post as the authenticated user. |
| like_postA | Like a LinkedIn post as the authenticated user. |
| search_jobsA | Search LinkedIn job postings (no login required; the user's account is never
involved). |
| get_jobA | Fetch full details for one job posting: description, seniority, employment
type, salary when listed, applicant count, and the external apply URL if the
posting is not Easy Apply. |
| save_jobA | Save a job to the user's local application tracker (stores a snapshot of the
posting, including its description, so it survives delisting). Idempotent: if
already saved, appends the note instead. |
| get_saved_jobA | Get one tracked job with its snapshot (description included) and full event history (status changes and notes). |
| list_saved_jobsA | List the user's tracked jobs with pipeline counts by status. Optionally filter by status and/or a title/company substring. |
| update_job_statusA | Move a tracked job through the pipeline (interested → applied → interviewing → offer/rejected/withdrawn; archived hides it). The change is recorded in the job's event history with the optional note. |
| add_job_noteA | Append a timestamped note to a tracked job (e.g. recruiter name, interview date, salary discussed) without changing its status. |
| remove_saved_jobA | Remove a job (and its history) from the local tracker. Prefer update_job_status(..., "archived") to keep the record. |
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
- Who's Calling? MCP Hosts Are an Identity Blind Spot (And the Spec Knows It)By Om-Shree-0709 on .mcpAgent IdentityOAuth 2.1
- Your AI Chatbot Just Exposed Your CEO's Salary to an InternBy Om-Shree-0709 on .Agent IdentityMCP SecurityOAuth Delegation
- 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/AmmYoo7/linkedin-safe-mcp'
If you have feedback or need assistance with the MCP directory API, please join our Discord server