Mixpeek MCP Server
OfficialClick on "Install Server".
Wait a few minutes for the server to deploy. Once ready, it will show a "Started" state.
In the chat, type
@followed by the MCP server name and your instructions, e.g., "@Mixpeek MCP Serversearch for files containing 'invoice' in my namespace"
That's it! The server will respond to your query, and you can continue using it as needed.
Here is a step-by-step guide with screenshots.
Mixpeek MCP Server
A lightweight, production-friendly Model Context Protocol (MCP) server for Mixpeek that:
Auto-loads Mixpeek's OpenAPI spec and exposes endpoints as MCP tools
Supports local and hosted use (bring-your-own API key)
Injects
AuthorizationandX-NamespaceheadersIncludes rate limits, timeouts, and redacted logs
Ships with Docker and simple configuration
Quickstart
Install
Python (PyPI):
# global (recommended)
pipx install mixpeek-mcp
# or in a venv
python -m venv .venv && source .venv/bin/activate
pip install mixpeek-mcpnpm (Node):
# run once
npx @mixpeek/mcp
# or install globally
npm i -g @mixpeek/mcpHomebrew (macOS):
# tap and install (once the tap is live)
brew tap mixpeek/tap https://github.com/mixpeek/homebrew-tap
brew install mixpeek-mcp
# temporary local formula (dev/testing):
brew install --build-from-source Formula/mixpeek-mcp.rbConfigure (env or your MCP client secret store)
cp env.sample .env
# edit as neededEnv vars:
MIXPEEK_API_KEY: Your Mixpeek API key (optional if endpoints don't require auth)MIXPEEK_API_BASE: Defaulthttps://api.mixpeek.comMIXPEEK_OPENAPI_URL: Defaults to<API_BASE>/openapi.json(or/docs/openapi.json)MIXPEEK_NAMESPACE: Optional namespace value to send viaX-NamespaceMCP_RATE_MAX_CALLS: Default20perMCP_RATE_PER_SECONDSMCP_RATE_PER_SECONDS: Default10MCP_CONNECT_TIMEOUT: Default5MCP_READ_TIMEOUT: Default30
Run locally (stdio)
# PyPI
mixpeek-mcp
# from source
python server.py
# npm
mixpeek-mcpYour MCP client (e.g., Claude Desktop) can attach to this server via stdio.
Docker
docker build -t mixpeek-mcp:latest .
docker run --rm -it \
-e MIXPEEK_API_KEY=sk_... \
-e MIXPEEK_NAMESPACE=your_namespace \
mixpeek-mcp:latestOr pull and run (once published):
docker run --rm -it \
-e MIXPEEK_API_KEY=sk_... \
-e MIXPEEK_NAMESPACE=your_namespace \
ghcr.io/mixpeek/mcp:latestDistribution
npm:
@mixpeek/mcp→https://www.npmjs.com/package/@mixpeek/mcpPyPI:
mixpeek-mcp→https://pypi.org/project/mixpeek-mcp/(publish pending)Docker Hub:
mixpeek/mcp(pending push), GHCR:ghcr.io/mixpeek/mcp(pending push)Homebrew:
mixpeek/tap/mixpeek-mcp(tap repo to be created)
Submit to Docker MCP Registry
We prepared registry.json compatible with the Official Docker MCP Registry. To submit:
Fork the registry and create a new entry under the appropriate directory per their CONTRIBUTING guide.
Include our
registry.json(update Docker image reference if you publish under a different org/tag).Open a PR. Upon approval, it will appear in the MCP catalog and Docker Desktop's MCP Toolkit.
Configuration
Required for write-protected endpoints:
MIXPEEK_API_KEY:Authorization: Bearer <key>
Optional:
MIXPEEK_NAMESPACE: setsX-Namespacefor isolationMIXPEEK_API_BASE: defaults tohttps://api.mixpeek.com; testing:https://server-xb24.onrender.comMIXPEEK_OPENAPI_URL: defaults to<API_BASE>/openapi.json(or/docs/openapi.json)MCP_RATE_MAX_CALLS/MCP_RATE_PER_SECONDS: simple token bucketMCP_CONNECT_TIMEOUT/MCP_READ_TIMEOUT: request timeouts
How it works
Loads OpenAPI spec and maps GET/POST JSON endpoints to tools using
operationIdTool arguments accept top-level query parameters or a
query/bodyenvelopeForwards requests to Mixpeek with configured headers
Provides small allowlist (configurable) and redacts secrets in logs
Testing
Unit tests:
pip install -r requirements.txt
pytest -qLive test (optional):
export LIVE_MIXPEEK_API_KEY=sk_...
export LIVE_MIXPEEK_OPENAPI_URL=https://server-xb24.onrender.com/docs/openapi.json
export LIVE_MIXPEEK_API_BASE=https://server-xb24.onrender.com
pytest -q tests/test_live_integration.pyUsing with MCP clients
This server uses MCP stdio transport and the official server interface, compatible with common MCP clients.
Start the server, then point your MCP client to the stdio command (
mixpeek-mcp).
References
Mixpeek docs:
https://docs.mixpeek.com/overview/introductionMixpeek OpenAPI:
https://api.mixpeek.com/docs/openapi.jsonMCP overview:
https://modelcontextprotocol.io/docs/getting-started/intro
Notes
For production hosting, front with HTTPS, add SSO/session issuance, per-tenant rate limits, and audit logs without bodies/headers. Keep local stdio as the default; hosted HTTP/SSE can be added later.
This server cannot be installed
Resources
Unclaimed servers have limited discoverability.
Looking for Admin?
If you are the server author, to access and configure the admin panel.
Latest Blog Posts
MCP directory API
We provide all the information about MCP servers via our MCP API.
curl -X GET 'https://glama.ai/api/mcp/v1/servers/mixpeek/mcp-server'
If you have feedback or need assistance with the MCP directory API, please join our Discord server