mcp-atlassian crashes at startup: cannot import name 'FakeConnection' from 'fakeredis.aioredis'

Question

After fakeredis 2.35.0 was released, my mcp-atlassian server (run with uvx mcp-atlassian in Claude Code on macOS/Python 3.12) now crashes at startup with ImportError: cannot import name 'FakeConnection' from 'fakeredis.aioredis'. Is there a fix or a workaround?

Originally asked on GitHub: https://github.com/sooperset/mcp-atlassian/issues/1248

AgentArmor team · Accepted Answer

**Status: fixed** in mcp-atlassian v0.21.1 (released 2026-04-10, now on PyPI). If you can't upgrade, pin `fakeredis` to 2.34.1 as a workaround.

**Root cause:** `fakeredis 2.35.0` renamed `FakeConnection` without a backward-compatible alias. `pydocket` (pulled in transitively via `fastmcp`) imports `FakeConnection` at runtime during lifespan startup, and `pydocket` requires `fakeredis[lua]>=2.32.1` with no upper bound, so fresh `uvx`/`pip` resolutions picked up the broken 2.35.0. The maintainer fixed this in v0.21.1 by pinning `fakeredis>=2.32.1,<2.35.0` directly in mcp-atlassian's dependencies.

**Fix (upgrade):** The maintainer verified startup with:

```bash
uvx --refresh --from mcp-atlassian==0.21.1 mcp-atlassian
```

**Workaround (if staying on an older mcp-atlassian):** Users confirmed adding `--with fakeredis==2.34.1` to the `uvx` args in the MCP client config (e.g., Claude Code's `.claude.json`) works:

```json
{
  "mcpServers": {
    "mcp-atlassian": {
      "command": "uvx",
      "args": ["--with", "fakeredis==2.34.1", "mcp-atlassian"]
    }
  }
}
```

Another suggested workaround was a constraints file:

```
# mcp-atlassian-constraints.txt
fakeredis==2.34.1
```

```bash
uvx --isolated --constraints mcp-atlassian-constraints.txt mcp-atlassian
```

Note: `--from fakeredis@2.34.1` was suggested, but commenters reported `--with` is the correct flag. After upgrading to v0.21.1, you can remove the `--with` pin from your config.

AgentArmor team · Answer

**What @sooperset tried on GitHub** (Worked)

Maintainer verified a fresh install with `uvx --refresh --from mcp-atlassian==0.21.1 mcp-atlassian`; startup now reaches `Starting MCP server` cleanly.

Source: https://github.com/sooperset/mcp-atlassian/issues/1248#issuecomment-4221957745

AgentArmor team · Answer

**What @MysticalGrape tried on GitHub** (Worked)

Added `--with fakeredis==2.34.1` to the uvx args in the MCP server JSON config. Several users confirmed this fixed the ImportError.

Source: https://github.com/sooperset/mcp-atlassian/issues/1248#issuecomment-4218493584

AgentArmor team · Answer

**What @andrew-demb tried on GitHub** (Outcome unclear)

Suggested a constraints file containing `fakeredis==2.34.1` and running `uvx --isolated --constraints mcp-atlassian-constraints.txt mcp-atlassian`; no explicit confirmation in the thread.

Source: https://github.com/sooperset/mcp-atlassian/issues/1248#issuecomment-4218072298

AgentArmor team · Answer

**What @pcf-cmroche tried on GitHub** (Didn't work)

Proposed `--from fakeredis@2.34.1` in the uvx args, but a later commenter corrected that the flag should be `--with`, not `--from`.

Source: https://github.com/sooperset/mcp-atlassian/issues/1248#issuecomment-4218127423

AgentArmor team · Answer

**What a GitHub user tried on GitHub** (Didn't work)

Ran the server via plain `uvx mcp-atlassian`; it crashed at startup with `ImportError: cannot import name 'FakeConnection' from 'fakeredis.aioredis'`.

Source: https://github.com/sooperset/mcp-atlassian/issues/1248

mcp-atlassian crashes at startup: cannot import name 'FakeConnection' from 'fakeredis.aioredis'

6 answers

Add your answer or comment

mcp-atlassian crashes at startup: cannot import name 'FakeConnection' from 'fakeredis.aioredis'

6 answers

Add your answer or comment

Related questions