Auggie CLI MCP server: auggie mcp add --transport http for Sume

To add Sume to Auggie, Augment's CLI, run auggie mcp add sume --transport http --url https://mcp.sume.com/mcp --header "x-api-key:$SUME_API_KEY". Augment's docs show this shape for remote HTTP servers and say the result is saved to ~/.augment/settings.json (read 2026-10-02).

What the Augment docs show

The Augment page gives one worked example, a Render MCP server added with --transport http, --url and a repeatable --header flag written as KEY:VAL. The docs cover bearer-style headers only; they do not describe an OAuth flow for the CLI, so this post stays with the key route.

auggie mcp add sume --transport http \
  --url https://mcp.sume.com/mcp \
  --header "x-api-key:$SUME_API_KEY"

Where the key ends up

Your shell expands $SUME_API_KEY before Auggie sees it, so the value is written into settings.json as text. Treat that file like any credential file: do not sync it into a dotfiles repo, and rotate the key if it ever lands in a log or chat. Sume's docs say the same for keys that appear in history (OAuth and API keys).

Sume also says an OAuth token is not an API key and that you should not mint keys for OAuth clients as a workaround, so keep the two paths separate.

What an API key lets Auggie do

Sume documents that an API-key session sees the full hosted tool set. That includes paid creates such as generate_image, generate_video and tts_create, each of which needs an idempotency_key. Spend is governed by the wallet and admission checks; dry_run=true previews a call and max_spend_usd caps it when you pass it (MCP tools and gates).

The page I read does not show a per-tool allowlist for Auggie, so put the guard in your instruction: ask Auggie to call tools_schema and dry_run before any paid create, and to report the job id so you can read it with jobs_status instead of submitting again.

First calls to verify

These are the read-only first calls Sume suggests in its MCP quickstart. If the server does not connect, check the header spelling and that the key variable was set when you ran the command.

• mcp_health confirms the endpoint, auth source and safety posture.
• tools_list shows every tool visible to this session.
• account_me confirms the workspace account context.