Get Started

Integrations

Connect MCP servers to desktop clients and local agent runtimes.

Integration model

Each project is standalone-first. You can run Memory-only, Vision-only, or Codebase-only. Combined operation is optional through MCP.

Auto-merge clients

Installer scripts can merge supported local config for:

Claude Desktop
Claude Code

Find MCP config on desktop after install

If you installed successfully but cannot find where MCP was written, use these checks:

Locate MCP config files

Run the channel that matches your platform.

find "$HOME" -maxdepth 5 \( -name "*mcp*.json" -o -name "claude_desktop_config.json" \) 2>/dev/null | head -n 60

Lists common MCP/desktop config files under your home directory.

After install behavior

If the installer reports merge success, restart the desktop client fully, then run one MCP tool call to confirm registration.

Manual MCP entry (other clients)

For Cursor, VS Code, Windsurf, Cline, Codex Desktop, and generic MCP clients:

MCP server entry

Add one server entry per runtime in your client config file.

{
"command": "/Users/<you>/.local/bin/agentic-vision-mcp",
"args": ["serve"]
}

Equivalent binaries:

agentic-memory-mcp
agentic-vision-mcp
acb-mcp

Validation checklist

Binary path validation

Run this before debugging client-side connection issues.

which amem
which agentic-vision-mcp
which acb
which acb-mcp

Expected signal

[ok] /Users/<you>/.local/bin/amem
[ok] /Users/<you>/.local/bin/agentic-vision-mcp
[ok] /Users/<you>/.local/bin/acb
[ok] /Users/<you>/.local/bin/acb-mcp

After validation

Restart the target desktop client and run a first tool call to confirm MCP wiring.

Safeguard MCP config

Backup MCP config before manual edits

Create a timestamped backup so you can roll back quickly.

mkdir -p "$HOME/.agentra-backups/mcp"
if [ -f "$HOME/.claude/mcp.json" ]; then
  cp "$HOME/.claude/mcp.json" "$HOME/.agentra-backups/mcp/claude-mcp-$(date +%F-%H%M%S).json"
fi