Privacy Policy — Multi-Model MCP

Last updated: 2026-04-11

Overview

Multi-Model MCP ("the extension") is a Model Context Protocol server that runs locally on your machine. It acts as a relay between Claude Desktop and third-party Large Language Model (LLM) providers that you explicitly configure. The extension does not run any backend service, cloud component, or telemetry endpoint.

What data is collected by this extension

None.

What data leaves your machine

When you invoke a tool (ask_ai, ask_all, generate_image, etc.), the extension sends your prompt (and any attached context such as system_prompt or conversation_id-linked history) to the LLM provider you configured for that call. This happens over HTTPS directly from your machine to the provider's API endpoint.

The data you send is governed entirely by the privacy policy of the provider you chose. Before configuring a provider's API key, please review that provider's own privacy policy:

ProviderPrivacy Policy
DeepSeekplatform.deepseek.com
Google Geminipolicies.google.com
Moonshot Kimimoonshot.cn
OpenAIopenai.com
OpenRouteropenrouter.ai
Perplexityperplexity.ai
xAI Grokx.ai
Qwen (Alibaba DashScope)alibabacloud.com
GLM (Zhipu AI)bigmodel.cn

Local data storage

The extension stores the following only on your local machine:

  1. API keys — Provided through Claude Desktop's extension configuration UI (stored by Claude Desktop), or via a local .env file on your disk. Keys are never written anywhere else by this extension.
  2. Conversation history — Multi-turn context linked by conversation_id, held in process memory only for up to 30 minutes or 10 turns, whichever comes first. Nothing is written to disk. History is lost when the extension process exits.
  3. Cost tracking — A running tally of token usage and estimated cost, held in process memory, cleared on restart.
  4. Response cache (optional) — If cache_ttl_ms is configured, identical prompts are cached in process memory for the configured duration. Cache is lost on restart.
  5. Generated media — If you use generate_image or generate_video, files are written to /tmp/mcp-media/ on macOS/Linux (or the equivalent temp directory on Windows). These files persist until your operating system cleans the temp directory (typically on reboot). You may delete them at any time.

No files are written to any other location.

Your control

Changes to this policy

Material changes will be announced via the project's GitHub releases page and reflected in both the CHANGELOG.md file and the "Last updated" date above.

Contact

Issues or questions: github.com/K1vin1906/mcp-multi-model/issues