Claude Code CLI

1-Line Terminal Add

One-Line Terminal MCP Setup & Dynamic CLAUDE.md Generation for Claude Code

The Challenge Without Meto

Claude Code runs in your terminal and executes multi-step refactoring, but forgets project architectural rules unless explicitly told in CLAUDE.md.

The Meto Solution

Add Meto as an MCP server to Claude Code with one command, or compile CLAUDE.md automatically with 'npx meto-cli sync'.

Key Advantages with Claude Code CLI

One-line installation via 'claude mcp add'

Dynamic querying of architectural decisions (ADRs) during CLI execution

Zero prompt duplication across terminal CLI and desktop IDE

Keeps CLAUDE.md synchronized with .cursor/rules/*.mdc

Step-by-Step Configuration Guide

Add Meto via Claude CLI

Run the single-line command in your terminal to register Meto as an MCP server.

Verify Connected Tools

Launch Claude Code ('claude') and verify that Meto's context and memory tools are listed.

Terminal

claude
# Inside Claude: /mcp

Terminal

claude mcp add meto -- npx -y mcp-remote https://www.metoctx.com/api/mcp/your-username --header "Authorization: Bearer meto_mcp_your_personal_token"

Frequently Asked Questions

How does Claude Code access Meto tools?

Claude Code communicates with Meto over Model Context Protocol using mcp-remote. When Claude needs architectural context, it calls Meto's tools automatically.

Can I use Meto with both Claude Code CLI and Claude Desktop?

Yes! Meto supports both. Claude Desktop uses claude_desktop_config.json while Claude Code CLI uses 'claude mcp add'.

Ready to give Claude Code CLI persistent memory?

Create your Meto profile in 2 minutes. Fill in your stack once, and never repeat your setup again.

Get Started for Free All Integrations