Skip to main content
Glama
koosoftware

QMSCloud Reporting MCP Server

by koosoftware
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

Server Configuration

Describes the environment variables required to run the server.

NameRequiredDescriptionDefault
METABASE_API_KEYYesThe Metabase API key
METABASE_BASE_URLNoBase URL of the Metabase server (default: http://54.251.164.99:7777)http://54.251.164.99:7777

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

Features and capabilities supported by this server

Protocol revision2025-11-25

CapabilityDetails
tools
{
  "listChanged": true
}

Tools

Functions exposed to the LLM to take actions

NameDescription
get_reportA

Fetch a QMSCloud report from Metabase and analyze it to answer the user's question. Returns a compact summary (distinct tickets; breakdowns by status, service, branch, counter, business date; a ticket_numbers list; and waiting/serving-time stats) plus a few sampleRows. For questions that require listing individual tickets WITH their times, pass detail=true to also get a per-ticket table. Pass the exact report key (call list_reports if unsure). Supply start_date/end_date as YYYY-MM-DD from the user's intent (defaults to current month-to-date). The tenant (company/branch) is resolved automatically from the workspace — do not ask the user for it. Currently available: 'ticket_summary'.

list_reportsA

List the QMSCloud report keys this server can fetch from Metabase.

Prompts

Interactive templates invoked by user choice

NameDescription

No prompts

Resources

Contextual data attached and managed by the client

NameDescription

No resources

Deploy Server
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

TDQS

A4/5.0

Scored across 2 tools

Disambiguation5/5

The two tools are clearly distinct: one lists available reports, the other fetches a specific report. No ambiguity.

Naming Consistency5/5

Both tools follow a consistent verb_noun pattern with snake_case: list_reports and get_report.

Tool Count4/5

For a focused reporting server with only one report type currently available, two tools (list and get) are appropriate and efficient.

Completeness3/5

Covers the essential operations for its narrow domain (listing and retrieving a report). However, it lacks support for other expected reports or more advanced filtering, limiting completeness.

Maintenance

ActivityStale
ResponsivenessNo issues

Resources