Navigation
Stop copying PRDs into chat windows and manually updating tickets. Klority’s official MCP server gives Cursor, Claude Desktop, Claude Code, and Windsurf direct access to your Agile Backlog, Wiki PRDs, QA Test Cases, and CRM.
Just drop this snippet into your IDE or Claude Desktop configuration file.
{
"mcpServers": {
"klority": {
"command": "npx",
"args": ["-y", "@klority/mcp-server"],
"env": {
"KLORITY_API_TOKEN": "klor_pat_YOUR_TOKEN_HERE",
"KLORITY_WORKSPACE": "your-workspace-slug",
"KLORITY_API_URL": "https://app.klority.com/api"
}
}
}
}Why juggle separate plugins for Jira, Confluence, and TestRail? Klority exposes the complete software delivery lifecycle through 12 specialized tools.
Your assistant can query assigned stories, inspect acceptance criteria, transition tickets to "In Progress" or "Done", and post work notes directly to comment threads.
Eliminate hallucinated business logic. AI agents read your actual product specs, architecture diagrams, and DB schemas before writing a single line of code.
Pull formal test cases, preconditions, and step-by-step assertions to synthesize robust Playwright, Jest, or Vitest suites, and record verification runs back into Klority.
Equip coding agents with client context: check account tiers, deal sizes, customer feature requests, and enterprise SLAs straight from your prompt.
Everything you need to know. Click a question to expand the answer.
Model Context Protocol (MCP) is an open standard initiated by Anthropic that allows AI applications (like Cursor, Claude Desktop, Claude Code CLI, Windsurf, and custom autonomous agents) to securely connect to external tools and context. Klority provides an official MCP server that connects your AI assistant directly to your Agile tasks, Wiki PRDs, QA test suites, and CRM records.
Yes. Klority MCP is 100% free and included in all plans (including the Solo free tier). You never pay Klority any fee to connect your AI assistant. You simply bring your existing AI subscription or API key (e.g., Cursor Pro, Claude Desktop, or free local Ollama).
Atlassian requires you to run separate, fragmented MCP servers for Jira and Confluence, with zero native QA test management. Klority is the 'Silo-Killer': a single MCP server provides unified context across your user stories, architectural specs, and QA acceptance criteria in one shot.
There is zero installation required. You can run it instantly using npx -y @klority/mcp-server inside your Cursor or Claude Desktop configuration file. Alternatively, connect directly to our hosted cloud SSE endpoint at https://app.klority.com/api/mcp/sse.
Authentication uses cryptographically secure Personal Access Tokens (klor_pat_...) generated with 1-click in your Klority workspace settings. Every database query enforces strict multi-tenant isolation via your workspaceSlug, ensuring AI agents only access resources you have explicit permission to view.
Yes! Any local agent or IDE supporting the Model Context Protocol standard can connect to Klority's MCP server over local stdio or cloud SSE.
Generate an API key in 1 click and connect Cursor or Claude Desktop to your real-world tasks, PRDs, and test cases.