mcp

Manage MCP server connections — authenticate servers and view their status — without re-running the full era-code init wizard.

era-code mcp operates on the Era baseline servers (Linear, Notion, Slack) plus whatever the current project has selected in its manifest. Credentials are written to the same store init uses, so the next era-code start or era-code claude picks them up.

Usage

era-code mcp auth [server]
era-code mcp list

Subcommands

mcp auth [server]

(Re)authenticate MCP servers.

• With no argument, lists the baseline + selected servers with their connection status, then interactively prompts which to (re)authenticate.
• With a server id, (re)authenticates that one server directly.

era-code mcp auth          # interactive picker
era-code mcp auth slack    # authenticate one server by id

Option	Description
-q, --quiet	Suppress output
--json	Output as JSON for programmatic use

mcp list

Show the connection status for the baseline + selected MCP servers. Read-only.

era-code mcp list

Option	Description
-q, --quiet	Suppress output
--json	Output as JSON for programmatic use

What It Does

era-code mcp auth exposes the same credential-prompt routine that era-code init uses, so you can connect or refresh a baseline server (e.g. supply a missing SLACK_USER_TOKEN) without stepping through the whole init flow. Always-enabled servers (observability, era-decision) and servers that need no auth are excluded — there is nothing to authenticate for those.

Stored credentials are consumed by both harnesses on the next launch; a server that was degraded (disabled at launch with a one-line warning) is re-enabled once its token is present.

[!TIP] Run era-code mcp auth to supply the tokens that era-code setup reported as missing, then re-run setup.

See the MCP Servers guide for per-server setup details.