Add Sume as an MCP server in Junie CLI (mcp.json)
Add Sume to Junie CLI's mcp.json as a remote server with url and headers, or leave headers out and use Authorize for OAuth. Both paths, step by step.

Add Sume to Junie CLI's mcp.json as a remote server with url set to https://mcp.sume.com/mcp. For an API key, add a headers entry of Authorization: Bearer <key>. For OAuth, omit headers and use the Authorize action Junie shows for servers that need it.
Junie's file paths and field names are from its MCP configuration page, read 2026-09-30. Sume's endpoint and auth are from the MCP quickstart and MCP OAuth and API keys.
Where does Junie read mcp.json?
Per Junie's page, a project file lives at .junie/mcp/mcp.json and a user file at ~/.junie/mcp/mcp.json. Use the project file for a team and the user file for yourself.
| Scope | Path |
|---|---|
| Project | .junie/mcp/mcp.json |
| User | ~/.junie/mcp/mcp.json |
What does the Sume entry look like?
Junie's remote example is an object with a url and a headers map holding an Authorization bearer value. Sume accepts Authorization: Bearer $SUME_API_KEY on the hosted endpoint, and an API-key session sees the full tool set, including paid tools. Paid and write calls still need an idempotency_key. Paste your own key into your user file only, never into a committed project file. The surrounding mcpServers wrapper is not in the snippet I read, so copy the outer structure from Junie's page.
"sume": {
"url": "https://mcp.sume.com/mcp",
"headers": {
"Authorization": "Bearer <your Sume API key>"
}
}How does the OAuth path work instead?
Junie says remote servers that need OAuth are added with an "Authorization required" status, and you select the server and choose Authorize. Sume returns an OAuth challenge and protected-resource metadata, so a bare url entry should land in that state. The default grant is mcp:read, which is read-only; Write is an opt-in toggle on the consent page. Docs say not to store OAuth tokens in CLI config.
How do I confirm it works?
Ask the agent to call tools_list, which lists every tool visible to the session. A read-only session shows read tools only; paid tools such as generate_image appear with a key or after Write is granted. For which credential to choose, see API key vs OAuth for an MCP server; a similar JetBrains setup is in IntelliJ with GitHub Copilot.
Sources
Related posts
More in Integrations
- Kling models in Runway MCP vs Sume: what maps to what
Runway MCP added four Kling entries on Sep 18, 2026. Sume lists a Kling v3 Pro row and a Kling motion control MCP tool; it has no Kling O3 row.
- Make webhook "Queue is full" 400: what Sume does and how to recover
When a Make webhook answers 400 Queue is full or 429, Sume retries up to 10 times at a fixed gap. If all fail, redeliver the job's event once the queue drains.
- n8n Edit Image text alignment over a Sume-generated image
n8n 2.39 adds horizontal and vertical alignment to Edit Image's Add Image Text. Generate the picture with Sume, then place the exact words on it.
- n8n MCP workflow access error vs a Sume insufficient_scope
n8n now links MCP workflow access errors to workflow settings. A Sume failure reads differently: insufficient_scope means the OAuth session lacks mcp:write.
Written by Sume