Borrowing it
Nothing to install: this file belongs to ihiteshgupta/linkedin-mcp-server. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/ihiteshgupta/linkedin-mcp-server/main/CLAUDE.mdgit clone --depth 1 https://github.com/ihiteshgupta/linkedin-mcp-serverWrote this? Show the measurements
A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.
[](https://agentmods.dev/instructions/ihiteshgupta/linkedin-mcp-server/claude-md)<a href="https://agentmods.dev/instructions/ihiteshgupta/linkedin-mcp-server/claude-md"><img src="https://agentmods.dev/badge/instructions/ihiteshgupta/linkedin-mcp-server/claude-md/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/instructions/ihiteshgupta/linkedin-mcp-server/claude-md"><img src="https://agentmods.dev/badge/instructions/ihiteshgupta/linkedin-mcp-server/claude-md.svg" alt="Reviewed on agentmods" width="80" height="20"></a>What it costs to keep this loaded
Counted locally with the o200k_base tokenizer, which is exact for GPT models; Claude uses its own tokenizer and its counts differ. Treat this as one consistent yardstick across the catalogue rather than a bill. Prices are per million input tokens.
| Model | Per session | Once invoked |
|---|---|---|
| Fable 5.1 | $0.01233 | $0.01233 |
| Opus 5 | $0.00616 | $0.00616 |
| Sonnet 5 | $0.00247 | $0.00247 |
| Haiku 4.5 | $0.00123 | $0.00123 |
Grade A, and why
linkedin-mcp-server CLAUDE.md scanned grade A with 0 findings against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured 9d ago.
A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.
Nothing flagged
None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.
How it starts
The opening of the file, as written. The whole thing — 128 lines — stays where its author put it; the contents beside it link to each section on GitHub.
LinkedIn MCP Server
MCP server for LinkedIn posting and profile management using LinkedIn's OAuth 2.0 API.
Tech Stack
- TypeScript / Node.js 18+
- MCP SDK (@modelcontextprotocol/sdk)
- LinkedIn REST API
- OAuth 2.0 authentication
Available Tools (6 total)
linkedin_get_profile- Get authenticated user's profilelinkedin_create_post- Create text post (max 3000 chars)linkedin_create_article_post- Share article with commentarylinkedin_get_posts- Get recent postslinkedin_delete_post- Delete a postlinkedin_get_connections_count- Get connection count
Visibility Options
PUBLIC- Visible to everyone (default)CONNECTIONS- 1st-degree connections onlyLOGGED_IN- LinkedIn members only
Setup
1. Create LinkedIn Developer App
- Go to LinkedIn Developer Portal
- Create app with company page
- Add redirect URL:
http://127.0.0.1:3000/callback - Request products: "Sign In with LinkedIn" + "Share on LinkedIn"
2. Install & Configure
npm install && npm run build
mkdir -p ~/.linkedin-mcp
# Add credentials
cat > ~/.linkedin-mcp/credentials.json << 'EOF'
{
"client_id": "YOUR_CLIENT_ID",
"client_secret": "YOUR_CLIENT_SECRET"
}
EOF
# Authenticate
npm run auth
# Add to Claude Code
claude mcp add linkedin -- node ~/personal-projects/linkedin-mcp-server/dist/index.js
File Locations
- Credentials:
~/.linkedin-mcp/credentials.json - Auth token:
~/.linkedin-mcp/token.json
Development Commands
npm run build # Compile TypeScript (tsc)
npm run dev # Build + run server (tsc && node dist/index.js)
npm start # Run compiled server (node dist/index.js)
npm run auth # Interactive OAuth flow (opens browser, saves token)
No test framework is configured. Manual testing via Claude Code MCP integration.
Architecture
Server Pattern
- Entry point:
src/index.ts-- MCP server with stdio transport - API client:
src/linkedin.ts--LinkedInClientclass using nativefetchagainst LinkedIn REST API - Auth layer:
src/auth.ts-- OAuth2 credential/token management with expiry tracking - Auth CLI:
src/auth-cli.ts-- Interactive browser-based OAuth flow (local HTTP callback server, configurable port/path)
What this file has done since we first saw it
Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.
- 9d ago First seen · 128 lines · 1,233 tokens per session scan A 30a09b9d3b3b
linkedin-mcp-server CLAUDE.md is an instructions file published in the GitHub repository ihiteshgupta/linkedin-mcp-server (0 stars, last pushed 5mo ago), licensed MIT. It adds 1,233 tokens to every session, about $0.0062 per session on Opus 5. A static security scan graded it A with 0 findings. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-31.
Other instructions, from other repositories
vibetags com-example-config-AsyncTestConfig.instructions.md
Instructions for PIsberg/vibetags, covering copilot instructions for asynctestconfig and immutable type.
next.js AGENTS.md
AGENTS.md instructions for vercel/next.js, covering next.js development guide, codebase structure, monorepo overview, core package: packages/next and other important packages.
codex AGENTS.md
AGENTS.md instructions for openai/codex, covering rust/codex-rs, the codex-core crate, code review rules, crate api surface and model visible context.
vscode buildNext.instructions.md
Working notes and architecture documentation for the new esbuild-based build system in build/next. Use when making changes to the new build pipeline (transpile/bundle commands, NLS plugin, source-map handling, resource copying, or self-hosting watch tasks).
vscode oss-third-party-notices.instructions.md
Instructions for microsoft/vscode, covering vs code oss third-party-notices pipeline, architecture, pipeline flow in ci, applying the notice (cutover) and fallback chain (never fail the build).
langchain AGENTS.md
AGENTS.md instructions for langchain-ai/langchain, covering global development guidelines for the langchain monorepo, corridor security analysis, project architecture and context, monorepo structure and development tools & commands.