MCP Server
Configuration
Connect your MCP client to the hosted Litica server with one config block.
Before you start
- You have a Litica API key. If not, create an account.
- Node.js is installed on your machine (required for
npx).
All configs below use mcp-remote, a small bridge package that connects your MCP client to Litica's hosted server over HTTP. You do not need to install anything separately.npx handles it automatically.
Claude Desktop
Open your Claude Desktop config file and add the litica-memory entry undermcpServers. Replace lk_your-api-key with your actual key.
{
"mcpServers": {
"litica-memory": {
"command": "npx",
"args": [
"-y",
"mcp-remote",
"https://mcp.litica.org/mcp/",
"--header",
"X-API-Key:lk_your-api-key"
]
}
}
}Save the file and restart Claude Desktop. The memory tools will be available immediately.
Claude Code
Add a .mcp.json file to your project root, or add to your global Claude Code config at~/.claude/mcp.json.
{
"mcpServers": {
"litica-memory": {
"command": "npx",
"args": [
"-y",
"mcp-remote",
"https://mcp.litica.org/mcp/",
"--header",
"X-API-Key:lk_your-api-key"
]
}
}
}Cursor
Create or edit .cursor/mcp.json in your project root.
{
"mcpServers": {
"litica-memory": {
"command": "npx",
"args": [
"-y",
"mcp-remote",
"https://mcp.litica.org/mcp/",
"--header",
"X-API-Key:lk_your-api-key"
]
}
}
}Verify the connection
After restarting your client, ask your agent what memory tools it has access to. A working connection will show add_memory and search_memory in the tools list.
You can also test it directly: ask Claude to remember something, then start a new conversation and ask it to recall. If Litica is connected, it will retrieve the memory across sessions.
Security note
Your API key is passed in plain text in the config file. Do not commit config files containing your key to source control.