# Claude

{% embed url="<https://youtu.be/aViHPX-o6tM>" %}

## Install Metabob

To get started, you need to install the Metabob CLI tool. If you don't have access to it yet, please request it by contacting <axel@metabob.com>.

#### Step 1: Download the latest version of metabob-cli

Download the current Metabob CLI release for your operating system.

####

#### Step 2: Move metabob-cli into your system PATH

Place the file in a directory included in your PATH, or another convenient execution location.

Make sure that the file is executable.

####

#### Step 3: Make the CLI executable (not needed on Windows)

On Mac/Linux:

```
chmod +x metabob-cli

## change metabob-cli to whatever name it is stored with in your computer

```

On Windows: use cmd. Assuming you downloaded the file to the default folder\
%userprofile%\Downloads\x.exe

```
cd /d %userprofile%
md .local\bin
copy Downloads\x.exe %userprofile%\.local\bin\metabob-cli.exe
set PATH %userprofile%\.local\bin;%PATH%
setx PYTHONUTF8 1
set PYTHONUTF8 1
metabob-cli versione it
REM ensure that you see the expected version here
REM Settings, Environment Variables, Path, prepend %userprofile%\.local\bin
REM in cmd, please cd back to your project root folder
REM do not use setx with Path

```

<br>

#### Step 4: Add Metabob MCP to Claude Code

To add Metabob MCP to Claude Code, run the following command from your project root:

```
claude mcp add --transport stdio metabob --env 
METABOB_API_KEY=your_api_key_here -- metabob-cli mcp --transport stdio

```

#### Step 5: Validate that .metabob/ directory was created

After running the command in Step 4, a .metabob/ directory should be created in your project root directory. Please confirm that you can see the .metabob/ directory.

#### Step 6: Create config.json inside .metabob/

Create .metabob/config.json

Add the following configuration:<br>

```
{
 "api_key": "mb_your_metabob_api_key_here", 	
 "base_url": "https://ide.metabob.com",
 "state_directory": ".metabob",
 "session_path": null,
 "output_path": null,
 "include_paths": ["app/**/*.py"], ## <-- add paths to include in analysis here
 "exclude_paths": [ ## add paths to exclude from analysis here
   "**/.*/**",
   "**/node_modules/**",
   "**/__pycache__/**",
   "**/venv/**",
   "**/dist/**",
   "**/build/**",
   "**/target/**",
   "**/bin/**",
   "**/obj/**",
   "*.pyc"
 ]
}

```

#### Fields to update

* api\_key — paste your API key here
* include\_paths — directories Metabob should analyze
* exclude\_paths — directories Metabob should ignore

No other fields typically require modification.

#### &#x20;Step 7: Start Claude Code

Start Claude Code from your terminal.

#### Step 8: Validate that the Metabob MCP tool is active

On your Claude Code, run the command /mcp:

```
/mcp

```

If Metabob was successfully installed, you should see the following output:

![](/files/Veqijv5hM4Hag6LocWHV)

#### If metabob shows to not be connected, press enter and try to reconnect the MCP servers:

![](/files/LhOdtfO2OJoDtW3CGB9X)

\
To search for the cause, log files from Metabob are in the folder .metabob\
To see Claude’s logs, restart it as claude —-debug # double dash\
ls -lt $HOME/.claude/debug | head\
Look at the most recent file. For windows the folder is %userprofile%\\.claude\debug\\<br>

#### Step 9: Confirm Metabob state tracking

Metabob maintains a live state file inside your .metabob/ directory. This file will update along with your code changes

If you cannot get the Metabob MCP to work on Claude Code, please contact <axel@metabob.com>.


---

# Agent Instructions: Querying This Documentation

If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://metabob.gitbook.io/product-docs/configure/claude.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.