
An MCP client (Claude, Cursor, VS Code, or your agent) authenticates with a Bearer API key and gets scope-gated tools — agent_search, retriever_execute, features_get, and (ingestion scope, off by default) agentic_enrich — that search and enrich the multimodal features and vectors in your Mixpeek namespace.
Hosted Server URLs
Mixpeek runs four hosted MCP servers. Each exposes a different subset of tools so you only load what your agent needs.Setup
ReplaceYOUR_API_KEY with your key from the Mixpeek dashboard.
- Claude Desktop
- Claude Code
Add this to your Claude Desktop config file (
claude_desktop_config.json):Per-Retriever MCP Server
The retriever server is a lightweight MCP server scoped to a single retriever. It reads your retriever’sinput_schema at startup and generates a typed search tool whose parameters match exactly.
1
Install
2
Run
3
Connect
Add to your Claude Desktop config:
If your retriever’s
input_schema has a field named page or page_size, the pagination parameters are automatically renamed to _pagination_page and _pagination_page_size to avoid conflicts.RETRIEVER_MCP_):
Available Tools by Scope
Ingestion — 18 tools
Retrieval — 11 tools
Admin — 14 tools
Authentication
All MCP servers authenticate with your Mixpeek API key. The key carries the same RBAC permissions as the REST API.- Hosted servers (HTTP): Pass the key in the
Authorization: Bearer YOUR_API_KEYheader. The server injects it into every tool call. - Stdio servers: Set the
MIXPEEK_API_KEYenvironment variable, or pass--api-keyas a CLI argument.
Example Conversation
Here is what a session looks like with the Retrieval server connected:Architecture
/ingestion, /retrieval, /admin) while the full server runs at /full.
Troubleshooting
Claude can't connect to the MCP server
Claude can't connect to the MCP server
- Verify the URL is correct (e.g.
https://mcp.mixpeek.com/ingestion/mcp) - Check that the
Authorizationheader format isBearer YOUR_API_KEY - Restart Claude Desktop or Claude Code after changing config
Tool not found (404)
Tool not found (404)
- You may be calling a tool on the wrong scoped server (e.g.
execute_retrieveron/ingestion) - Use the full server if you need all tools
Retriever Server fails to start
Retriever Server fails to start
- Ensure
--retriever-idand--namespace-idare correct - Verify the API key has access to that namespace
- Check that the retriever exists via the API
Search returns empty results
Search returns empty results
- Confirm your collection has processed documents (not just uploaded files)
- Check that the retriever’s
feature_urimatches your collection’s extractor - Try a broader query or remove optional filters
Next Steps
LangChain Integration
Use Mixpeek as a LangChain tool
Retriever Stages
Configure multi-stage search pipelines
Feature Extractors
Choose the right extractor for your data
Core Concepts
Understand namespaces, collections, and documents

