The Pocket Agent MCP server
One server that hands your agent the brain as tools — memory, personas, privacy zones. Node or Python; pick the runtime you already have.
Node · npx
No install step. The first run pulls the package and starts the server on stdio. This is the command your client's MCP config invokes.
$ npx -y @pocketagent/mcpPython · uvx
Same server, Python runtime. Useful when your stack is already on uv and you'd rather not add Node.
$ uvx pocketagent-mcpAdd it to a client
Every MCP client takes the same shape: a command, its args, and the API key in the env. The quickstart has the exact file path for each one.
mcp config (any client)
{
"mcpServers": {
"pocketagent": {
"command": "npx",
"args": ["-y", "@pocketagent/mcp"],
"env": { "POCKETAGENT_API_KEY": "pa_live_…" }
}
}
}The tools it exposes
memory.writeStore a fact in a zone. Returns its id.memory.recallPull memories matching a query, newest first.persona.runSend a turn to a named persona and stream the reply.persona.listList the personas the key can reach.zone.checkAsk whether a piece of content is allowed in a zone before you send it.Privacy zones apply to MCP calls the same way they apply to the REST API: a tool can't read across a zone it wasn't scoped to. The boundary lives on the server, not in the prompt you send.