Model reference · open weights
MiniCPM4-MCP is an open-weight language model from openbmb. MiniCPM4-MCP (BF16) weighs 16.4 GB; the smallest configuration that runs it is 2× RTX 3060 12 GB.
Summary of the openbmb/MiniCPM4-MCP model card, 2026-10-01
What it is
| Released by | openbmb |
|---|---|
| Released | 2025-06-05 |
| Parameters | 8.2B |
| VRAM | 16.4 GB for the weights |
What it runs on
| Card | Requests at once | Context max | Memory | |
|---|---|---|---|---|
| 8K each | 32K each | |||
| RTX 3060 12 GB … RTX 4060 Ti 16 GB 2 smaller cards | — | — | — | |
| RTX 3090 24 GB | 23 | 5 | all 32K | 23.4 GB |
| RTX 4090 24 GB | 23 | 5 | all 32K | 23.4 GB |
| RTX 5090 32 GB | 51 | 12 | all 32K | 31.0 GB |
| L40S 48 GB | 100 | 25 | all 32K | 44.0 GB |
| A100 80 GB | 227 | 56 | all 32K | 78.2 GB |
| H100 80 GB | 214 | 53 | all 32K | 78.1 GB |
| RTX PRO 6000 Blackwell 96 GB | 272 | 68 | all 32K | 93.8 GB |
| DGX Spark (GB10) 128 GB unified | 323 | 80 | all 32K | 107 GB |
| H200 141 GB | 437 | 109 | all 32K | 138 GB |
| B200 180 GB | 576 | 144 | all 32K | 176 GB |
| 2× RTX 3060 12 GB tensor parallel | 20 | 5 | all 32K | 11.6 GB a card |
| 2× RTX 4060 Ti 16 GB tensor parallel | 48 | 12 | all 32K | 15.4 GB a card |
| Requests at once | 8K tokens each | 32K tokens each |
|---|---|---|
| 1 | 17.3 GB | 18.2 GB |
| 5 | 18.4 GB | 22.4 GB |
| 8 | 19.2 GB | 25.7 GB |
| 16 | 21.4 GB | 34.3 GB |
| 32 | 25.7 GB | 51.4 GB |
| 64 | 34.3 GB | 85.8 GB |
One card, with vLLM's small-card settings.
From the model card
MiniCPM4 series are highly efficient large language models (LLMs) designed explicitly for end-side devices, which achieves this efficiency through systematic innovation in four key dimensions: model architecture, training data, training algorithms, and inference systems.
MiniCPM4-MCP is an open-source on-device LLM agent model jointly developed by THUNLP, Renmin University of China and ModelBest, built on MiniCPM-4 with 8 billion parameters. It is capable of solving a wide range of real-world tasks by interacting with various tool and data resources through MCP.
As of now, MiniCPM4-MCP supports the following:
Utilization of tools across 16 MCP servers: These servers span various categories, including office, lifestyle, communication, information, and work management.
Single-tool-calling capability: It can perform single- or multi-step tool calls using a single tool that complies with the MCP.
Cross-tool-calling capability: It can perform single- or multi-step tool calls using different tools that complies with the MCP.
The MCP Servers supported by MiniCPM4-MCP include Airbnb, Amap-Maps, Arxiv-MCP-Server, Calculator, Computer-Control-MCP, Desktop-commander, Filesystem, Github, Gaode, MCP-Code-Executor, MCP-DOCx, PPT, PPTx, Simple-Time-Server, Slack, and Whisper. Follow the instructions provided in each server's repository for successful deployment. Note that not all tools in these servers will function properly in every environment. Some tools are unstable and may return errors such as timeouts or HTTP errors. During training data construction, tools with consistently high failure rates (e.g., those for which the LLM fails to produce a successful query even after hundreds of attempts) are filtered out.
We modified the existing MCP Client from the mcp-cli repository to enable interaction between MiniCPM and MCP Servers.
After the MCP Client performs a handshake with a Server, it retrieves a list of available tools. An example of tool information contained in this list is provided in available_tool_example.json.
Once the available tools and user query are obtained, results can be generated using the following script logic:
python generate_example.py \
--tokenizer_path {path to MiniCPM4 tokenizer} \
--base_url {vllm deployment URL} \
--model {model name used in vllm deployment} \
--output_path {path to save results}
where the generate_example.py is located in link and MiniCPM4 gen
Quoted from the model card on Hugging Face. The full card is behind the Hugging Face link above.