amp mcp remote add: connect Sume with OAuth or a bearer file

To add Sume to Amp, run amp mcp remote add Sume https://mcp.sume.com/mcp --auth oauth for interactive use, or --auth bearer --bearer-token-file /path/to/token for automation. Amp's docs describe both flags, plus a settings.json route where a headers object can read ${VAR_NAME} environment variables, so your Sume key never has to sit in the file.

Which command should you use?

Amp's manual shows the same command with different auth modes. Adapted for Sume:

# Interactive: browser OAuth on the Sume MCP host
amp mcp remote add Sume https://mcp.sume.com/mcp --auth oauth --personal

# Automation: Sume API key stored in a file
amp mcp remote add Sume https://mcp.sume.com/mcp --auth bearer --bearer-token-file /path/to/sume-key --workspace acme

What does each auth mode give you on Sume?

OAuth lands on Sume's consent page. Read is locked on and Write is off by default, so the session sees read-only tools until the person turns Write on. There is no mcp:paid scope. A bearer token file holds a Sume API key, which sends Authorization: Bearer and sees the full hosted tool set. Paid and write calls need an idempotency_key in both cases.

Do not put an OAuth access token where an API key goes. Sume's docs say the two credentials are not interchangeable.

Can you configure it in settings.json instead?

Yes. Amp reads amp.mcpServers from ~/.config/amp/settings.json or .amp/settings.json. Its example for another server uses a url and a headers object with ${VAR_NAME} expansion, so the equivalent for Sume is a url of https://mcp.sume.com/mcp and an x-api-key header set from an environment variable such as ${SUME_API_KEY}. Sume accepts x-api-key or Authorization: Bearer.

Amp also notes that browser-based OAuth flows are unavailable in orbs. For a cloud or unattended run, use the bearer route.

How should an Amp agent handle long renders?

Ask it to call tools_list, then generation_admission_preview or a paid tool with dry_run=true. When the real create returns a job id, resume with jobs_wait on the same id; each call holds at most 55 seconds. If Amp restarts mid-render, find the job with jobs_list instead of resubmitting.