RELATED 01
Render MCP Server
OFFICIAL SERVERCreate, deploy and troubleshoot Render services, Postgres and Key Value from an AI client
194GitHub stars
40popularity score
Momento MCP Server
Read and write keys in Momento Cache and manage its caches from an MCP client
Official · momentohq TypeScript Local · stdio DatabasesCloud platforms
25 popularity score ★ 3 ↓ 17/wk
Connect your client
Local (npm)
Add in one click
Opens the app, which asks before it adds the server. Then replace each <NAME> in its settings with your value.
Or add it by command or config
It needs MOMENTO_API_KEY. Replace each <NAME> with your value.
Claude CodeTerminal
claude mcp add momento -e MOMENTO_API_KEY=<MOMENTO_API_KEY> -- npx -y @gomomento/mcp-momentoClaude Desktopclaude_desktop_config.json
{
"mcpServers": {
"momento": {
"command": "npx",
"args": [
"-y",
"@gomomento/mcp-momento"
],
"env": {
"MOMENTO_API_KEY": "<MOMENTO_API_KEY>"
}
}
}
}Cursor~/.cursor/mcp.json
{
"mcpServers": {
"momento": {
"command": "npx",
"args": [
"-y",
"@gomomento/mcp-momento"
],
"env": {
"MOMENTO_API_KEY": "<MOMENTO_API_KEY>"
}
}
}
}VS Code.vscode/mcp.json
{
"servers": {
"momento": {
"type": "stdio",
"command": "npx",
"args": [
"-y",
"@gomomento/mcp-momento"
],
"env": {
"MOMENTO_API_KEY": "<MOMENTO_API_KEY>"
}
}
}
}Codex~/.codex/config.toml
[mcp_servers.momento]
command = "npx"
args = ["-y", "@gomomento/mcp-momento"]
[mcp_servers.momento.env]
MOMENTO_API_KEY = "<MOMENTO_API_KEY>"Gemini CLITerminal
gemini mcp add --scope user -e MOMENTO_API_KEY=<MOMENTO_API_KEY> momento npx -- -y @gomomento/mcp-momentoSettings 3
MOMENTO_API_KEY |
Required: Momento API key from the Momento Console; a super user key is needed for the cache-management tools. |
|---|---|
MOMENTO_CACHE_NAME |
Optional: Cache used when a call names none; defaults to mcp-momento. |
DEFAULT_TTL_SECONDS |
Optional: Time to live for stored values when set gives none; defaults to 60. |
What it does
Momento MCP Server connects an MCP client to Momento Cache, Momento's hosted key-value cache service. It is published by momentohq, the company behind Momento, and runs locally as a Node.js process over stdio, talking to Momento's cloud API with your API key.
It offers two kinds of work. On the data side, an assistant can fetch the value stored under a key and store a string value under a key, with an optional time to live in seconds; a stored value replaces whatever was there before. On the control side, it can list the caches in the account, create a new cache and delete one.
A default cache name and default TTL come from environment variables; when they are unset the server uses a cache called mcp-momento and a 60-second TTL. Each get or set call may name a different cache instead.
What it needs
| Runtime | Node.js |
|---|
Node.js with npx, and a Momento account with an API key from the Momento Console passed as MOMENTO_API_KEY. The cache-management tools (list-caches, create-cache, delete-cache) need a super user API key.
Limits
Only five tools: plain string get and set plus cache list, create and delete. No key deletion, no listing of keys, and none of Momento's other data types or services. Values are strings and set always overwrites an existing value. The makers describe it as a simple implementation, and it is at version 0.1.x.
Who it suits
Suits developers already using Momento Cache who want an assistant to inspect or seed cache entries, or to set up and tear down caches during development. Since it is official but small, pick something else if you need richer data structures, key scanning or a self-hosted cache such as Redis. Give it a scoped, non-super-user key if you only want reads and writes of values, since delete-cache can remove a whole cache.
Tools 5
get- Fetch the value stored under a key, from the default or a named cache
set- Store a string value under a key, with an optional TTL in seconds and cache name
list-caches- Return the names of all caches in the Momento account
create-cache- Create a new cache with the given name
delete-cache- Delete the named cache from the account