Mcp Momento

What is Mcp Momento about?

Mcp Momento implements a Model Context Protocol (MCP) server for Momento Cache, exposing cache primitives (get, set) and control‑plane commands (list‑caches, create‑cache, delete‑cache) through a lightweight Node.js process.

How to use Mcp Momento?

1. Obtain a Momento API key from the Momento Console (super‑user key required for control‑plane tools).
2. Set environment variables:

   export MOMENTO_API_KEY="your-api-key"
   export MOMENTO_CACHE_NAME="your-cache-name"   # optional, defaults to "mcp-momento"
   export DEFAULT_TTL_SECONDS=60                # optional, defaults to 60
   

3. Run the server with MCP Inspector (or any MCP‑compatible client):

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

   Or use the JSON configuration format for tools like Claude Desktop.

Key features of Mcp Momento

• Cache retrieval (get): returns Hit, Miss, or Error.
• Cache storage (set): writes a string value with optional TTL.
• Control‑plane utilities:
  • list-caches – list all caches in the account.
  • create-cache – create a new cache.
  • delete-cache – delete an existing cache.
• Zero‑config defaults fallback to a cache named mcp-momento with a 60‑second TTL.
• Available as an npm package (@gomomento/mcp-momento) and works out‑of‑the‑box with npx.

Use cases of Mcp Momento

• Rapid prototyping of AI agents that need temporary memory via a standardized protocol.
• Integration testing where a lightweight cache server is required without managing external services.
• Serverless functions that need fast key‑value storage backed by Momento’s managed infrastructure.
• Educational demos of Model Context Protocol interactions.

FAQ from the Mcp Momento

Q: Do I need a super‑user API key for all commands? A: Only the control‑plane commands (list-caches, create-cache, delete-cache) require a super‑user key. get and set work with regular cache keys.

Q: What data types are supported? A: Keys and values are plain strings. Binary data must be base64‑encoded before storage.

Q: How is TTL handled? A: If a TTL is supplied to set, the entry expires after the specified number of seconds. Otherwise the default TTL (DEFAULT_TTL_SECONDS) is used.

Q: Can I run the server without building from source? A: Yes. The pre‑built package can be launched directly via npx as shown above.

Q: Is there a way to customize the cache name at runtime? A: Set the MOMENTO_CACHE_NAME environment variable before starting the server.

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