Support & Troubleshooting

Cursor Composer does not show Meto tools, or Cursor Settings → Features → MCP displays a red/orange dot with 'timeout after 10000ms'.

• 1.Ensure Node.js 18+ is available on your system PATH (`node -v`).
• 2.Check your user or workspace MCP configuration file (`~/.cursor/mcp.json` or `.cursor/mcp.json`).
• 3.If running inside WSL2 or a remote container, ensure npx is installed inside the Linux distro rather than executing Windows npx.exe.
• 4.Run the automated setup command to re-link and verify your MCP configuration.

// ~/.cursor/mcp.json
{
  "mcpServers": {
    "meto": {
      "command": "npx",
      "args": ["-y", "@metoai/mcp-server"]
    }
  }
}

Claude Code terminal assistant doesn't recall project stack or fails to query Meto memory tools during terminal coding sessions.

• 1.For Claude Code CLI, add the Meto MCP server in one command: `claude mcp add meto npx @metoai/mcp-server`.
• 2.Inside Claude Code, run `/mcp` to inspect connected servers and verify 'meto' is listed as Connected.
• 3.For Claude Desktop app, edit the configuration file at `~/Library/Application Support/Claude/claude_desktop_config.json` (macOS) or `%APPDATA%\Claude\claude_desktop_config.json` (Windows).

claude mcp add meto npx @metoai/mcp-server

Cascade agent does not discover tools from Meto server or reports 'MCP server failed to spawn'.

• 1.Open your Windsurf MCP configuration file located at `~/.codeium/windsurf/mcp_config.json`.
• 2.Add the Meto MCP server entry with command `npx` and args `["-y", "@metoai/mcp-server"]`.
• 3.Restart Windsurf completely to reload the Cascade agent's MCP process pool.

// ~/.codeium/windsurf/mcp_config.json
{
  "mcpServers": {
    "meto": {
      "command": "npx",
      "args": ["-y", "@metoai/mcp-server"]
    }
  }
}

Understanding how .cursorrules, CLAUDE.md, .windsurfrules, and GEMINI.md are updated, or preserving custom manual edits.

• 1.Hierarchy: Local Repository Directives take top precedence over Team ADRs, which override Global Directives.
• 2.Preserving custom sections: You can protect manual file blocks by surrounding them with `<!-- meto:keep-start -->` and `<!-- meto:keep-end -->`.
• 3.To inspect the exact merged rules for your active repository, run `npx @metoai/cli health` in your project root.

<!-- meto:keep-start -->
# Custom Project Rules
- Always use bun for testing
<!-- meto:keep-end -->

After 20+ messages in Cursor or Claude, the AI starts hallucinating, ignoring architectural rules, or degrading in quality.

• 1.LLM attention naturally degrades as chat windows swell with noisy terminal output and past conversation turns.
• 2.Meto is designed for context wiping: You can safely reset or clear your chat thread at any moment.
• 3.On the very first prompt in your fresh thread, the AI queries Meto's live MCP tools to restore verified tech stack rules without prompt re-typing.

Verifying whether Meto accesses, scans, clones, or stores your private source code repository.

• 1.Meto strictly stores developer directives, coding preferences, architectural decision records (ADRs), and your public context profile.
• 2.Meto never clones, scans, uploads, or stores your private source code repository files.
• 3.All MCP tools query metadata and directives locally or through encrypted HTTPS endpoints with zero repository telemetry.