Skip to content
qwest.devChangelogGet Qwest

Connect AI apps

Let Claude Desktop, Claude Code, Cursor and other MCP apps work with your projects, as you.

3 min read

AI apps on your computer can connect to Qwest over MCP (Model Context Protocol). Claude Desktop, Claude Code, Cursor, LM Studio and others speak it. Once connected, the app can read your projects and, if you let it, change them. It always acts as you, and never sees more than you can.

This is separate from the Assistant: you bring the app and its model, and the project needs no API key.

  1. Open Profile settings›AI apps.
  2. Under Connect an app, give it a name (like “Claude Desktop on my laptop”), choose what it may do, its projects, and when it expires.
  3. Select Make token. The token is shown once: copy it, or copy the setup for your app straight from the tabs below it.
Terminal window
claude mcp add --transport http qwest https://your-qwest/mcp --header "Authorization: Bearer qwst_…"

Then start a new claude session.

In Settings›Developer›Edit Config, paste this (or add its "qwest" entry to the "mcpServers" already there), then quit and reopen Claude. It needs Node.js.

{
"mcpServers": {
"qwest": {
"command": "npx",
"args": ["-y", "mcp-remote", "https://your-qwest/mcp", "--header", "Authorization: Bearer qwst_…"]
}
}
}

Any app that speaks MCP over Streamable HTTP: give it the address https://your-qwest/mcp and send the token as the header Authorization: Bearer qwst_….

Choice What the app can do
Read only Search and read objects, docs, graphs, tables, tasks, milestones, assets and your community page.
Suggest changes Also propose changes. Each one waits in your Assistant, in a chat named after the app, as a card you apply or dismiss. Nothing changes until you do.
Make changes Changes apply at once, as you. It can also comment on tasks, mark them done, create docs and run your community page.

Changes it can make or suggest: object fields, doc sections, graph cards and links, table rows and columns, new tasks, moving tasks, and who’s assigned.

With Make changes, the app can undo most of what it did. Edits to docs, graphs and tables aren’t undone that way: each file’s version history keeps how it was before, and shows the edit as yours “via” the app.

In projects where you’re a guest, an app can only read.

With Make changes, an app can run the whole community page: the page’s settings and look, the roadmap, polls, the devlog, players’ ideas and bug reports, and playtests open to players. New polls and posts start as drafts, but publishing one takes effect at once, and so does anything else that’s already on a published page. Only project owners can publish the page or change its address, through an app too.

An app sees that a player left an email on a bug report, but not the address. A status change on an idea or a report can notify the player in Discord.

Suggest changes doesn’t cover the community page: those connections can read it, but not change it.

  • Anyone with the token can act as you. Keep it out of chats, screenshots and repositories.
  • An app reads what people wrote in your projects. Text written to mislead it could steer what it does, so prefer Suggest changes unless you trust what’s in the project. Anyone can send ideas and bug reports to a published community page, so be especially careful with an app that reads those and can also change things.
  • Revoke a connection in Profile settings›AI apps to cut it off at once. You can also change what it may do there.
  • Instance admins can turn connecting AI apps off for everyone in Admin.