Junie MCP server not working: statuses, sign-in and config fixes

Find the file Junie reads

• User scope, every project: ~/.junie/mcp/mcp.json.
• Project scope: .junie/mcp/mcp.json at the project root.
• In a JetBrains IDE, Junie's MCP Settings page lists each server with its status and tools, shows whether it's stored globally or in the project, and its Add button opens mcp.json for editing.
• The CLI also takes --mcp-location <path> to search more folders, and --mcp-default-locations false to skip the two above.

{
  "mcpServers": {
    "my-local": {
      "command": "npx",
      "args": ["-y", "some-mcp-server"],
      "env": { "API_KEY": "..." }
    },
    "my-remote": {
      "url": "https://example.com/mcp",
      "timeout": 120000
    }
  }
}

Read the status in /mcp

• Starting: Junie is launching or connecting to it.
• Active: running, tools available.
• Inactive: configured and enabled, but not running. Choose Reconnect.
• Disabled: switched off. Choose Enable.
• Failed: the connection failed, the server didn't start, or it crashed. Junie's causes: an invalid entry, failed authentication, a missing dependency or a runtime crash. Fix the cause, then choose Reconnect.
• Authorization required: the remote server wants a sign-in. Choose Authorize, not Reconnect.

Reconnect is only offered for enabled servers that are Failed or Inactive. When Junie runs inside another client over ACP, /mcp is read-only: edit mcp.json directly.

Signing in to a remote server

1. In /mcp, select the server showing Authorization required.
2. Open its menu and choose Authorize.
3. Sign in on the page that opens in your browser.
4. Check the status is now Active.

Junie's docs describe this sign-in for the CLI. In the IDE plugin, use a server that takes a key in headers if the browser sign-in doesn't start.

Timeouts in milliseconds

Junie waits 60 seconds by default for each request: the startup handshake, the tool list and every tool call. timeout overrides it per server, in milliseconds, from 1000 to 3600000. A value outside that range, such as "timeout": 60 written as if it were seconds, is ignored with a warning in the log and the default applies.

Local servers that won't start

A Failed local server usually means the command isn't found or exits. Run the same command and args in a terminal: if it fails there, it fails in Junie. Give command an absolute path if the terminal finds it and Junie doesn't, and put the variables it needs in env.

Taskhold-specific checks

Taskhold is a remote server at https://taskhold.com/api/mcp. When its tools don't show up in Junie, check these in order:

1. The entry in ~/.junie/mcp/mcp.json has url set to exactly https://taskhold.com/api/mcp and no headers. In the Junie CLI, /mcp then shows Authorization required: choose Authorize and sign in, with no sign-up first. The first time Junie uses Taskhold it gives you the link to start the 7-day trial.
2. In the IDE plugin, add a headers line with an atd_sk_ key instead, as on the Junie page. Taskhold's 401 names the cause: missing_key, bad_header, not_a_taskhold_key or unknown_key.
3. Ask Junie to call the taskhold list tool. Settings in Taskhold shows the connection once the first call arrives.

With the tools loaded and the workflow from the Junie page in your guidelines, every task Junie starts, its steps and its questions show on the live board next to your other agents. More clients: MCP server not connecting, fixes for every client.