Fovea Memory MCP
Click on "Install Server".
Wait a few minutes for the server to deploy. Once ready, it will show a "Started" state.
In the chat, type
@followed by the MCP server name and your instructions, e.g., "@Fovea Memory MCPSearch my memories for 'project update'"
That's it! The server will respond to your query, and you can continue using it as needed.
Here is a step-by-step guide with screenshots.
Fovea Memory MCP
Fovea Memory MCP is a local stdio MCP server that lets AI clients read memories created by the Fovea macOS app.
It runs on your Mac, reads the local Fovea Memory SQLite database, and exposes only memories marked visible to MCP. It does not upload your memory database to Fovea, GitHub, npm, or any third-party service.
Install
Use this configuration in any MCP client that supports local stdio servers:
{
"mcpServers": {
"fovea-memory": {
"command": "npx",
"args": ["-y", "fovea-memory-mcp@1"]
}
}
}The equivalent command is:
npx -y fovea-memory-mcp@1No environment variables are required for normal use. The server discovers the current Fovea namespace through:
~/Library/Application Support/Fovea/current-namespace.jsonRelated MCP server: mcp-context
Requirements
macOS with Fovea installed and run at least once
Node.js 22.5 or newer
A local Fovea Memory database with memories visible to MCP
An MCP client that supports local stdio servers
Client Examples
Claude Code
claude mcp add fovea-memory -- npx -y fovea-memory-mcp@1Codex
codex mcp add fovea-memory -- npx -y fovea-memory-mcp@1Claude Desktop, Cursor, VS Code, and Other Clients
Use the standard local server configuration:
{
"mcpServers": {
"fovea-memory": {
"command": "npx",
"args": ["-y", "fovea-memory-mcp@1"]
}
}
}Some clients use a different top-level key, such as servers instead of mcpServers. Keep the server command and args the same.
Tools
The server exposes these MCP tools:
recall_recent_fovea_memory: recall what the user recently saw, asked, or said through Fovealist_recent_fovea_memories: list recent visible Fovea memoriessearch_fovea_memory: search visible Fovea memories by keyword, with optional semantic search when configuredforget_fovea_memory: soft-delete a memory from the local recent store
Privacy Model
Local stdio process only
Reads the local Fovea Memory SQLite database
Returns only active memories with
mcp_visibility='visible'Soft delete uses local SQLite status updates
Writes best-effort local audit events to
audit.sqliteDoes not send memory data to GitHub or npm
Semantic search is optional. If FOVEA_BACKEND_URL and FOVEA_AUTH_TOKEN are set, the server can request an embedding for the search query. If they are not set, search automatically falls back to local keyword matching.
Development
npm testThe test suite creates a synthetic SQLite database at runtime. It does not require private Fovea fixtures.
License
Apache-2.0
This server cannot be installed
Maintenance
Resources
Unclaimed servers have limited discoverability.
Looking for Admin?
If you are the server author, to access and configure the admin panel.
Latest Blog Posts
MCP directory API
We provide all the information about MCP servers via our MCP API.
curl -X GET 'https://glama.ai/api/mcp/v1/servers/hellofovea/fovea-memory-mcp'
If you have feedback or need assistance with the MCP directory API, please join our Discord server