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

MGS9006: connector token not found

magus config mcp connector revoke (or a lookup) named a connector token - by name or fingerprint - that the store does not contain.

[MGS9006] magus config mcp connector revoke: no connector matches "ci"
  see: .../MGS9006.md

Why

Revoke resolves the token you named against the store. Nothing matched: the name or fingerprint is wrong, it was already revoked, or it belongs to a different daemon's store.

Resolution

List what is actually there and revoke by an exact name or fingerprint from the list:

magus config mcp connector ls
magus config mcp connector revoke <name-or-fingerprint>

A fingerprint prefix works if it is unambiguous; if it matches more than one token, magus asks you to disambiguate rather than guess.

What this is NOT

  • Not the operator token. The built-in cli token is not in the connector store and is never a revoke target here.

See also

  • magus config mcp connector ls: the tokens you can revoke.
MGS9006authconnectortokenrevokefingerprint
Last updated (b529b75f)
Earlier changes on this page (1)

Full history ↗ · Blame source ↗

Glossary

Target

A named operation (build, test, ...) you invoke with magus run <target>; it may compose a spell's tool-native operations and depend on other targets. See targets.

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.