QMCP
Exposes a Prometheus-compatible /metrics endpoint to enable monitoring and tracking of server performance and tool invocation metrics.
This server does not currently have a deployable release on Glama. Follow the repository's setup instructions to install and configure it for your MCP client, including any required credentials and local dependencies.
qmcp
An AI assistant can only use a tool somebody has exposed to it, and some of what it does should wait for a person. qmcp is the server that keeps the record for both: it runs the tools assistants and flows call, holds the questions that wait on a person, and remembers each instruction it was given and what came of it, so work carries from one session to the next.
It is a FastAPI server with its record in SQLite, listening on
127.0.0.1:3141 (QMCP_PORT moves it), with a command line for every part:
uv run qmcp --help.
What it is for
qmcp plays several roles in the Quaternion Media stack, and each is set up on
its own. docs/roles.md says what each owns and what it
leaves to another program.
Set it up to | Page |
give an assistant or a flow tools, and stop for a person | |
run a repository's gates and hand the results to dossier | |
speak instructions at the machine and hear what the model found | |
declare how agents are arranged, and save a design | |
run the cookbook's flows, alfred renders among them | |
build agents whose tool calls are recorded here | |
change qmcp itself |
Related MCP server: AI Agent MCP Server
Start
Needs git and uv.
git clone --recurse-submodules https://github.com/quaternionmedia/qmcp.git
cd qmcp
uv sync --all-extras
uv run pytest tests walkthrough -q
uv run qmcp serveBefore starting a server on a machine that may already run one, read "Which
server, and which queue" in docs/setup/README.md:
the clone's database holds questions somebody has not answered yet.
Documentation
docs/README.md lists every page by the role it serves.
License
MIT, as REUSE.toml declares for this project's own files; vendored and
third-party files carry their own.
Tool Schema Changelog
Recent tool additions, removals, and schema changes observed during successful MCP inspections.
Loading tool schema changelog…
This server cannot be deployed
Maintenance
Related MCP Connectors
MCP server for your apps' tools and custom tools, plus hosted AI agents and approval-gated workflows
A comprehensive Model Context Protocol (MCP) server that enables AI assistants to interact with yo…
Model Context Protocol server for the Apideck Unified API. Connect any MCP-compatible agent framework to 100+ accounting systems, HRIS platforms, file storage providers, and more through one integration. More information https://www.apideck.com/mcp-server
The Mercado Pago MCP Server implements the Model Context Protocol to provide AI agents and LLMs with access to Mercado Pago's APIs and tools within compatible development environments. It acts as an intermediary that translates Mercado Pago resources into executable functions (tools) that AI applications can invoke to perform actions and automate flows. The server simplifies integration, enables using documentation to implement or improve code, and optimizes operations through natural language interactions without manual implementations.
Related MCP Servers
- AlicenseNot gradedqualityDmaintenanceA FastAPI-based implementation of the Model Context Protocol that enables standardized interaction between AI models and development environments, making it easier for developers to integrate and manage AI tasks.10MIT
- FlicenseNot gradedqualityDmaintenanceA Model Context Protocol server implementation built with FastAPI that enables AI agent interactions. Provides a structured foundation for building AI-powered applications with proper data validation and modern Python tooling.-
- AlicenseNot gradedqualityDmaintenanceModel Context Protocol server that standardizes tool discovery, execution, and context management for AI applications.MIT
- FlicenseNot gradedqualityDmaintenanceA Model Context Protocol server that connects multiple AI models into a single workflow, enabling multi-model orchestration, conversation continuity, and tools like code review, planning, and CLI-to-CLI bridging.-