# Qwen Code

Qwen Code can read your fivebar stats over MCP, and answer questions about them.

Ask it about your sites in your own words, such as why traffic jumped on Tuesday, and it answers from your figures, following fivebar’s rules about what they mean. Working in your site’s code, it can also [add fivebar to it](https://fiveb.ar/docs/coding-assistants.md) and check it’s working. Connecting is adding fivebar’s address, signing in and choosing Allow, with no key to copy.

## Add fivebar

Run:

```
qwen mcp add --transport http fivebar https://fiveb.ar/api/mcp
```

That keeps it in `~/.qwen/settings.json`, for every project. Add `--scope project` to keep it in `.qwen/settings.json` in the project instead. Or write it there yourself:

```
{
  "mcpServers": {
    "fivebar": {
      "httpUrl": "https://fiveb.ar/api/mcp"
    }
  }
}
```

If Qwen Code was already running, restart it in the same project.

## Sign in

Start Qwen Code, run `/mcp`, choose fivebar and authenticate. Qwen Code needs no client ID or secret: it registers itself with fivebar.

fivebar opens in your browser. Sign in if you need to, check that the page names Qwen Code, and choose Allow. Qwen Code can then [read the stats](https://fiveb.ar/docs/mcp.md#what-an-app-can-read) of every site on your Sites page, and changes nothing of yours unless you also tick the box to let it [change settings](https://fiveb.ar/docs/mcp.md#changing-settings).

## Try it

Ask Qwen Code about your sites in your own words, such as:

- Which pages did best last week, and where did their visitors come from?
- How does this month compare with last month so far?
- How many people are on my site right now?

## Removing it

Run `qwen mcp remove fivebar`, which also deletes what Qwen Code kept to stay signed in.

To stop Qwen Code reading your stats from fivebar’s side, disconnect it in [Settings](https://fiveb.ar/settings).

## Good to know

Qwen Code listens for your browser at `localhost:7777`, so sign in with a browser on the same computer as Qwen Code. It keeps what it needs to stay signed in in `~/.qwen/mcp-oauth-tokens.json`, unencrypted unless you set `QWEN_CODE_FORCE_ENCRYPTED_FILE_STORAGE=true`.

More in [Qwen Code’s own documentation](https://qwenlm.github.io/qwen-code-docs/en/users/features/mcp/).