head to head · open source
vllm vs mcp-memory-service
vllm has 96,158 GitHub stars, 24,317 forks, 7,953 open issues and last shipped yesterday. mcp-memory-service has 2,062 stars, 383 forks, 30 open issues and last shipped yesterday. vllm leads on adoption by 4,563% (96,158 vs 2,062 stars). vllm is written in Python under Apache-2.0; mcp-memory-service is written in Python under Apache-2.0. vllm has attracted 25% as many forks as stars, mcp-memory-service 19%. vllm was the more recently maintained of the two, and both are self-hostable with no licence fee.
Two open source projects, one decision. Both are free and self-hostable — the differences are community size, license terms, language stack and release pace.
← all 20902 open source comparisons
Side by side
| vllm | mcp-memory-service | |
|---|---|---|
| GitHub stars | ★ 96K | ★ 2.1K |
| License | Apache-2.0 | Apache-2.0 |
| Written in | Python | Python |
| Last push | 2026-11-02 | 2026-11-02 |
| Forks | ⑂ 24K | ⑂ 383 |
| Self-hosting | Yes | Yes |
| Data ownership | Your server | Your server |
pick vllm if
- You weight community size — 96K stars and counting
- You want the Apache-2.0 license terms
- Your stack matches Python
- You value the larger contributor base for long-term maintenance
pick mcp-memory-service if
- You want the mcp-memory-service feature set and don't need the biggest community
- You prefer the Apache-2.0 license terms
- Your stack matches Python
- You evaluated both and mcp-memory-service fits your workflow better
About vllm
Easy, fast, and cheap LLM serving for everyone 🔥 We have built a vLLM website to help you get started with vLLM. Please visit vllm.ai to learn more. For events, please visit vllm.ai/events to join us. About vLLM is a fast and easy to use library for LLM inference and serving. Originally developed in the Sky Computing Lab at UC Berkeley, vLLM has grown into one of the most active open source AI projects built and maintained by a diverse community of many dozens of academic institutions and companies from over 2000 contributors. vLLM is fast with: State of the art serving throughput Efficient management of…
About mcp-memory-service
This repository has moved to GitHub Active development, issues, pull requests, CI and releases are at as of 5 September 2026. This copy stays here, readable and unchanged, so that existing links, issue numbers and pull request references keep resolving. It receives no further pushes and its CI no longer runs. Please do not open issues or pull requests here, they will not be seen. The wiki moved too: mcp memory service Persistent Shared Memory for AI Agent Pipelines Open source memory backend for AI agents — REST API, MCP, OAuth, CLI, dashboard . One self hosted service, every transport. Agents store decisions…
read the full mcp-memory-service overview →
More in AI & Machine Learning
Related comparisons
More Machine Learning Infrastructure projects
Compare either of these against the rest of the Machine Learning Infrastructure field.
Frequently asked questions
Is vllm or mcp-memory-service more popular?
vllm has 96,158 GitHub stars and mcp-memory-service has 2,062. vllm has the larger community by that measure.
Are vllm and mcp-memory-service free?
Both are open source. vllm is licensed under Apache-2.0 and mcp-memory-service under Apache-2.0. Neither carries a licence fee.
What is the difference between vllm and mcp-memory-service?
vllm is written in Python and mcp-memory-service in Python. The practical differences are community size, licence terms, language stack and release cadence — all compared in the table above.
Which should I choose, vllm or mcp-memory-service?
Choose vllm if you want the larger community (96,158 stars) or its Apache-2.0 licence terms. Choose mcp-memory-service if its feature set, stack or Apache-2.0 licence fits better. Both are self-hostable.