Mixpeek

io.github.mixpeekPublished by GitHub account mixpeekv0.1.1Updated Oct 24, 2026

Give your agent eyes. Search video, images, and audio via the Mixpeek multimodal retrieval API.

VerifiedSTDIODesktop onlyKnowledge & MemoryMedia & Design

Overview

AI-generated overview

Lets an assistant search and retrieve video, image, and audio content through the Mixpeek multimodal retrieval API.

What you can do
This server loads Mixpeek's OpenAPI specification and exposes its endpoints as MCP tools, mapping GET and POST JSON operations by operationId. Tool arguments accept top-level query parameters or a query/body envelope, and requests are forwarded to Mixpeek with the configured Authorization and X-Namespace headers. It includes rate limiting, request timeouts, a configurable endpoint allowlist, and redacted logs.
When to use it
Use it when an assistant needs to search or retrieve multimodal media assets — video, images, or audio — held in a Mixpeek account, and you want that access through a local stdio MCP client. It is aimed at bring-your-own-API-key use, either locally or hosted.
Requirements
Runs locally over stdio, installed from npm (@mixpeek/mcp) or PyPI (mixpeek-mcp, run with uvx); Docker and Homebrew options are also described. Needs network access to the Mixpeek API. Set MIXPEEK_API_KEY for write-protected endpoints; MIXPEEK_API_BASE, MIXPEEK_OPENAPI_URL, and MIXPEEK_NAMESPACE are optional, as are rate-limit and timeout variables.
Before you install
The server sends requests to the Mixpeek API using the MIXPEEK_API_KEY credential, which is forwarded as a Bearer token; anyone with access to the local environment or client secret store can read it. Because tools are generated from the remote OpenAPI spec, the available operations and any write or delete behavior depend on that spec and on the key's permissions. MIXPEEK_API_BASE can be pointed at a non-default host, which would send the key and requests elsewhere.

Installation

In SourceWeft

  1. Open Mixpeek in the dashboard and add it to a workspace.
  2. Enable the server for the chats that should use its tools.

Desktop only via STDIO. STDIO servers start a local process, so they need the SourceWeft desktop host.

Other MCP clients

Follow the launch instructions in the repository.

README

[Mixpeek MCP Server]

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 Authorization and X-Namespace headers
  • Includes rate limits, timeouts, and redacted logs
  • Ships with Docker and simple configuration

Quickstart

  1. Install

Python (PyPI):

bash
# global (recommended)pipx install mixpeek-mcp
# or in a venvpython -m venv .venv && source .venv/bin/activatepip install mixpeek-mcp

npm (Node):

bash
# run oncenpx @mixpeek/mcp
# or install globallynpm i -g @mixpeek/mcp

Homebrew (macOS):

bash
# tap and install (once the tap is live)brew tap mixpeek/tap https://github.com/mixpeek/homebrew-tapbrew install mixpeek-mcp
# temporary local formula (dev/testing):brew install --build-from-source Formula/mixpeek-mcp.rb
  1. Configure (env or your MCP client secret store)
bash
cp env.sample .env# edit as needed

Env vars:

  • MIXPEEK_API_KEY: Your Mixpeek API key (optional if endpoints don't require auth)
  • MIXPEEK_API_BASE: Default https://api.mixpeek.com
  • MIXPEEK_OPENAPI_URL: Defaults to <API_BASE>/openapi.json (or /docs/openapi.json)
  • MIXPEEK_NAMESPACE: Optional namespace value to send via X-Namespace
  • MCP_RATE_MAX_CALLS: Default 20 per MCP_RATE_PER_SECONDS
  • MCP_RATE_PER_SECONDS: Default 10
  • MCP_CONNECT_TIMEOUT: Default 5
  • MCP_READ_TIMEOUT: Default 30
  1. Run locally (stdio)
bash
# PyPImixpeek-mcp
# from sourcepython server.py
# npmmixpeek-mcp

Your MCP client (e.g., Claude Desktop) can attach to this server via stdio.

Docker

bash
docker build -t mixpeek-mcp:latest .docker run --rm -it \  -e MIXPEEK_API_KEY=sk_... \  -e MIXPEEK_NAMESPACE=your_namespace \  mixpeek-mcp:latest

Or pull and run (once published):

bash
docker run --rm -it \  -e MIXPEEK_API_KEY=sk_... \  -e MIXPEEK_NAMESPACE=your_namespace \  ghcr.io/mixpeek/mcp:latest

Distribution

  • npm: @mixpeek/mcp → https://www.npmjs.com/package/@mixpeek/mcp
  • PyPI: 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:

  1. Fork the registry and create a new entry under the appropriate directory per their CONTRIBUTING guide.
  2. Include our registry.json (update Docker image reference if you publish under a different org/tag).
  3. 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: sets X-Namespace for isolation
  • MIXPEEK_API_BASE: defaults to https://api.mixpeek.com; testing: https://server-xb24.onrender.com
  • MIXPEEK_OPENAPI_URL: defaults to <API_BASE>/openapi.json (or /docs/openapi.json)
  • MCP_RATE_MAX_CALLS / MCP_RATE_PER_SECONDS: simple token bucket
  • MCP_CONNECT_TIMEOUT / MCP_READ_TIMEOUT: request timeouts

How it works

  • Loads OpenAPI spec and maps GET/POST JSON endpoints to tools using operationId
  • Tool arguments accept top-level query parameters or a query/body envelope
  • Forwards requests to Mixpeek with configured headers
  • Provides small allowlist (configurable) and redacts secrets in logs

Testing

Unit tests:

bash
pip install -r requirements.txtpytest -q

Live test (optional):

bash
export LIVE_MIXPEEK_API_KEY=sk_...export LIVE_MIXPEEK_OPENAPI_URL=https://server-xb24.onrender.com/docs/openapi.jsonexport LIVE_MIXPEEK_API_BASE=https://server-xb24.onrender.compytest -q tests/test_live_integration.py

Using 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/introduction
  • Mixpeek OpenAPI: https://api.mixpeek.com/docs/openapi.json
  • MCP 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.

Source: README.md at commit 3312b89

Tools

0
SourceWeft has not started this package in its sandbox yet, so its tools are not known.

Version history

1
  1. v0.1.1LatestSep 16, 2026

Score

50% of the applicable checks met

How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.

  • Reached in the last 30 days25 pts

    Keep the endpoint answering the MCP handshake; SourceWeft probes it every 30 days.

  • Auth declared10 pts

    Declare the credential headers in the registry entry, or keep the endpoint answering the probe so its auth can be classified.

  • Tools listed15 pts

    Answer tools/list without a credential, or ship a package that starts in a sandbox without one.

  • DescriptionRequired15 pts
  • Logo10 pts
  • Documentation15 pts
  • License10 pts