Documentation

Quick Start

{
  "mcpServers": {
    "memexa": {
      "command": "npx",
      "args": ["-y", "@memexa/mcp-server"],
      "env": {
        "MEMEXA_API_KEY": "your-api-key-here"
      }
    }
  }
}

Installation

{
  "mcpServers": {
    "memexa": {
      "command": "npx",
      "args": ["-y", "@memexa/mcp-server"],
      "env": {
        "MEMEXA_API_KEY": "memexa_..."
      }
    }
  }
}

{
  "name": "memexa",
  "command": "npx",
  "args": ["-y", "@memexa/mcp-server"],
  "env": {
    "MEMEXA_API_KEY": "memexa_..."
  }
}

Configuration

MCP Tools

Memexa exposes the following tools to your AI agent via the Model Context Protocol:

get_context

Load the full project context at the beginning of each session. This is the foundational tool that gives your AI agent access to all project knowledge.

{
  "task_hint": "Implementing user authentication",
  "max_tokens": 12000
}

update_context

Update the project context at the end of a session with all changes made. This is how your work gets saved for future sessions.

{
  "decisions": [
    {
      "decision": "Use JWT for authentication",
      "context": "Stateless auth needed for microservices",
      "alternatives": ["Session-based auth", "OAuth only"]
    }
  ],
  "bugs": [
    {
      "description": "API returns 500 on empty body",
      "cause": "Missing null check",
      "solution": "Added validation middleware"
    }
  ],
  "progress": {
    "completed_tasks": ["Setup auth routes", "Add JWT middleware"],
    "current_task": "Implement refresh token logic",
    "blockers": []
  },
  "files_changed": ["src/auth/routes.ts", "src/middleware/auth.ts"]
}

search_memory

Perform semantic search across all project history to find relevant decisions, bugs, conventions, or progress updates.

{
  "query": "How did we handle rate limiting?",
  "type": "decision",
  "limit": 5
}

compare_sessions

Compare the current project state with a previous session to see what has changed over time.

{
  "n": 3
}

add_decision

Record an important technical or architectural decision for future reference. Helps maintain consistency across sessions.

{
  "decision": "Use JWT for authentication",
  "context": "Stateless authentication better suits our microservices architecture and allows for horizontal scaling",
  "alternatives": [
    "Session-based authentication with Redis",
    "OAuth-only authentication"
  ]
}

log_bug

Log a bug encountered during development along with its cause and solution. Prevents repeating the same mistakes in future sessions.

{
  "description": "API returns 500 error when request body is empty",
  "cause": "Missing null check in request parser middleware",
  "solution": "Added validation middleware to check for empty bodies before parsing",
  "file": "src/api/middleware/parser.ts"
}

get_project_status

Get a quick summary of the current project status including recent activity, progress, and key metrics.

{}

validate_context

Analyze the project context for coherence, consistency, and potential issues. Useful for detecting conflicting decisions or outdated information.

{}

Context Files

Memexa structures your project memory into three specialized files:

Snapshots

Memexa automatically creates snapshots at the end of each session. Snapshots capture:

• Complete state of all three context files
• Session metadata (agent used, timestamp)
• Summary of changes made during the session

View and manage snapshots in the dashboard.

Rollback

Made a mistake? Rollback to any previous snapshot to restore your project context:

1. Go to your project's History page in the dashboard
2. Select the session you want to restore
3. Preview the changes that will be reverted
4. Confirm the rollback