CLI
l4 mcp status
Show which agent clients on this machine carry a LevelFour entry, what each one points at, and which credential l4 resolves.
l4 mcp status reports, per client, whether it is installed on this machine and whether it carries a LevelFour entry, and what the hosted server offers your credential. Run this first when an agent says it cannot see any LevelFour tools.
l4 mcp status [flags]Flags
| Flag | Description |
|---|---|
--name | Name of the server entry to look for. Defaults to levelfour |
--endpoint | MCP endpoint to check. Defaults to the hosted server |
Global flags (--json, --jq, --template, --quiet, --token, --api) apply. See CLI overview.
Output
LevelFour MCP
Entry name: levelfour
Endpoint: https://mcp.levelfour.ai/mcp
Surface for this key: 36 tools, 5 prompts, 4 resources
Credential: system keychain (l4_live_...abcd)
╭────────────────┬───────────┬────────────┬──────────────────────────────────╮
│ Client │ Installed │ Configured │ Endpoint │
├────────────────┼───────────┼────────────┼──────────────────────────────────┤
│ Claude Code │ yes │ yes │ configured in Claude Code │
│ Claude Desktop │ yes │ yes │ /opt/homebrew/bin/l4 mcp serve │
│ Cursor │ yes │ no │ │
╰────────────────┴───────────┴────────────┴──────────────────────────────────╯The block above the table is global rather than per client: the entry name being looked for, the endpoint, what that server offers the credential l4 resolved for itself, and where that credential came from. l4 mcp status reads the surface line live from the server, so it matches what l4 mcp serve relays.
| Column | What it means |
|---|---|
| Installed | The client was found on this machine |
| Configured | It carries an entry under --name |
| Endpoint | What that entry points at, read back from the file rather than the hosted default above. This is how you catch an entry left pointing somewhere unexpected |
yes in both columns, with an endpoint you recognize beside it.If a client is installed but not configured, run l4 mcp install --client <id>.
--name. A client wired under another entry name, levelfour-org-b for instance, reports no here until you pass the same --name.Reading the surface line
A healthy line counts tools, prompts and resources. If l4 cannot read the server, the line starts unavailable: and carries the reason l4 mcp serve would stop on, and that page explains each one. With no credential at all, it reads unknown until you authenticate.
Reading the credential line
Credential names where the key came from: the --token flag, LEVELFOUR_TOKEN, or the system keychain. CLI authentication has the order l4 resolves them in.
Credential: none means nothing resolved. Run l4 auth login.The key is masked, so the source is the part to read: it names where to go when the wrong credential is in play. Where a client keeps its own key is a separate question, and l4 mcp install covers it.
Related
l4 mcp install: configure a client that reports no under Configuredl4 mcp uninstall: remove an entry it reportsl4 mcp serve: relays the surface this reports on- CLI authentication: how credentials resolve