memaxdocs
Integrations

Other Agents

Connect Copilot, Windsurf, or any custom agent to Memax using MCP or CLI piping.

Memax is agent-agnostic. Any agent that supports MCP or can read from stdin/stdout works with Memax.

MCP-compatible agents

Any agent that supports the Model Context Protocol can use Memax's MCP server:

npx memax-cli mcp serve

This starts a stdio-based MCP server. Configure your agent to run this command as an MCP server, similar to the Claude Code and Cursor guides.

Windsurf

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

CLI piping (universal)

For agents that don't support MCP, CLI piping is the universal fallback:

# Recall context and pipe it into your workflow
memax recall "how does deployment work?" --quiet

# Use in scripts
CONTEXT=$(memax recall "coding conventions" --quiet)

# Copy to clipboard
memax recall "auth design" | pbcopy

SDK embedding

For custom agents, use the TypeScript SDK:

import { MemaxClient } from "memax-sdk";

const memax = new MemaxClient({ apiKey: process.env.MEMAX_API_KEY });

// Recall relevant context
const results = await memax.recall("how does auth work?");

// Push new knowledge
await memax.push({
  content: "We decided to use JWT for stateless auth",
  category: "decisions",
});

Memax is designed to work with any agent. If your agent can read text input, it can use Memax context. CLI piping is the universal integration method.