magus v0.4.2 is out. See what's new
¶ View generated markdown
1 min read

magus-mcp

Print how to reach the MCP server

Synopsis

magus mcp

Description

MCP is not a standalone process: it is served by the daemon, alongside everything else magus server start hosts. This command prints what a client needs to reach it - the endpoint, the auth token command, and a liveness probe - and exits non-zero, since it starts nothing itself.

magus server start start the daemon (MCP comes up with it) magus config token print print the bearer token magus status --probe=liveness,mcp confirm the endpoint is serving

Per-client configuration lives in docs/guides/integrations/mcp.md, not in this binary: naming a client here would make a change to its config format a magus release.

Exit status

2
Always: mcp prints reach-it instructions and starts nothing, so the invocation is treated like any other command that named a retired verb.

See Also

magus(1), magus-ls(1), magus-describe(1), magus-run(1), magus-x(1), magus-where(1), magus-affected(1), magus-graph(1), magus-query(1), magus-explain(1), magus-path(1), magus-refs(1), magus-watch(1), magus-events(1), magus-status(1), magus-clean(1), magus-vcs(1), magus-doctor(1), magus-config(1), magus-session(1), magus-memory(1), magus-notes(1), magus-diff(1), magus-server(1), magus-buzz(1), magus-completion(1), magus-man(1), magus-init(1), magus-agent(1), magus-self(1), magus-version(1)

ManpagePages in this section. magus sessionOne family over the repository's session store: list what sessions ran, list the blocks agents raised, close one by hand, and take the host-hook ingest that writes it all. magus-runRun builds, tests, lints, and codegen through magus targets. ChangelogEvery released change to magus, newest first, in Keep a Changelog format. Generated from releases/*.yaml.
generatedinternal/cli/registry.goclimagus mcpmcpagentdaemon
Last updated (4f8cc295)
Glossary

Op

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

Buzz

The language magusfiles are written in (the .buzz engine). See engines.

Affected

The set of projects touched by a change; magus affected <target> runs a target only over them. See affected.

Daemon

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

MAGUS.md

The committed routing index at a workspace root, regenerated from the knowledge graph: it lists every node and points at the exact query for a given question, so it is the entry point an agent reads first. See knowledge.

Session

One magus process's recorded facts - the targets it finished, their outcomes, and the lease it acted as - kept in a repo-scoped store every worktree shares. magus session lists them; the store prunes itself by last-fact age.

Lease

One row of the lease ledger: a piece of work an orchestrating agent handed out, with its goal, the checkpoint it was cut against, and the paths it owns or must not touch. The ledger records; the agent guard is what reads those facts back when grading a write. See doctrine.

Conventions

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