Summary
A cache you can poke at while debugging.
Reading a key and seeing Hit or Miss is the fastest way to settle whether a caching problem is the cache or the code around it — and the same server will spin up a throwaway cache to test against.
What it is
Momento's own MCP server for Momento Cache. The data-plane calls read and write keys with a TTL; the control-plane calls that list, create and delete caches require a super user API key.
What you get
- A key read back, returning Hit with the value, or Miss
- A key written with a per-call TTL in seconds, replacing whatever was there
- The caches on your account, listed
- A cache created, and a cache deleted
Requirements
A Momento API key in MOMENTO_API_KEY. Listing, creating and deleting caches need a super user key. MOMENTO_CACHE_NAME and DEFAULT_TTL_SECONDS are optional and fall back to mcp-momento and 60 seconds.
Setup effort
One command plus a key — npx -y @gomomento/mcp-momento, then supply credentials