Skip to main content
Glama
Waldur MCP Server

Waldur MCP Server

Official
by waldur

Waldur MCP 서버

Waldur MCP 서버는 모델 컨텍스트 프로토콜(MCP)을 구현하여 Waldur 인스턴스와 Claude Desktop 간의 통합을 지원합니다. 이를 통해 Claude는 Waldur 인스턴스와 직접 상호 작용할 수 있습니다.

빠른 시작

  1. Claude Desktop 릴리스 페이지에서 플랫폼에 맞는 Claude Desktop을 설치하세요.

  2. Python 3.13 이상을 설치하세요.

  3. uv 패키지 관리자를 설치합니다.

설치

패키지를 설치하려면:

지엑스피1

또는 uv를 사용하여:

uv pip install waldur-mcp-server

Waldur 토큰 생성

  1. Waldur 인스턴스에 로그인하세요

  2. 사용자 이름 > 자격 증명 > API 토큰으로 이동합니다.

  3. 적절한 토큰 수명을 사용하여 새 토큰을 생성합니다. 구성에 필요합니다.

Claude Desktop MCP 서버 구성

Windows의 경우: %APPDATA%\Claude\claude_desktop_config.json

MacOS의 경우: ~/Library/Application Support/Claude/claude_desktop_config.json

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

디버깅

macOS에서는 로그 파일이 ~/Library/Logs/Claude/mcp.log 에 있습니다.

spawn uvx ENOENT 오류가 발생하면 PATH 환경 변수에 uv 설치된 Python 설치 디렉터리가 포함되어 있는지 확인하세요. 또는 구성 파일에 uvx 의 전체 경로를 지정할 수 있습니다(예: ~/Library/Frameworks/Python.framework/Versions/3.13/bin/uvx

MCP 서버는 stdio를 통해 실행되므로 디버깅이 어려울 수 있습니다. 최상의 디버깅 환경을 위해서는 MCP Inspector 사용을 강력히 권장합니다.

다음 명령을 사용하여 npm 통해 MCP Inspector를 시작할 수 있습니다.

npx @modelcontextprotocol/inspector uv --directory C:\\waldur_service run waldur-mcp-server

디버깅할 때는 필요한 환경 변수를 설정해야 합니다. 실행 시 Inspector에 브라우저에서 액세스할 수 있는 URL이 표시되어 디버깅을 시작할 수 있습니다.

일반적인 문제

  • 잘못된 토큰: 토큰 권한 및 만료를 확인하세요

  • 연결 문제: WALDUR_API_URL에 액세스할 수 있는지 확인하세요.

Available Tools

7 tools
create_invitationB

Invite users to project or organization by email

Args: scope_type: Whether to invite users to organization or project scope_name: Name of the organization or project to invite users to role: Role to assign to invited users emails: List of email addresses to invite extra_invitation_text: Custom message to include in the invitation

Inputs: scope_type (required), scope_name (required), role (required), emails (required), +1 more.

list_customersC

List all customers

Inputs: no named parameters.

list_invoicesC

List all invoices

Inputs: no named parameters.

list_offeringsC

List all offerings

Inputs: no named parameters.

list_projectsC

List all projects

Inputs: no named parameters.

list_resourcesC

List all resources

Inputs: no named parameters.

queryC

Run a read-only SQL query

Inputs: sql (required).

Tool Schema Changelog

Recent tool additions, removals, and schema changes observed during successful MCP inspections.

Loading tool schema changelog…

    TDQS

    B3.2/5.0

    Scored across 7 tools

    Disambiguation4/5

    Most tools have distinct purposes: list_customers, list_invoices, list_offerings, list_projects, and list_resources each target different Waldur entities, while create_invitation and query serve unique functions. However, the five list_* tools could potentially be confused for similar listing operations, though their descriptions clarify distinct scopes.

    Naming Consistency5/5

    Tool names follow a highly consistent pattern: six tools use verb_noun format (e.g., create_invitation, list_customers), and the seventh (query) aligns with a simple verb style. All names are in snake_case, making them predictable and readable across the set.

    Tool Count4/5

    With 7 tools, the count is reasonable for a management server, covering core listing operations and key actions like invitations and queries. It feels slightly thin for comprehensive Waldur management, but each tool serves a clear purpose without bloat.

    Completeness2/5

    The tool set is severely incomplete for Waldur management, focusing heavily on listing operations with only one creation tool (create_invitation) and a generic query. Missing are essential CRUD operations for customers, invoices, offerings, projects, and resources (e.g., create, update, delete), leaving significant gaps that will hinder agent workflows.

    Maintenance

    ActivityInactive
    ResponsivenessNo recent community issues

    Related MCP Connectors

    Related MCP Servers

    • A
      license
      Not graded
      quality
      D
      maintenance
      MCP Server simplifies the implementation of the Model Context Protocol by providing a user-friendly API to create custom tools and manage server workflows efficiently.
      39 npm
      4
      MIT
    • A
      license
      Not graded
      quality
      C
      maintenance
      MCP Server provides a simpler API to interact with the Model Context Protocol by allowing users to define custom tools and services to streamline workflows and processes.
      26 npm
      3
      MIT
    • F
      license
      Not graded
      quality
      D
      maintenance
      The MCP Server for Weaviate facilitates integration with Weaviate using a customizable Python-based server, enabling interaction with Weaviate databases and OpenAI APIs via configurable URL and API keys.
      162
      -
    • F
      license
      Not graded
      quality
      C
      maintenance
      An MCP server with HTTP/stdio support, a web admin panel for managing services, capabilities, and user permissions with Bearer token authentication, enabling relay and access control for MCP tools.
      -