Decuga now exposes an MCP server, so Claude Desktop, Claude Code, Gemini CLI, and any other MCP-compatible client can create tasks, manage sprints, and triage tickets directly - using whichever AI assistant you already use.
Decuga already has an AI assistant built in - the chat panel, and the Slack bot you can DM or @mention. Both work well, but they're Decuga's assistant, running on Decuga's terms. A lot of teams already live inside a different AI client all day: Claude Desktop, Claude Code in their terminal, Gemini CLI, or something they've wired up themselves. Switching context to a separate chat panel just to create a task is friction that shouldn't exist. MCP removes it - the assistant you already have open can reach into Decuga directly.
MCP (Model Context Protocol) is an open standard for letting an AI client call tools in another application. It's the same idea as the Slack assistant or the in-app chat - an AI reasons about what you asked for, then calls a specific action - except the AI client lives outside Decuga entirely, and it's one you chose and are already paying for. Decuga does the exposing; your client does the reasoning. That also means MCP access adds no extra AI cost on Decuga's side, since your client is the one doing the thinking.
Which one you use depends on your client, not on any real difference in what you get.
| Claude Code, Gemini CLI, OpenAI | Claude Desktop |
|---|---|
| Generate a personal MCP key from your Profile page | Settings → Connectors → Add custom connector |
| Starts with dmcp_ - shown once, copy it immediately | Enter the Decuga MCP URL, nothing else |
| Add it as a bearer token when adding the MCP server | Sign in with your normal Decuga account in the browser |
| Revoke it any time from Profile, no confirmation needed | Approve once - no key to copy or manage |
The in-app chat panel is scoped to whatever project you have open. An MCP client isn't tied to a tab, so it isn't tied to one project either - if you belong to more than one, just tell it which one you mean, or ask it to list your projects first. Every action still checks your actual role and membership on that project, exactly as if you'd clicked into it in the dashboard yourself.
Anything you could do from the Slack assistant, you can now ask your own AI client for, in plain language:
An MCP client acts as you, with exactly the permissions your account already has - the same authorization checks that guard the dashboard and the Slack assistant guard every MCP tool call too. There's no separate, more-permissive door here. Decuga never sees your Claude credentials, and Claude never sees your Decuga password - Claude Desktop's connector uses your normal sign-in, and personal keys can be revoked in one click whenever you want to cut a client off.
Requires Pro or higher
MCP access is available on Pro and Business plans. Everything else about your account works exactly the same either way.
Pick the path that matches your client:
Open Profile → MCP API Keys
Or go straight to Claude Desktop's connector settings if that's your client.
Create a key, or add the connector
A dmcp_ key for Claude Code/Gemini CLI/OpenAI, or a one-time sign-in for Claude Desktop.
Ask it something
Try "what are my open tasks?" to confirm it's connected.
Full setup steps, troubleshooting, and the complete list of what you can ask are in the MCP docs.
Ready to try Decuga?
Start free - no account or credit card required. One week free trial of the Business plan.
Start free trial