Agent Update

Connect

JetBrains Junie → Agent Update

JetBrains' coding agent inside the IntelliJ-family IDEs. Configured separately from AI Assistant.

JetBrains Junie talks to Agent Update over MCP. The server is https://api.tryagentupdate.com/v1/mcp, the transport is Streamable HTTP, and the credential is one header.

Where it goes: ~/.junie/mcp/mcp.json (user, preferred) · .junie/mcp/mcp.json (project)

Setup

~/.junie/mcp/mcp.json
{
  "mcpServers": {
    "agent-update": {
      "url": "https://api.tryagentupdate.com/v1/mcp",
      "headers": { "Authorization": "Bearer au_live_..." }
    }
  }
}

Before you file a bug

Test this before publishing it. The shape is verified first-party, but JetBrains never distinguishes Streamable HTTP from SSE, and YouTrack issue JUNIE-461 reports remote support shipping with SSE working and Streamable HTTP still buggy. If it hangs or 404s, fall back to the mcp-remote bridge used for Claude Desktop. No environment-variable interpolation is documented, so use the user scope rather than committing a project file. Junie and AI Assistant are configured independently.

Check it worked

Ask the agent to text you. A 401 means the token is wrong, or the word Bearer is in there twice. No tool at all means the transport string is wrong. Both are covered in troubleshooting.

Next

The five tools and their arguments are on the MCP page. The same tools over plain HTTP are on the REST page. Every other tool is on the docs index.