# argus-agent setup

> Talos next · Since next

Connect a person's own AI client to a project in one step: write the project's `.mcp.json` (what Claude Code reads) with this `argus-agent` as the `argus` server, keeping any other servers there.

## Usage

```sh
argus-agent setup [OPTIONS]
```

## Options

| Flag | Value | Default | Allowed values | Description |
|---|---|---|---|---|
| `--project` | `<PROJECT>` |  |  | The project folder (or its argus.project.json). The current folder when absent |
| `--print` |  |  |  | Print the config rather than writing it |
| `--tool-names` | `<TOOL_NAMES>` | `dotted` |  | How `tools/list` spells the names. `dotted` is the interface's own (`scene.read`); `underscore` is for a client that namespaces a tool into an identifier and will not take a dot (`scene__read`); `hyphen` for one that also takes no `__` inside a tool's name (Grok: `scene-read`). `tools/call` takes any spelling whichever this is |
| `--toolsets` | `<TOOLSETS>` | `""` |  | Toolsets to list from the start, beyond the core: comma-separated names, or `all`. For a client that does not refetch `tools/list` when told it changed; one that does can call `tools.enable` instead and pay for the tools only when it needs them. ARGUS_AGENT_TOOLSETS when absent, so a harness can set it for every server it starts |

## Example

```sh
argus-agent setup
```