mcpstat
mcpstat documentation and demo server with local usage statistics, a tool catalog, and conversions.
Que pouvez-vous faire avec mcpstat ?
- SQLite-backed - Stats persist across restarts
- Built-in MCP tools -
get_tool_usage_stats,get_tool_catalog - Tag system - Categorize and filter tools
- Token tracking - Estimate or record actual token usage
- Latency tracking - Measure execution duration, identify slow tools
- File logging - Optional timestamped audit trail
- Async-first - Database operations run in worker threads with serialized transactions
Installation
Ajoutez ceci à la configuration MCP de votre client (Claude Desktop : claude_desktop_config.json ; Cursor : .cursor/mcp.json ; VS Code et les autres utilisent la même forme « mcpServers »).
mcpstatclaude mcp add mcpstat -e 'OTEL_SDK_DISABLED=<OTEL_SDK_DISABLED>' -e 'OTEL_PROPAGATORS=<OTEL_PROPAGATORS>' -- uvx mcpstat==0.3.0
{
"mcpServers": {
"mcpstat": {
"command": "uvx",
"args": [
"mcpstat==0.3.0"
],
"env": {
"OTEL_SDK_DISABLED": "<OTEL_SDK_DISABLED>",
"OTEL_PROPAGATORS": "<OTEL_PROPAGATORS>"
}
}
}
}
Variables d'environnement
OTEL_SDK_DISABLEDDisable OpenTelemetry SDK signals for this server process.OTEL_PROPAGATORSDisable OpenTelemetry context and baggage propagation.
Documentation
Tirée du README du projet sur GitHub, actualisée chaque semaine. Les liens ouvrent GitHub.
Sommaire
mcpstat
Python observability and usage analytics for MCP (Model Context Protocol) servers.
Track tool, prompt, and resource calls, successful and failed invocations, and execution latency in local SQLite storage. Add tracking to your existing Python MCP server and expose its statistics as MCP tools that an assistant can query. Optional file logging provides an audit trail.
Installation
pip install mcpstat
pip install "mcpstat[server]" # Includes the SDK for the example below
Quick Start
from mcp.server import MCPServer
from mcpstat import MCPStat, disable_sdk_tracing
app = MCPServer("my-server")
disable_sdk_tracing(app)
stat = MCPStat("my-server")
@app.tool()
@stat.track(name="echo")
async def echo(message: str) -> str:
"""Return a message, tracking usage and latency automatically."""
return message
@app.tool()
async def get_tool_usage_stats() -> dict:
"""Return cumulative MCP usage statistics."""
return await stat.get_stats()
if __name__ == "__main__":
try:
app.run()
finally:
stat.close()
Connect your assistant to this server, then ask: "Give me MCP usage stats"
For a complete request-to-statistics example, follow the weather server walkthrough. It demonstrates successful calls, an intentional failure, unused tools, and statistics that persist after restarting the server.
Choose Your Integration
| Use case | Installation | What it tracks |
|---|---|---|
| Add tracking to an existing Python server | pip install mcpstat | The handlers you instrument with the SDK-independent library; keep your server's MCP SDK installed separately. |
| Run the bundled documentation and demonstration server | pip install "mcpstat[server]" | Its own temperature conversion tools and other registered handlers. |
The decorator records usage; register a statistics tool such as get_tool_usage_stats
to query that data from Claude Code, VS Code, or another MCP client. The standalone
server does not automatically observe other MCP servers.
Features
- SQLite-backed - Stats persist across restarts
- Built-in MCP tools -
get_tool_usage_stats,get_tool_catalog - Tag system - Categorize and filter tools
- Token tracking - Estimate or record actual token usage
- Latency tracking - Measure execution duration, identify slow tools
- File logging - Optional timestamped audit trail
- Async-first - Database operations run in worker threads with serialized transactions
Install mcpstat for the SDK-independent tracking library. The [server] extra includes
the SDK and the runnable mcpstat documentation and demonstration server. The standalone
server tracks its own calls; integrate the library into each server you want to monitor.
Documentation
Full Documentation - Quick start, API reference, examples
- Quick Start - Get running in 5 minutes
- Configuration - Customize paths, logging, presets
- API Reference - Complete method reference
- Token Tracking - Cost analysis features
- Latency Tracking - Performance monitoring
- Agent Documentation Index - Links to plain Markdown guides and examples
- Full Agent Reference - Detailed integration and API summaries
Examples
# Clone and run example server
git clone https://github.com/tekkidev/mcpstat.git
cd mcpstat
pip install -e ".[dev]"
python examples/example_server.py
See examples/ for minimal and full integration patterns.
Contributing
See CONTRIBUTING.md. Run tests with:
pip install "mcpstat[dev]"
pytest tests/
License
MIT - see LICENSE for details.
MCP is a trademark of its respective owners. This project is not affiliated with or endorsed by any trademark holders.
Questions fréquentes
Qu'est-ce que mcpstat ?
mcpstat documentation and demo server with local usage statistics, a tool catalog, and conversions.
Comment installer mcpstat ?
Il s'exécute sur votre machine. Dans Claude Code : claude mcp add mcpstat -e 'OTEL_SDK_DISABLED=<OTEL_SDK_DISABLED>' -e 'OTEL_PROPAGATORS=<OTEL_PROPAGATORS>' -- uvx mcpstat==0.3.0. Pour les autres clients, collez la configuration JSON de cette page dans leurs réglages MCP.
Faut-il une clé API pour mcpstat ?
Son entrée au registre n'indique aucune clé ni secret obligatoire. Certaines fonctions peuvent tout de même demander un compte auprès du service auquel il se connecte.
mcpstat est-il open source ?
Oui. Son code est sur GitHub sous licence MIT.
Qui maintient mcpstat ?
Il est publié par tekkidev. AI.tn le référence sans le maintenir ni le recommander.
Issu du registre MCP officiel. Être listé n'est pas une recommandation : vérifiez le code et les permissions d'un serveur avant de lui donner accès à vos données.