MCP Server
The Model Context Protocol (MCP) is the most powerful way to connect Q to your development tools. Any tool that supports MCP can talk directly to your Q project - accessing your projects, and all connected product context in real time. Never re-explain your vision!
MCP is an open protocol that standardizes how AI tools communicate with external data sources. If you are interested to learn more check out the official Model Context Protocol docs.
How It Works
When you connect an MCP client (like Cursor, Claude Desktop, or any other MCP-compatible tool) to Q's MCP server, the tool gains access to a set of tools and resources that let it:
- Read your Projects - traverse files, their content, links, and hierarchy
- Access your Mission Board - understand current missions, tasks, and priorities
- Query project context - ask structured questions about your product
- Create and update content - add ideas, update missions, and more
Q exposes your project data only to the extent chosen. Meaning: You choose which files an MCP Token gets access to. You can create multiple tokens for different services so that these services get only the access needed!
Setup
Create an MCP token
In your workspace, open the relevant project, go to the Project Settings (bottom of the file tree on the left), click on "Integrations" and then click on "+ New Token".
Give the token permissions
In the now opening modal, you can give your token a name, set read/write permissions for any files in your project, decide whether to allow file creation and/or deletion.
Add the MCP server config to your tool of choice
If you use Cursor, just click on the "Add to Cursor" - deeplink. Otherwise, in your tool's MCP configuration, point the server to the provided MCP Server config which looks like the following.
{
"mcpServers": {
"Q-Product-Manager-for-YOUR_PROJECT_NAME": {
"url": "https://heyq.com/api/mcp/<idea-id>/mcp",
"headers": {
"Authorization": "Bearer <your-mcp-token>"
}
}
}
}Verify the connection
Check that Q's tools appear in the MCP tool list (else restart your tool). Then ask the tool something like "Hey, I am using Q as my product management tool, what can you tell me about it?" and it should answer appropriately.
If your tool allows you to set rules, check out the automatically created IDE Rule (below the created MCP token). Add this rule to your tool e.g. to the cursor rules and all of your Cursor Agents will always know that you use Q.
Client-Specific Formats
Different MCP clients expect slightly different config formats. Q currently emits these patterns:
Cursor
{
"mcpServers": {
"Q-Product-Manager-for-YOUR_PROJECT_NAME": {
"url": "https://heyq.com/api/mcp/<idea-id>/mcp",
"headers": {
"Authorization": "Bearer <your-mcp-token>"
}
}
}
}Claude Desktop
{
"mcpServers": {
"Q-Product-Manager-for-YOUR_PROJECT_NAME": {
"command": "npx",
"args": [
"mcp-remote",
"https://heyq.com/api/mcp/<idea-id>/mcp",
"--header",
"Authorization:Bearer <your-mcp-token>"
]
}
}
}Claude Code CLI
claude mcp add Q-Product-Manager-for-YOUR_PROJECT_NAME --transport http --scope user https://heyq.com/api/mcp/<idea-id>/mcp --header "Authorization: Bearer <your-mcp-token>"Available Tools
The MCP server exposes a small set of focused tools. Some are always available, while write tools depend on the permissions granted when the MCP token was created.
Read Tools
These are always available for any valid MCP token:
| Tool | Description |
|---|---|
listPages() | Lists all accessible pages with metadata. Useful to discover what content the token can see. |
readPage() | Reads a specific page by path. For mission board items, it includes the mission metadata and body content. |
getProjectContext() | Returns all accessible top-level context in one document. |
Write Tools
These are only available if the token has write access:
| Tool | Description |
|---|---|
createPage() | Creates a standalone page or a new mission board item. Q assigns mission numbers automatically. |
updatePage() | Updates a page or mission. |
createOperations() | Creates one or more operations on a mission board to group related missions. |
Delete Tool
This is only available if the token has both write access and delete permission:
| Tool | Description |
|---|---|
deletePage() | Deletes a standalone page, a mission item, or an entire mission board. Deleting a board also deletes its missions. |
The AI is instructed to always call getProjectContext() first when starting
a new session. Then use listPages() and readPage(path) to drill into
specific files or mission items.
Supported Tools
Any tool that implements the MCP client protocol works with Q. For detailed setup instructions, see our walkthroughs: