Getting it into your agent
One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.
npx agentmods add instructions/professioneit/lsp-mcp-server/claude-mdgit clone --depth 1 https://github.com/ProfessioneIT/lsp-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/professioneit/lsp-mcp-server/claude-md)<a href="https://agentmods.dev/instructions/professioneit/lsp-mcp-server/claude-md"><img src="https://agentmods.dev/badge/instructions/professioneit/lsp-mcp-server/claude-md.svg" alt="Measured on agentmods" 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 | $0.01611 | $0.01611 |
| Opus 5 | $0.00805 | $0.00805 |
| Sonnet 5 | $0.00322 | $0.00322 |
| Haiku 4.5 | $0.00161 | $0.00161 |
Grade A, and why
lsp-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 5d 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 — 124 lines — stays where its author put it; the contents beside it link to each section on GitHub.
CLAUDE.md
This file provides guidance to Claude Code (claude.ai/code) when working with code in this repository.
Project Overview
lsp-mcp-server is an MCP (Model Context Protocol) server that bridges Claude Code to Language Server Protocol (LSP) servers. It enables semantic code intelligence capabilities like go-to-definition, find-references, hover information, workspace symbol search, diagnostics, completion, rename, code actions, call/type hierarchy, and document formatting.
Build Commands
npm run build # Compile TypeScript to dist/
npm run dev # Watch mode for development
npm start # Run the compiled server (node dist/index.js)
npm test # Run unit tests (vitest)
npm run test:watch # Watch mode for tests
npm run test:integration # Run integration tests (separate vitest config)
npm run lint # Run ESLint
npm run lint:fix # Auto-fix ESLint issues
npm run typecheck # Type-check without emitting
npm run clean # Remove dist/
Running a Single Test
npm test -- tests/unit/position.test.ts # Run specific test file
npm test -- -t "converts 1-indexed" # Run tests matching pattern
Interactive Testing with MCP Inspector
npx @modelcontextprotocol/inspector node dist/index.js
Architecture
Claude Code ──[MCP/stdio]──> lsp-mcp-server ──[LSP/stdio]──> Language Servers
│
├── ConnectionManager (keyed by serverId + workspaceRoot)
├── DocumentManager (per-URI versioning, thread-safe open/close)
├── DiagnosticsCache (stores pushed publishDiagnostics)
└── Tool Handlers (24 MCP tools)
Key Design Decisions
- Server Instance Keying: Servers are keyed by
(serverId, workspaceRoot)pairs viacreateServerKey()insrc/utils/workspace.ts. This enables proper monorepo support where each workspace can have its own language server instance.
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.
- 5d ago First seen · 124 lines · 1,611 tokens per session scan A 0f9514574545
lsp-mcp-server CLAUDE.md is an instructions file published in the GitHub repository ProfessioneIT/lsp-mcp-server (21 stars, last pushed 2mo ago), licensed MIT. It adds 1,611 tokens to every session, about $0.0081 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-30.
Other instructions, from other repositories
llm-council CLAUDE.md
Claude Code instructions for amiable-dev/llm-council, covering claude.md — technical notes for llm council, project overview, running & developing, architecture: the l1→l4 layer model (adr-024) and module map (src/llmcouncil/).
openings-mcp AGENTS.md
Instructions for amikai/openings-mcp, a project described as: 💼 One MCP server to search job boards and company career sites.
mimirs CLAUDE.md
Claude Code instructions for TheWinci/mimirs, a project described as: Local MCP server that gives AI coding agents persistent, searchable memory of your codebase.
pubcrawl CLAUDE.md
Claude Code instructions for nickjlamb/pubcrawl, covering claude.md, project overview, commands, testing and architecture.
steam-games-mcp AGENTS.md
Instructions for Grinv/steam-games-mcp, covering agents.md, project shape, commands, conventions and testing the live/published server.
brapi-mcp-server AGENTS.md
Instructions for cyanheads/brapi-mcp-server, covering agent protocol, what's next?, core rules, patterns and tool — connection bootstrap.