Velocity
officialAI-centric project management. Project management for 2026 and beyond.
What can you do with Velocity MCP?
- Create and update issues — Ask your assistant to file a bug or edit an existing issue's fields via
create_issueorupdate_issue. - Search and retrieve issue context — Use
search_issues,get_issue, orget_issue_contextto find related tasks, comments, and linked events. - Manage project and cycle visibility — Pull project details, sprint cycles, and active sprint progress with
list_projects,get_cycle, orget_active_sprint. - Plan and vote on roadmap items — Create, update, or vote on roadmap items and versions using
create_roadmap_item,vote_roadmap_item, orlist_roadmap_versions. - Track agent workflow progress — Link commits or PRs to issues and check pending runs via
link_commit,link_pr, orget_pending_agent_runs. - Configure workspace and domains — Add or verify custom domains and manage workspace settings with
add_domain,verify_domain, orupdate_workspace.
Hosted MCP Server
npx add-mcp 'https://velocity.quest/api/mcp'Installs into Claude Code, Codex, Cursor and more
Documentation
MCP Server
Connect AI agents to Velocity via the Model Context Protocol.
What is MCP?
The Model Context Protocol (MCP) is an open standard that lets AI agents interact with external tools through a unified interface. Velocity includes a built-in MCP server with 84 tools for issue tracking, PRDs and user stories, project context, workspace events, workspace and user management, roadmap planning, custom domains, Claude agent coordination, and more.
AI agents like Claude Code, Claude Desktop, Codex, Cursor, and other MCP-compatible clients can connect to Velocity and create issues, search tasks, update statuses, manage projects, plan roadmaps, and configure domains — all without leaving their workflow.
Availability and access
MCP is available to current members of workspaces on Pro, Business or Enterprise. Free workspaces cannot use MCP. Connect through browser OAuth or a workspace connection token from Settings → MCP. Personal API keys cannot authenticate MCP. See setup and troubleshooting.
The connected server's tools/list response is the current tool and input-schema catalog. A listed tool can still require write scope, an owner/admin role, a feature entitlement, integration configuration or a managed worker lease. Tool access alone does not start a worker or guarantee autonomous coding, review, merge or deployment.
Use Cases
- AI coding assistants — create bug reports directly from code reviews
- Automated triage — agents categorize and prioritize incoming issues
- Status updates — agents update issue progress as they complete work
- Search & context — agents find related issues to inform their work
- Project management — agents read projects, cycles, and milestones
- Roadmap planning — agents manage roadmap items, versions, and voting
- Domain management — agents add and verify custom domains
- AI agent coordination — configured workers process issues, link commits, and track sprint progress
Available Tools
These tables are selected tools. The tools reference also covers PRD and story planning, private attachments, workspace events, issue/check monitoring and delivery profiles. MCP currently reads project/cycle context; use the GraphQL API to create projects, cycles or project milestones.
PRDs and user stories
Read and edit PRDs, requirements and stories; split stories, link issues, and create issues from reviewed story proposals. AI proposal tools require mcp:write, the corresponding AI plan entitlement and available credits. Proposals require separate review and save actions; human PRD approval remains in Velocity. See From idea to issues.
Issue Tracking
| Tool | Scope | Description |
|---|---|---|
list_issues | read | List issues with filters for project, status, priority, assignee, label |
get_issue | read | Get full details of an issue by ID or identifier (e.g., ENG-123) |
create_issue | write | Create a new issue with title, description, priority, status |
update_issue | write | Update an existing issue's fields |
search_issues | read | Full-text search across issue titles and descriptions |
add_comment | write | Add a comment to an issue |
list_comments | read | List all comments on an issue |
Projects & Cycles
| Tool | Scope | Description |
|---|---|---|
list_projects | read | List all projects with optional status filter |
get_project | read | Get project details including milestones and issue count |
list_cycles | read | List sprint cycles with optional status filter |
get_cycle | read | Get cycle details with issue counts and progress |
Workspace Metadata
| Tool | Scope | Description |
|---|---|---|
list_teams | read | List all teams in the workspace |
list_labels | read | List all available labels |
list_statuses | read | List all issue statuses across teams |
list_members | read | List workspace members with roles |
Roadmap
| Tool | Scope | Description |
|---|---|---|
list_roadmap_items | read | List roadmap items with status, category, and version filters |
create_roadmap_item | write | Create a new roadmap item |
update_roadmap_item | write | Update an existing roadmap item |
delete_roadmap_item | write | Delete a roadmap item |
vote_roadmap_item | write | Toggle vote on a roadmap item |
list_roadmap_versions | read | List all roadmap versions (releases) |
create_roadmap_version | write | Create a new roadmap version |
get_roadmap_settings | read | Get roadmap visibility and voting settings |
update_roadmap_settings | write | Update roadmap settings |
Workspace & User
| Tool | Scope | Description |
|---|---|---|
list_workspaces | read | List user workspaces; OAuth returns only the connected workspace |
create_workspace | write | Create a new workspace (user becomes owner) |
delete_workspace | write | Permanently delete a workspace (owner only) |
get_workspace | read | Get current workspace details (name, plan, member count) |
update_workspace | write | Update workspace name (description is unsupported) |
get_current_user | read | Get the authenticated user's profile |
update_current_user | write | Update user display name or avatar |
list_user_api_keys | read | List personal API keys (velu_ prefix) |
create_user_api_key | write | Create a personal API key (returns key once) |
revoke_user_api_key | write | Revoke a personal API key |
Custom Domains
| Tool | Scope | Description |
|---|---|---|
list_domains | read | List custom domains with verification status |
add_domain | write | Add a custom domain with DNS setup instructions |
verify_domain | write | Check domain verification status |
remove_domain | write | Remove a custom domain |
Agent workflow
| Tool | Scope | Description |
|---|---|---|
transition_issue | write | Move issue to a status by name (e.g., "In Progress") instead of UUID |
get_my_issues | read | Get issues assigned to the authenticated user, filtered by status group |
get_active_sprint | read | Get the active cycle with issue counts and progress |
link_commit | write | Record a commit SHA against an issue |
link_pr | write | Record a pull request URL against an issue |
get_issue_context | read | Rich issue context: comments, activities, labels, linked events |
get_pending_agent_runs | read | Get pending API or Claude Code runs for a local worker |
update_agent_run | write | Update an agent run's status, tokens, and result |
Resources
The MCP server also exposes these read-only resources for quick context:
| URI | Description |
|---|---|
velocity://workspace | Workspace metadata (name, slug, plan, member/team counts) |
velocity://issues | Recent issues (last 20, sorted by update time) |
velocity://projects | All projects with status and progress |
velocity://roadmap | Roadmap items, versions, and settings overview |
velocity://domains | Custom domains with verification status |
Credential limitations
OAuth connections cannot list, create or revoke personal API keys, even when those tools appear in the catalog. Manage keys in Velocity settings or use a connection token for these tools. Connection tokens have broader account capabilities; keep them private and revoke unused connections.
Scopes
MCP OAuth grants use these scopes. Connection tokens from Settings → MCP include both:
mcp:read— Read tools and resources, subject to credential and feature restrictionsmcp:write— Write tools, subject to role, feature and worker policy checks (request withmcp:read)
Next Steps
- Setup & Auth — sign in or create a connection token and configure your client
- Tools Reference — detailed parameter docs for each tool