Developer · Local MCP server
quota-mcp
Usage & quota tracker for AI subscription accounts (StepFun, Command Code)
What the MCP Registry states
The entry as published to the official MCP Registry (read 2026-10-04), latest version.
- Registry name
io.github.limitcool/quota-mcp- Version
- 0.3.2
- Status
- Active
- Category
- developer
- Transport
- stdio (local process)
- Package
- OCI image (Docker)
- Published
- 2026-09-21
- Updated
- 2026-09-21
- Publisher
- limitcool (GitHub)
- Namespace
- Namespace verified by the MCP Registry via GitHub (github.com/limitcool) · how
- Website
- github.com/limitcool/quota-mcp
- Repository
- github.com/limitcool/quota-mcp
- Source
- Registry API entry
Packages
| Registry | Package | Version | Transport |
|---|---|---|---|
| OCI image (Docker) | ghcr.io/limitcool/quota-mcp:0.3.2 | - | stdio |
How to connect quota-mcp
quota-mcp runs locally from a container image in an OCI registry such as Docker Hub or GitHub Container Registry: ghcr.io/limitcool/quota-mcp:0.3.2. It speaks MCP over stdio, so the client starts it as a program and talks to it through standard input and output. It needs Docker or another OCI container runtime; started with docker run - the usual command is docker run -i --rm -e QUOTA_MCP_MASTER_KEY -e QUOTA_MCP_DB ghcr.io/limitcool/quota-mcp:0.3.2. It reads these environment variables: QUOTA_MCP_MASTER_KEY (secret) and QUOTA_MCP_DB; set them in the client's configuration for this server.
In the mcpServers JSON format that many desktop and editor MCP clients read, the entry looks like this (placeholders in angle brackets):
{
"mcpServers": {
"quota-mcp": {
"command": "docker",
"args": [
"run",
"-i",
"--rm",
"-e",
"QUOTA_MCP_MASTER_KEY",
"-e",
"QUOTA_MCP_DB",
"ghcr.io/limitcool/quota-mcp:0.3.2"
],
"env": {
"QUOTA_MCP_MASTER_KEY": "<secret>",
"QUOTA_MCP_DB": "<value>"
}
}
}
}Derived from the registry entry, not tested here. What the server does, and on what terms, is set by its publisher; check its repository or website before giving it access to your accounts or files. How to add an MCP server to an assistant · Before you connect
More developer servers
| Server | Runs |
|---|---|
| Quiet Stance Productive Opportunity IntakePermission-aware intake for infrastructure, project development, commercial energy, and solar. | Remote · HTTPLive check: ✓ handshake |
| QuillPre-execution gate for AI-agent tool calls. Touch ID approval. Tamper-evident audit log. | Local · stdio |
| QuiltTrack which AI agent wrote which lines in a shared Git checkout; each commits only its own lines. | Local · stdio |
| QuizBaseMCP server for trivia: 1.4M+ questions (EN+PL), 24 categories, 12 tools + 4 prompts, OAuth 2.1. | Remote · HTTPLive check: ✓ handshake |
| QuoteFirstGet dollar quotes from 200+ LLMs before any work runs; accept, execute, and verify quality. | Remote · HTTPLive check: ✗ no handshake |
| Qwen DAP MCPNative runtime debugging via DAP-to-MCP for crashes, hangs, dumps, symbols, and forensics. | Local · stdio |
| r3Local Redis memory MCP for AI apps with hybrid caching and optional Mem0 cloud backup. | Local · stdio |
| RaceHooksF1 race analytics & live timing for AI assistants - webhooks, results, and race simulations. | Local · stdio |