MCP Tools DirectoryAbout this integration
Maps allowed Mixpeek OpenAPI operations to local stdio MCP tools and forwards requests with configured authorization and namespace headers.
- Transport
- stdio
- Authentication
- api-key
- Initial setup
- credentials
- Runtime
- unattended
- Evidence
- documented
- Package
- mixpeek-mcp
- Last compatibility test
- Not independently tested
Connect your agent
mixpeek-mcpPublisher documentation reviewed; the Python package and Mixpeek endpoints were not executed. MIXPEEK_API_KEY is optional only for endpoints that do not require authentication and is required for write-protected endpoints. This Python artifact is distinct from the existing npm @mixpeek/mcp artifact.
Capabilities: Load Mixpeek's OpenAPI specification, Expose allowed Mixpeek API operations as MCP tools, Forward configured authorization and namespace headers
Connected profiles
Additional details
mixpeek-mcp
Source ↗ · Checked 2026-09-190.1.1
Source ↗ · Checked 2026-09-19Publisher documents the mixpeek-mcp command as a local MCP server using stdio transport.
Source ↗ · Checked 2026-09-19MIXPEEK_API_KEY is sent as an Authorization bearer value and is required for write-protected endpoints; public endpoints may not require it. MIXPEEK_NAMESPACE is an optional isolation header.
Source ↗ · Checked 2026-09-19An MCP client starts the mixpeek-mcp command and attaches to the server over stdio.
Source ↗ · Checked 2026-09-19Publisher documentation reviewed; package and integration endpoint not executed or independently security-audited.
Source ↗ · Checked 2026-09-19