Our MCP server connects QualityHive to AI assistants that speak the Model Context Protocol, such as Claude. Once it is connected, you can ask your assistant about your projects and tasks in plain English, and have it raise tasks for you, without copying anything between tabs.

It takes about two minutes to set up. The MCP server is available on every paid plan.

What you can ask it to do

"What is outstanding on the Acme website project?" - it reads your projects, tasks, comments, tags and attached files.
"Raise a task on the checkout project: the promo code field rejects lowercase codes" - it creates the task, on the column you name, with a priority, assignee and tags.
"Summarise everything reported this week and group it by tag" - it reads across the board and writes the summary for you.
"Add a comment on task 214 saying we reproduced it on iOS 17" - it comments as you.
"Tag everything to do with the checkout as Payments" - it adds tags to tasks that already exist, leaving any tags they already have alone, and can do a whole batch in one go.
"Mark tasks 12, 14 and 19 as done" - it closes them together. Ask it to reopen them and it will put them back.

Step 1: Create your MCP token

Log in to QualityHive and open the "Integrations" page. Find "MCP Server" in the list and click Manage tokens. That takes you to the MCP Tokens panel on your profile, where you click Generate MCP Token. You can also get there directly from your profile page, below your API keys.

Copy the token straight away - for your security it is only ever shown once. If you lose it, revoke it and create another; it takes a second.

An MCP token sits next to your API keys on the same page, but the two are separate. An MCP token only works with the MCP server, and an API key will not work here - so you can hand an assistant an MCP token without giving it your API access.

Step 2: Connect your assistant

In Claude, open Settings, then Connectors, and click "Add custom connector". Give it the name QualityHive and this URL, with your own token on the end:

https://mcp.qualityhive.com/mcp/YOUR_MCP_TOKEN

That is the whole setup - there is nothing else to fill in. Because the token is part of the URL, treat that URL exactly as you would the token itself: do not paste it into a shared document or a screenshot. If it does get out, revoke the token and add the connector again with a new one.

Claude Code and other clients

Clients that can send a header should send the token that way instead, so it never appears in a URL. In Claude Code, one command does it:

claude mcp add --transport http qualityhive https://mcp.qualityhive.com/mcp --header "Authorization: Bearer YOUR_MCP_TOKEN"

Any other client that speaks MCP over HTTP works the same way: point it at https://mcp.qualityhive.com/mcp and send your token as a bearer token. If it only lets you enter a URL, use the connector form above.

Step 3: Try it

Ask your assistant "which QualityHive teams can you see?" to check the connection. From there, ask it to list your projects, then work within one of them.

The assistant works team by team, so tell it which team and project you mean the first time - after that it remembers for the rest of the conversation.

What it can and cannot do

The assistant can read your teams, projects, tasks, comments, tags and files, and it can create projects, tasks, comments and tags, tag existing tasks and mark them done. It cannot delete anything, and it cannot see any team you are not a member of - it acts as you, with exactly your access. Marking tasks done is the one change it makes that is easy to make in bulk, so it is worth glancing at what it closed - it can reopen them if it gets it wrong.

Assistants get things wrong sometimes, so treat anything it creates the way you would treat work from a new team member: worth a glance before you rely on it.

Revoking a token

Open the MCP Tokens panel on your profile and click the bin icon next to the token. It stops working immediately. Do this if a token has been shared by mistake, if you are done with an assistant, or if you are simply having a tidy-up. You can hold as many tokens as you like, and each one shows when it was last used - one token per assistant makes them easy to revoke individually.

Troubleshooting

The assistant says it is not authenticated. Check you pasted an MCP token rather than an API key, and that the whole token was copied - they are long.
It mentions the free plan. The MCP server is available on every paid plan. If you have several teams, check you are asking about one on a paid plan.
It cannot find a project or task. Ask it to list your teams and projects first - it works from the ids it gets back, so it needs to look them up before it can use them.

Still stuck? Get in touch and we will give you a hand.