memax mcp

Start and manage the Memax MCP server. Gives tool-calling agents direct access to recall, push, and search.

Start a local MCP (Model Context Protocol) server that gives tool-calling agents direct access to your Memax hub.

Usage

memax mcp serve

This starts a stdio-based MCP server that exposes Memax tools to any MCP-compatible client.

Most agents configure MCP via a JSON config file:

{
  "mcpServers": {
    "memax": {
      "command": "npx",
      "args": ["-y", "memax-cli", "mcp", "serve"]
    }
  }
}

For agent-specific setup, see the Integrations guide.

The MCP server exposes 7 tools:

Semantic search for relevant memories.

Parameter	Type	Required	Description
`query`	string	Yes	Search query
`hint`	string	No	Additional context for ranking
`project_context`	object	No	Repo, branch, project info
`limit`	number	No	Max results (default: 5)

Store new knowledge.

Parameter	Type	Required	Description
`content`	string	Yes	Content to store
`title`	string	No	Title (auto-generated if omitted)
`category`	string	No	Category override
`tags`	string[]	No	Tags
`boundary`	string	No	`private`, `team`, `public`
`hub_reason`	string	No	Reason for pushing to team hub

Browse memories by metadata.

Parameter	Type	Required	Description
`category`	string	No	Filter by category
`tags`	string[]	No	Filter by tags
`limit`	number	No	Max results

Retrieve a specific memory by ID.

Parameter	Type	Required	Description
`id`	string	Yes	Memory ID

Delete a memory.

Parameter	Type	Required	Description
`id`	string	Yes	Memory ID to delete

Capture and store content from a URL.

Parameter	Type	Required	Description
`url`	string	Yes	URL to capture
`snapshot`	boolean	No	Capture full content

List knowledge topics.

Parameter	Type	Required	Description
`hub_id`	string	No	Scope to a specific hub

The CLI MCP server and the remote MCP server (api.memaxlabs.com/mcp) expose identical tools. Use whichever fits your setup.