Waldur MCP Server

Waldur MCP server enables integration between Waldur instance and Claude Desktop by implementing the Model Context Protocol (MCP). This allows Claude to interact with your Waldur instance directly. Exposed over MCP by the waldur mcp server, that capability becomes something an assistant can invoke while it works, not something you go and do afterwards.

Adding it to your client

@modelcontextprotocol/inspector on npm is all you need. Most clients run it directly, so configuration is a few lines and a restart.

Its toolset

Everything the assistant can do here goes through one of these:

• Installation — The Installation tool exposed by this server
• Debugging — On macOS, log files are located at ~/Library/Logs/Claude/mcp.log

Configuration

You will need 2 environment variables: WALDUR_API_URL, WALDUR_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.

Caveats

• 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 waldur mcp server does with a few real requests.

When to reach for it

Plenty of monitoring and observability servers cover similar ground. The differences that matter in practice are scope of access and how much setup stands between you and a working tool call. Waldur's toolset — Installation, Debugging — is a fair guide to whether it matches your workflow. It is maintained by waldur; 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.