A

Amicus MCP Server

A state persistence layer that enables seamless handoffs between different AI coding assistants by m...

30 views
0 installs
Updated Feb 8, 2026
Not audited
Tools I Recommend
A state persistence layer that enables seamless handoffs between different AI coding assistants by maintaining a shared context bus. It provides tools for tracking summaries, next steps, and active files to ensure continuity across development sessions.
  1. Click the "Install Now" button to open the FastMCP connection / installer interface.
  2. In the FastMCP connection interface find the "Environment Variables" (ENV) or "Add ENV" section. This is where you will add key/value pairs for the Amicus MCP server.
  3. Add the primary environment variable required by Amicus:
    • Key: CONTEXT_BUS_DIR
    • Value: the absolute path to the project context directory (the directory that will contain state.json). Examples:
      • macOS / Linux: /Users/you/path/to/project/.ai
      • Windows: C:\Users\you\path\to\project.ai
    • If you prefer Amicus to use the workspace default, leave CONTEXT_BUS_DIR blank (Amicus will use /.ai/state.json).
  4. Save / apply the ENV entries in the FastMCP interface and finish the install flow in that UI (the same Install Now workflow).
  5. Initialize or create the context directory locally (if it doesn’t already exist):
    • Open a terminal, cd to your project root, then run:
      • amicus-mcp --init
    • Or create manually: mkdir .ai (ensure correct ownership/permissions).
  6. Verify the ENV was applied and Amicus can access the context bus:
    • Run: amicus-mcp --validate-env
    • Check state visibility: amicus-mcp --show-state
      These commands will confirm CONTEXT_BUS_DIR is set (or that the default .ai directory is being used) and that state.json is accessible.
  7. If you get permission or path errors:
    • Ensure the path you supplied is absolute and writable by the user running the MCP server.
    • On Linux/macOS, check permissions (chown / chmod) so the MCP process can read/write the directory.
  8. Optional: after install, use amicus-mcp --list-tools and amicus-mcp --help to confirm the MCP is installed and tooling is available.

Quick Start

View on GitHub

More for Memory Management

View All →

More for Developer Tools

View All →

Similar MCP Servers

Report Issue

Thank you! Your issue report has been submitted successfully.