Waldur

Provides local and remote Waldur MCP server endpoints for client integrations and debugging.
  • typescript

0

GitHub Stars

typescript

Language

7 months ago

First Indexed

3 months ago

Catalog Refreshed

Documentation & install

Readme and setup notes from the catalogue, plus a client-ready config you can copy for your MCP host.

Installation

Add the following to your MCP client configuration file.

Configuration

View docs
{
  "mcpServers": {
    "mcp-mirror-waldur_waldur-mcp-server": {
      "command": "uv",
      "args": [
        "--directory",
        "C:\\waldur_service",
        "run",
        "waldur-mcp-server"
      ],
      "env": {
        "WALDUR_TOKEN": "your-token",
        "WALDUR_API_URL": "https://your-waldur-instance/api"
      }
    }
  }
}

You manage an MCP server that enables your client applications to communicate with Waldur’s MCP-backed services. This server runs locally or remotely, exposing a stable interface for MCP clients to connect, start, and debug your Waldur integrations efficiently.

How to use

You will configure two MCP server entries and run them through the present MCP system. The development entry runs locally via the UV package manager, and the published entry runs through a prebuilt runtime. Each entry provides the same essential environment variables to connect to your Waldur instance.

How to install

Prerequisites you need before starting: Install Claude Desktop for your platform from the Claude Desktop releases page. Install Python 3.10 or higher. Install the UV package manager.

# Windows example for working with Waldur MCP Server
# Install Claude Desktop (from the Claude Desktop releases page)
# Install Python 3.10+
# Install UV package manager

Additional sections

Configuration and environment variables are shown in the examples below. Each MCP entry contains a command, arguments, and the necessary environment variables to connect to Waldur.

["waldur-mcp-server"]

Configuration details

Two MCP server configurations are provided. One is for development using the UV tool to run a local Waldur MCP server, and the other is for a published/production setup using UVX to run the server.

Security and debugging

Keep your Waldur API URL and token secure. When debugging, you can use the MCP Inspector to connect to the running MCP server and view its debugging URL in the browser.

Notes

Environment variables shown below must be set for each MCP entry to connect to Waldur. If you switch between development and published modes, ensure you use the corresponding command and arguments.

Available tools

MCP Inspector

A debugging tool that connects to a running MCP server to inspect requests, responses, and runtime behavior through a browser-based interface.

Built by
VeilStrat
AI signals for GTM teams
© 2026 VeilStrat. All rights reserved.All systems operational