Agent Lsp MCP Server

agent-lsp is an **MCP server** that orchestrates existing LSP servers (gopls, rust-analyzer, jdtls, etc.) into agent-native workflows.

Local serverstdioPython

What is the Agent Lsp MCP server?

Agent Lsp MCP server exists for a simple reason — assistants are far more useful when they can act on Agent Lsp directly instead of describing what you should do. agent-lsp is an MCP server that orchestrates existing LSP servers (gopls, rust-analyzer, jdtls, etc.) into agent-native workflows.

What you get

  • /lsp-refactor → impact analysis → preview → apply → verify build → run tests
  • /lsp-safe-edit → preview → diagnostic diff → apply if safe
  • /lsp-verify → LSP diagnostics → build → test suite

What the assistant can call

Once Agent Lsp is connected, these are the calls the assistant has available:

  • Documentation — The Documentation tool exposed by this server
  • Contributing — The Contributing tool exposed by this server

Configuration and credentials

You will need 2 environment variables: AGENT_LSP_OUTPUT_FORMAT, AGENT_LSP_TOKEN. The server will not start without them, which is usually why the tools fail to appear on a first run. Keep credentials in your client's env block or a secrets manager rather than in a file you might commit.

Setting it up

Installation goes through your MCP client rather than a global install: point it at @blackwell-systems/agent-lsp on npm and it is fetched when the client starts. The copy-paste blocks for Claude Desktop, Claude Code and Cursor are further down this page.

Choosing this one

Among the knowledge and memory options, the useful question is rarely "what can it do" but "what does it cost you to run" — permissions, credentials, and how much of your context its toolset consumes. Agent Lsp's toolset — Documentation, Contributing — is a fair guide to whether it matches your workflow. It is maintained by blackwell-systems; worth a glance at recent repository activity before you build anything load-bearing on it.

SyncDev reviews every entry in this directory against the project's own documentation before publishing, and revisits them as servers change.

Before you rely on it

  • It runs with your machine's permissions. That is convenient and also the reason to think about what you point it at before you approve a tool call.
  • Missing credentials fail quietly in some clients — if no tools show up, check the environment block first.
  • MCP clients confirm each tool call by default. Leave that on until you have watched what the agent lsp mcp server does with a few real requests.

Available tools

ToolWhat it does
DocumentationThe Documentation tool exposed by this server.
ContributingThe Contributing tool exposed by this server.

How to install the Agent Lsp MCP server

{
  "mcpServers": {
    "agent-lsp": {
      "command": "npx",
      "args": ["-y", "@blackwell-systems/agent-lsp"],
      "env": {
        "AGENT_LSP_OUTPUT_FORMAT": "your-value",
        "AGENT_LSP_TOKEN": "your-value"
      }
    }
  }
}

Add to claude_desktop_config.json, then restart Claude Desktop.

Configuration

VariableDescriptionRequired
AGENT_LSP_OUTPUT_FORMATConfiguration value read at startup.Optional
AGENT_LSP_TOKENCredential the server authenticates with.Yes

Example prompts to try

  • Use Agent Lsp to Documentation.
  • Use Agent Lsp to Contributing.

Frequently asked questions

It connects Agent Lsp to MCP-compatible AI assistants such as Claude and Cursor, exposing 2 tools (Documentation, Contributing) that the assistant can call on your behalf. Instead of copying data back and forth by hand, the assistant works with Agent Lsp directly.