Dunyo for Claude, ChatGPT and other AI apps
Last Updated: November 19, 2026
Connect Dunyo to Claude, ChatGPT, Codex, Cursor or any app that supports the Model Context Protocol (MCP). Your AI app can then find and update issues, check how projects and initiatives are going, see who's out and who has capacity, track career progress and catch up on your inbox, all in plain language.
The connected app acts as you: it works only in the workspace you approve and can do only what your role in Dunyo allows.
Server URL: https://api.dunyo.app/mcp
Set up
Claude (web and desktop)
- In Claude, open Customize → Connectors and browse the directory.
- Find Dunyo and select Connect.
- Sign in to Dunyo, choose the workspace to connect, and approve the connection.
On Team and Enterprise plans, an organization Owner adds Dunyo for the organization first, and then each member connects with their own Dunyo account.
To add Dunyo as a custom connector instead, open Customize → Connectors, select +, choose Add custom connector, name it Dunyo and paste the server URL.
Claude Code
Run:
claude mcp add --transport http dunyo https://api.dunyo.app/mcp
Then run /mcp in Claude Code, select dunyo and sign in.
ChatGPT
- In ChatGPT, open the plugin directory and find Dunyo.
- Select Connect.
- Sign in to Dunyo, choose the workspace to connect, and approve the connection.
- In a chat, select + and choose Dunyo, or mention Dunyo in your request.
To add Dunyo as a custom app instead, open Settings → Apps → Advanced settings and turn on Developer mode, then select Create, name it Dunyo, paste the server URL and choose OAuth. Custom apps need a ChatGPT Business, Enterprise or Edu plan, and a workspace admin may need to turn on Developer mode first.
Codex
codex mcp add dunyo --url https://api.dunyo.app/mcp
codex mcp login dunyo
Cursor and other apps
Apps that can't open a browser sign-in can use a personal API key. In Dunyo, open Settings → AI agents, create a key and copy it (it's shown only once). Then add Dunyo to your app's MCP configuration. For Cursor, add this to ~/.cursor/mcp.json:
{
"mcpServers": {
"dunyo": {
"url": "https://api.dunyo.app/mcp",
"headers": { "Authorization": "Bearer YOUR_API_KEY" }
}
}
}
Settings → AI agents in Dunyo also shows ready-to-copy setup for each app, filled in with your key.
Try it
Once connected, ask your AI app things like:
- "What should I work on today?"
- "Start DUN-123"
- "Who's out on Backend this week?"
- "What needs my attention?"
Every tool, with an example of what to ask, is listed below.
Dunyo also offers prompt templates, such as starting an issue, writing a new issue from a short request, and designing a career ladder. Your app lists them where it shows prompts (in Claude Code, type /).
What the app can do
Each tool has an example of what to ask. Reads run without changing anything. Adds create something new. Changes overwrite existing data, so Dunyo marks them for your AI app, and apps such as Claude ask for your confirmation before running them.
Absences
| Tool | What it does | Example | Type |
|---|---|---|---|
list_absences | Who's out between two dates, for the workspace, a team or a person | “Who's out on Backend this week?” | Read |
request_time_off | Requests time off, pending approval where the absence type needs it | “Book vacation for me Dec 23 to Jan 2” | Adds |
Career · Ladders
| Tool | What it does | Example | Type |
|---|---|---|---|
create_ladder | Creates a complete career ladder as a draft | “Draft an iOS engineering ladder from junior to staff” | Adds |
Career · Progressions
| Tool | What it does | Example | Type |
|---|---|---|---|
get_team_readiness | Who is ready for or closest to their next level, and what's blocking them | “Who on Backend is ready for promotion?” | Read |
get_progression | A person's level and progress toward the next one | “How close am I to Senior Engineer?” | Read |
update_requirement_status | Marks a career requirement completed, in progress or incomplete | “Mark ‘Leads a cross-team project’ as met for Aziz” | Changes |
add_progression_note | Adds a note to a person's career progression | “Add a note to my progression about the billing migration” | Adds |
Inbox
| Tool | What it does | Example | Type |
|---|---|---|---|
list_inbox | Your notifications, starting with those that need action | “What needs my attention?” | Read |
mark_inbox_done | Clears inbox items (you can restore them in Dunyo) | “Mark the comments you just answered as done” | Changes |
Workflow · Initiatives
| Tool | What it does | Example | Type |
|---|---|---|---|
list_initiatives | Lists initiatives with status, health, owner and target date | “What initiatives are at risk this quarter?” | Read |
get_initiative | An initiative's health, progress of each project and latest updates | “How is Mobile launch going?” | Read |
create_initiative | Creates an initiative | “Create a Mobile launch initiative owned by me, target June 30” | Adds |
update_initiative | Changes an initiative's title, description, status, owner, priority or dates | “Move Mobile launch's target date to July 15” | Changes |
post_initiative_update | Posts a status update and sets the initiative's health, visible to the whole workspace | “Draft this week's update for Mobile launch” | Adds |
Workflow · Issues
| Tool | What it does | Example | Type |
|---|---|---|---|
search_issues | Full-text search over open issues, or find one by its key | “Find issues about checkout” | Read |
list_issues | Lists issues by team, assignee, status, project, label or priority | “List urgent bugs in Payments v2” | Read |
list_my_work | Your open issues by in progress, overdue, due soon and up next | “What should I work on today?” | Read |
get_issue | Reads an issue with its comments, sub-issues, related issues and attachments | “What does DUN-123 ask for?” | Read |
create_issue | Creates an issue | “Create an issue for the login timeout bug” | Adds |
create_sub_issues | Splits an issue into up to 20 sub-issues | “Split DUN-100 into backend and web tasks” | Adds |
update_issue | Changes an issue's title, description, status, priority, assignee, labels, project, due date or estimate | “Mark DUN-123 as done” or “Assign DUN-123 to me with high priority” | Changes |
link_issues | Records that one issue blocks, duplicates or relates to another | “DUN-123 is blocked by DUN-98” | Adds |
add_comment | Comments on an issue | “Comment on DUN-123 with what you changed” | Adds |
start_issue | Moves an issue to In Progress, assigns it to you and returns everything needed to work on it | “Start DUN-123” | Changes |
finish_issue | Comments with a summary and pull request link and moves the issue to review | “Finish DUN-123, the PR is github.com/…/pull/42” | Changes |
Workflow · Labels
| Tool | What it does | Example | Type |
|---|---|---|---|
list_labels | Labels available for a team's issues | “Which labels does the Backend team use?” | Read |
Workflow · Projects
| Tool | What it does | Example | Type |
|---|---|---|---|
list_projects | Lists a team's active projects | “What projects does Backend have?” | Read |
get_project | A project's status, lead, dates and progress, with its open and recently completed issues | “How is Payments v2 going?” | Read |
create_project | Creates a project | “Create a Q1 billing project led by Emma, due March 31” | Adds |
update_project | Changes a project's name, description, status, lead, initiative or dates | “Move Payments v2's due date to April 15” | Changes |
add_project_comment | Comments on a project | “Note on Payments v2 that we dropped Apple Pay from scope” | Adds |
Workspace · Members
| Tool | What it does | Example | Type |
|---|---|---|---|
search_people | Finds people by name, email, job title, department or team | “Who owns payments, and who do they report to?” | Read |
get_person | A person's role, manager, teams, local time, time off and open work | “When is Emma back, and what is she working on?” | Read |
get_workload | Open issues per person, with who's out, to see who has capacity | “Who on Backend has capacity for DUN-123?” | Read |
Workspace · Teams
| Tool | What it does | Example | Type |
|---|---|---|---|
list_teams | Your teams, their keys and workflow statuses | “Which teams am I in?” | Read |
Revoke access
In Dunyo, open Settings → AI agents. Select Disconnect next to an app, or Revoke next to an API key. Access stops immediately. App connections that go 90 days without being used are removed automatically; API keys last until they expire or you revoke them.
You can also remove Dunyo in your AI app: in Claude, under Customize → Connectors; in ChatGPT, under Settings → Apps.
Troubleshooting
- "Sign in to Dunyo" or "invalid token": disconnect Dunyo in your AI app and connect it again.
- "You are no longer an active member of this workspace": your account was deactivated in that workspace. Ask a workspace admin.
- "Too many requests": the app sent too many requests in a short time. Wait a minute and try again.
- An issue, project or person isn't found: the app sees only teams and data you can see in Dunyo. Check that you connected the right workspace.
- An error with a reference: something went wrong on our side. Check whether the change was saved, and if the problem continues, email [email protected] with the reference.
More help is on the Support page. How we handle data that connected apps access is in our Privacy Policy.