Skip to main content
Glama
waldur

Waldur MCP Server

Official
by waldur

Server Configuration

Describes the environment variables required to run the server.

NameRequiredDescriptionDefault
WALDUR_TOKENYesYour token for accessing the Waldur API.
WALDUR_API_URLYesThe API URL of your Waldur instance.
UV_PUBLISH_TOKENNoYour token used for publishing.
UV_PUBLISH_PASSWORDNoYour password for publishing.
UV_PUBLISH_USERNAMENoYour username for publishing.

Instructions

Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.

This server publishes no instructions, or was last inspected before Glama recorded them.

Capabilities

Server capabilities have not been inspected yet.

Tools

Functions exposed to the LLM to take actions

NameDescription
queryC

Run a read-only SQL query

list_customersC

List all customers

list_projectsC

List all projects

list_resourcesC

List all resources

list_invoicesC

List all invoices

list_offeringsC

List all offerings

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

Prompts

Interactive templates invoked by user choice

NameDescription
schema_aware_query

Resources

Contextual data attached and managed by the client

NameDescription
schema://main

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 issues