Krusch Context vs PayMCP
Side-by-side comparison of two Model Context Protocol servers. Pick the right one for Claude Desktop, Claude Code, or Cursor.
Gives IDE agents semantic codebase search, episodic project memory, and steering nuggets across sessions.
Comparison
| Feature | Krusch Context | PayMCP |
|---|---|---|
| Pricing | Free | Free |
| Installs | — | 2 |
| Rating | — | — |
| Verified | — | |
| Hosted | — | — |
| Tools | — | — |
| Category | development | development |
| Author | kruschdev | blustAI |
| Repo | kruschdev/krusch-context-mcp | blustAI/paymcp |
When to pick Krusch Context
Gives IDE agents semantic codebase search, episodic project memory, and steering nuggets across sessions.
When to pick PayMCP
Lightweight payments layer for MCP servers: turn tools into paid endpoints with a two-line decorator. [PyPI](https://pypi.org/project/paymcp/) · [npm](https://www.npmjs.com/package/paymcp) · [TS repo](https://github.com/blustAI/paymcp-ts)
Looking for something else? Browse all MCPs or check trending this week.