magus v0.3.0 is out. See what's new
¶ View markdown source · ✎ Suggest an edit

MGS9004: no auth token configured

A command needed the operator (cli) token - the built-in credential the local CLI and daemon authenticate with - but none has been created yet.

[MGS9004] no token configured; run `magus config mcp token generate`
  see: .../MGS9004.md

Why

The operator token is auto-seeded the first time the daemon starts. Before that (a fresh install where the daemon has never run), there is nothing to print or authenticate with.

Resolution

Either start the daemon once (it mints the token), or generate it explicitly:

magus config mcp token generate

Then re-run your command.

What this is NOT

  • Not a connector-token problem. Connector tokens (for MCP clients) are a separate store; this is the built-in operator credential. See MGS9001 for a rejected connector token.

See also

  • magus config mcp token: print or generate the operator token.
  • magus server start: starts the daemon, which seeds the token.
MGS9004authtokenclioperatoronboarding
Last updated (b022d75e)
Glossary

Daemon

The background magus host that owns shared state such as services and the warm knowledge graph. See daemon.

CI

An ordinary magusfile-defined target you compose yourself with magus\needs - magus does not hardcode its stages. Magus.RunCI treats it specially only in that it strips the rw charm, it is the anchor magus affected ci keys off, and a selected scope with no project declaring it is a load error rather than a silent no-op. See targets.

Conventions

This page uses none of the site's convention markers. The full set is on the conventions page.