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

MGS9005: connector name already exists

magus config mcp connector create was asked to mint a token under a name that the connector store already has. Names are unique so each client's token is unambiguous to list and revoke.

[MGS9005] magus config mcp connector create: a connector named "ci" already
exists; pass a different --name
  see: .../MGS9005.md

Why

A connector name is the human handle for a token in list and revoke. Allowing two tokens with the same name would make it ambiguous which one an operator means to revoke - a footgun for a credential.

Resolution

  • Pick a different name:

    magus config mcp connector create --name ci-2
    
  • Or revoke the existing one first if you meant to replace it (there is no renew; replacing is revoke-then-mint):

    magus config mcp connector revoke ci
    magus config mcp connector create --name ci
    

See also

  • magus config mcp connector ls: the names already in use.
MGS9005authconnectortokencreatename
Last updated (b529b75f)
Earlier changes on this page (1)

Full history ↗ · Blame source ↗

Glossary

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.