Momento MCP Server

Momento MCP Server

What is Momento MCP Server about?

Provides a Model Context Protocol (MCP) server that connects to Momento Cache, exposing commands to retrieve, store, list, create, and delete caches.

How to use Momento MCP Server?

1. Obtain a Momento API key (super‑user key required for list‑caches, create‑cache, delete‑cache).\n2. Set environment variables:

   export MOMENTO_API_KEY="your-api-key"
   export MOMENTO_CACHE_NAME="your-cache-name"   # optional
   export DEFAULT_TTL_SECONDS=60                # optional
   

2. Run the server via npx (recommended) with MCP Inspector or any MCP‑compatible client:

   npx -y @modelcontextprotocol/inspector npx @gomomento/mcp-momento@latest
   

   or configure in a client JSON:

   {
     "mcpServers": {
       "momento": {
         "command": "npx",
         "args": ["-y", "@gomomento/mcp-momento"],
         "env": {
           "MOMENTO_API_KEY": "your-api-key",
           "MOMENTO_CACHE_NAME": "your-cache-name",
           "DEFAULT_TTL_SECONDS": 60
         }
       }
     }
   }
   

Key features

• get – Retrieve a value by key, with optional cache name.\n- set – Store a value with optional TTL and cache name.\n- list‑caches – Return all cache names in the Momento account.\n- create‑cache / delete‑cache – Manage cache lifecycle.\n- Works as an npm package (@gomomento/mcp-momento).\n- Compatible with MCP Inspector, Claude Desktop, and other MCP clients.\n- Configurable default cache name and TTL via environment variables.

Use cases

• Integrate caching directly into AI model workflows that use MCP.\n- Rapid prototyping of cache operations during development.\n- Automated cache management in CI/CD pipelines.\n- Providing a lightweight cache layer for micro‑services without needing a custom server.

FAQ

Q: Do I need a super‑user API key?\nA: Yes, a super‑user key is required for control‑plane commands (list‑caches, create‑cache, delete‑cache).
Q: What defaults are used if I don’t set environment variables?\nA: The server defaults to cache name mcp-momento and TTL of 60 seconds.
Q: Can I run the server without MCP Inspector?\nA: Yes, you can invoke the packaged server directly with npx @gomomento/mcp-momento and connect any MCP‑compatible client.

Momento MCP Server

A simple Model Context Protocol (MCP) server implementation for Momento Cache.

Available on npmjs as @gomomento/mcp-momento

Tools

• get
  • Get the cache value stored for the given key.
  • Inputs:
    • key string -- the key to look up in the cache.
    • cacheName string -- the name cache where the key presides (optional)
  • Returns:
    • Hit with the found value if the key was found.
    • Miss if the key was not found.
    • Error if the request failed.
• set
  • Sets the value in cache with a given Time To Live (TTL) seconds. If a value for this key is already present, it will be replaced by the new value regardless of the previous value's data type.
  • Inputs:
    • key: string -- the key to set in the cache
    • value: string -- the value to set for the given key
    • ttl: integer -- the number of seconds to keep this value in the cache (optional)
    • cacheName: string -- the name of the cache to store the key in (optional)
  • Returns:
    • Success if the key was successfully written to the cache.
    • Error if the request failed.
• list-caches
  • Lists the names of all the caches in your Momento account.
  • Inputs:
    • (none)
  • Returns:
    • Success with a comma separated list of cache names
    • Error if the request failed
• create-cache
  • Creates a new cache in your Momento account
  • Inputs:
    • name: string - the name of the cache to create
  • Returns:
    • Success if the cache was successfully created
    • Error if the request failed
• delete-cache
  • Deletes a cache from your Momento account
  • Inputs:
    • name: string - the name of the cache to delete
  • Returns:
    • Success if the cache was successfully deleted
    • Error if the request failed

Quickstart

1. Get a Momento API key from the Momento Console. Note - to run control plane tools (list-caches, create-cache, delete-cache), you must use a super user API key.

2. Set environment variables to configure the cache name and Time To Live (TTL) for items in the cache.

   # required
   export MOMENTO_API_KEY="your-api-key"
   
   # optional
   export MOMENTO_CACHE_NAME="your-cache-name"
   export DEFAULT_TTL_SECONDS=60
   

If you do not set these values, it will use mcp-momento as the cache name and 60 seconds for the default time to live.

Usage with MCP Inspector

npx -y @modelcontextprotocol/inspector npx @gomomento/mcp-momento@latest

Usage with NPX on Claude Desktop

Note: if you're using nodenv, replace the plain npx with the path to your npx binary (e.g. /Users/username/.nodenv/shims/npx).

{
  "mcpServers": {
    "momento": {
      "command": "npx",
      "args": [
        "-y",
        "@gomomento/mcp-momento"
      ],
      "env": {
        "MOMENTO_API_KEY": "your-api-key",
        "MOMENTO_CACHE_NAME": "your-cache-name",
        "DEFAULT_TTL_SECONDS": 60
      }
    }
  }
}

Setup for local development

1. Install dependencies:

   npm install
   

2. Build the server:

   npm run build
   

3. Run with MCP Inspector

   export MOMENTO_API_KEY="your-api-key"
   npx @modelcontextprotocol/inspector node dist/index.js