magus v0.4.3 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 server 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 server starts. Before that (a fresh install where the server has never run), there is nothing to print or authenticate with.

Resolution

Either start the server 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 server, which seeds the token.
AuthPages in this section. magus stdlibReference for every magus stdlib module - fs, os, http, json, yaml, crypto, and the rest of the magusfile API. The CLI in practiceThe magus subcommands you reach for most, grouped by the question you are asking, with the quirks that are not obvious from the help text. Knowledge-graph diagnosticsLanding page for MGS7xxx diagnostics that flag ambiguities the knowledge-graph extractor hits while building the deterministic graph, such as a buzz import that resolves to no file or a doc that cites an unregistered diagnostic code.
MGS9004authtokenclioperatoronboarding
Last updated (895d94e4)
Earlier changes on this page (4)

Full history ↗ · Blame source ↗

Glossary

Op

A single tool-native command a target composes (long form: operation); the middle of the work hierarchy (Spell to Op to Target). Op in full.

CI

An ordinary target you compose yourself with ctx.needs; magus does not hardcode its stages. It is the anchor magus affected ci keys off, and ci strips the rw charm. CI in full.

Run

One target executing under one magus invocation, such as magus run test web or magus affected ci. A run keeps its captured output behind an output reference. Every magus run is a run whether or not any job asked for it; see Job for how the two relate. Run in full.

Conventions

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