> ## Documentation Index
> Fetch the complete documentation index at: https://docs.joystream.ai/llms.txt
> Use this file to discover all available pages before exploring further.

# jstm registry

> See the resolved catalog for a workspace, and find out which entry wins when names collide.

Catalog entries come from several tiers — system, org, workspace, and personal. When the same name exists at more than one tier, the most specific wins. The registry commands show you the resolved result rather than the raw sources.

## `registry list`

List the deduplicated, precedence-applied registry for a workspace.

```bash theme={null}
jstm registry list
jstm registry list --kind skill
jstm registry list --kind mcp --workspace acme-corp/finance --tier org
```

| Option              | Default          | Description                                                        |
| ------------------- | ---------------- | ------------------------------------------------------------------ |
| `--kind`, `-k`      | `mcp`            | Catalog kind: `mcp` or `skill`                                     |
| `--workspace`, `-w` | Active workspace | Workspace as UUID, handle, or FQN                                  |
| `--tier`            | all              | Filter by source tier: `system`, `org`, `workspace`, or `personal` |
| `--json`            | off              | Emit as JSON                                                       |

## `registry resolve`

Resolve one qualified name to its winning entry, and the reason it won.

```bash theme={null}
jstm registry resolve mcp github-mcp-server
jstm registry resolve skill google-calendar-read --workspace acme-corp/finance
```

| Argument or option  | Description                                  |
| ------------------- | -------------------------------------------- |
| `KIND`              | Required. `mcp` or `skill`                   |
| `NAME`              | Required. The qualified name to resolve      |
| `--workspace`, `-w` | Workspace. Defaults to your active workspace |
| `--json`            | Emit as JSON                                 |

Use this when an agent picks up a different server or skill than you expected. It names the tier the winner came from and what it beat.

## Why this matters

A team can override a shared server with their own version without affecting anyone else. That is useful, and it is also the reason a catalog entry sometimes isn't the one you thought. `registry resolve` is how you find out, rather than guessing from the raw catalog listings.

## See also

* [Skills and MCP servers](/concepts/skills-and-mcp) — scope and resolution.
* [`jstm mcp`](/cli/mcp) and [`jstm skills`](/cli/skills)