---
title: "Maestro vanished in another repository"
description: "Maestro works in one folder and is missing in every other. This is an install-scope problem, and it has a one-line fix."
canonical: "https://help.sitesmojo.com/kb/troubleshooting/maestro-not-in-this-repo/"
---

Symptom: Maestro's tools are there in the project where you set it up, and gone
everywhere else. Nothing is broken — the server was filed under one directory.

## The cause

`claude mcp add` defaults to `--scope local`, which registers the server for
**the current directory only**. Open Claude Code anywhere else and there is no
Maestro, because as far as that session is concerned it was never installed.

## The fix

Re-add it with user scope:

```bash
claude mcp add --scope user --transport http maestro <url> --header "Authorization: Bearer <key>"
```

Then restart Claude Code. Configuration is read at session start, so the current
session will not see the change.

The portal's **Connect Claude** dialog already emits the `--scope user` form —
this problem generally comes from a command typed by hand, or from an older
snippet.

## Getting the URL and key right

Both come from the same place: the user-chip menu in the portal →
**Connect Claude** → the Claude Code tab. The **Advanced** tab there carries the
bare terminal command if you would rather paste that than let Claude run it.

Do not run `verify()` to obtain a fresh key for this. It rotates the key and
breaks the install that *was* working. Re-show the existing key instead — see
[whoami() fails](../whoami-fails/).

## Checking which scope you are on

`claude mcp list` reports the servers a session can see. Run it in the folder
where Maestro works and in one where it does not: a server that appears in the
first and not the second is scoped local. There is no harm in adding it at user
scope on top — the user-scoped entry is what other directories will find.