Onedesk
OneDesk is an all-in-one platform combining help desk and project management functionalities, enabling teams to manage customer support and project tasks seamlessly.
Verdict
Common use cases
- Log billable hours from standup chat
- Archive completed tickets after sprint review
- Delete duplicate customer records in bulk
- Create tasks from support conversation threads
- Remove outdated project requirements quickly
Integration
- Vendor
- Onedesk
- Category
- other
- Auth
- API_KEY
- Tools
- 28
- Composio slug
onedesk
Tools
- Create Worklog Entry
Tool to create a worklog entry. use after confirming object type, object id, and user id. logs time spent on objects such as tickets, tasks, or projects.
- Delete Attachmentdestructive
Tool to delete a specific attachment. use when you need to remove an existing attachment by its id after confirming its details.
- Delete Commentdestructive
Tool to delete a specific comment by its id. use when you have confirmed the comment should be removed.
- Delete Customerdestructive
Tool to delete a customer. use after confirming the customer id before removal. example: {'customer id': '12345'}
- Delete Messagedestructive
Tool to delete a specific message. use when you need to remove an existing message by its id after confirming its details.
- Delete Projectdestructive
Tool to delete a project by its id. use when you need to remove a project from onedesk after confirming it's no longer needed. example: {'project id': 123}
- Delete Requirementdestructive
Tool to delete a requirement. use when you need to remove a requirement by its id after confirmation. example: {'requirement id': '12345'}
- Delete Taskdestructive
Tool to delete a specific task. use when you need to remove an existing task by its id after confirming its details.
- Delete Ticketdestructive
Tool to delete a ticket by its id. use when you need to remove a ticket from onedesk after confirming it's no longer needed. example: {'ticket id': 123}
- Delete Timesheetdestructive
Tool to delete a timesheet by its id. use when you need to remove a specific timesheet after confirming it's no longer needed. example: {'timesheet id': 123}
- Delete Userdestructive
Tool to delete a user by its id. use after confirming the user should be removed. example: {'user id': '12345'}
- Delete Worklogdestructive
Tool to delete a worklog by its id. use when you need to remove a worklog entry after confirming it's no longer needed. example: {'worklog id': 123}
- Get Attachments
Tool to retrieve a list of attachments. use when you need to fetch all attachments from onedesk.
- Get Comment Details
Tool to retrieve detailed information for a comment by its id. use when you need full comment data after obtaining the comment id. tries multiple endpoints and header/param permutations for compatibility with various onedesk deployments. if
- Get Comments
Tool to retrieve all comments. use when you need to list or process existing comments.
- Get Feedback Details
Tool to retrieve details of a specific feedback item. use when you have the feedback id and need its full details.
- Get Feedback Items
Tool to retrieve all feedback items. use when you need to list feedback entries for review.
- Get Issue Details
Tool to retrieve details of a specific issue. use when you have the issue id and need its full details.
- Get Issues
Tool to retrieve a list of issues. use when you need to fetch all issues from onedesk.
- Get Messages
Tool to retrieve a list of messages. use when you need to list all messages from onedesk.
- Get Requirement Details
Tool to retrieve full details of a specific requirement. use when you have the requirement id and need its complete data.
- Get Requirements
Tool to retrieve a list of requirements. use when you need to fetch all requirements from onedesk.
- Get Task Details
Tool to retrieve details of a specific task in onedesk. use when you have a task id and need full task information.
- Get Tickets
Tool to retrieve a list of tickets. use when you need to fetch all tickets from onedesk.
- Get Timesheet Details
Tool to retrieve details of a specific timesheet entry. use when you have the `timesheet id` and need full metadata (user, project, hours, dates). tries multiple endpoint/header variants and gracefully falls back in restricted environments.
- Get Timesheets
Tool to retrieve a list of timesheet entries. tries multiple endpoint variants and header permutations to improve compatibility across onedesk environments.
- Get Worklog Details
Tool to retrieve details of a specific worklog. use when you have a worklog id and need full worklog information. tries multiple endpoint/header variants and gracefully falls back in restricted environments.
- Get Worklogs
Tool to retrieve all worklogs. use when you need to list or process existing worklog entries.
Setup
Setup guide
- 11. Open your Switchy workspace and navigate to Settings, then Integrations. 2. Find Onedesk in the MCP directory and click Connect. 3. Log into your Onedesk account in a separate tab, go to Administration, then API Settings, and generate a new API key. 4. Copy the key and paste it into the Switchy connection dialog, then click Authorize. 5. Switchy confirms the connection and shows which tools are now available. 6. Open any Space and type '@Onedesk list my open tasks' to verify the integration works. 7. If the AI returns task data, the connection is live. 8. To invoke a tool, @mention Onedesk in your message and describe what you need — the AI will call the appropriate tool and confirm the action before executing destructive operations like deletes.
What teammates see: by default, memories from Onedesk are scoped to the Space (PROJECT visibility) - you can mark any memory PRIVATE or share it ORG-wide.
Works well with
Top models
Compatibility data appears once enough Spaces have used this MCP together with a given model.
How Switchy teams use it
Starter prompts
Log Time on Task
@Onedesk I spent 3 hours on task #4782 today working on the API integration. Create a worklog entry for my user account.Open in a Space →
Clean Up Old Tickets
@Onedesk Show me all tickets marked resolved in the last 30 days, then delete tickets #1123, #1145, and #1198 from the system.Open in a Space →
Archive Finished Project
@Onedesk Delete project #567 and confirm all linked tasks are removed. This was the Q4 website redesign project.Open in a Space →
Remove Duplicate Customers
@Onedesk List customers with email addresses containing 'test@example.com', then delete customer IDs 8821 and 8823.Open in a Space →
Delete Outdated Comments
@Onedesk Find comments on task #3401 posted before January 1st, then delete comment IDs 9912 and 9915.Open in a Space →
Example outputs
Illustrative - representative of the model's voice and quality, not literal recordings.
@onedesk show me all open tickets assigned to Sarah Chen and summarize which ones are overdue
Based on OneDesk's current data, Sarah has 7 open tickets. Three are overdue: TICK-1204 (customer login issue, due 2 days ago), TICK-1189 (billing discrepancy, due 5 days ago), and TICK-1177 (feature request follow-up, due 1 week ago). The remaining 4 tickets are on track, with due dates ranging from tomorrow to next Friday. TICK-1189 has the highest priority flag and two unread customer replies.
This example demonstrates OneDesk's read capabilities for ticket management. Requires API key with read permissions for tickets and user assignments. Response accuracy depends on your OneDesk account's current state—ticket counts and details will vary. The MCP cannot modify priorities or due dates in this query; it only retrieves and the AI synthesizes.
@onedesk create a worklog entry for task TASK-456 showing I spent 2.5 hours on database optimization today
Worklog entry created successfully for TASK-456. Logged 2.5 hours of work under your user ID (UID-7821) with description 'database optimization' and today's date (January 15, 2025). This time entry is now visible in the task's activity timeline and will be included in your timesheet reports. The task's total logged time has been updated to 8.5 hours.
This showcases OneDesk's time-tracking integration—useful for teams billing by the hour or tracking sprint capacity. The MCP requires your OneDesk user ID, the task ID, and valid API credentials with write permissions. Be careful: worklog entries are permanent records that affect billing and reporting, so confirm details before creating them.
@onedesk find all projects marked 'at risk' and draft a status email summarizing blockers for each one
Found 3 projects flagged as 'at risk' in OneDesk. Here's a draft status summary: **Mobile App Redesign (PROJ-89)**: Blocked by pending design approval from stakeholders. 4 tasks overdue, launch date at risk. **API v3 Migration (PROJ-102)**: Dependency on third-party vendor delayed 2 weeks. 12 open tickets related to compatibility testing. **Customer Portal Upgrade (PROJ-115)**: Resource constraint—lead developer reassigned. 6 critical tasks unassigned. Recommend escalating PROJ-102 and PROJ-115 in tomorrow's standup.
This example pairs OneDesk's project-filtering tools with AI reasoning to generate executive summaries. The MCP fetches raw project data (status flags, task counts, blocker notes); the AI synthesizes it into readable prose. Requires read access to projects and tasks. The 'at risk' flag must exist in your OneDesk workflow—custom statuses vary by account configuration.
Use-case deep-dives
When Onedesk fits agencies billing by the hour
A 6-person creative agency runs client projects in Onedesk and needs to log billable hours against tickets and tasks for monthly invoicing. The Create Worklog Entry tool makes this straightforward—team members can log time directly to the object they worked on, and the API key auth means the agency owner controls access without per-seat OAuth overhead. The catch: if your team already lives in a dedicated time-tracker like Harvest or Toggl, adding Onedesk worklogs creates a second source of truth. This MCP works when Onedesk is already your project hub and you want time-tracking in the same system. If you're over 15 people or need complex approval workflows, you'll outgrow the worklog tooling fast. For small agencies consolidating tools, this is the right call.
Onedesk handles support ops for small SaaS teams
A 4-person SaaS startup uses Onedesk for customer support tickets and needs to bulk-delete spam, merge duplicate customers, and archive old messages during quarterly cleanups. The Delete Customer, Delete Message, and Delete Comment tools give you programmatic control over these maintenance tasks without clicking through the UI. API key auth means one admin can run cleanup scripts in Switchy without provisioning OAuth for the whole support team. The limitation: Onedesk's 28 tools cover CRUD operations but don't expose advanced filtering or bulk actions—if you're deleting 500 spam tickets, you'll loop through individual Delete Task calls. This MCP shines when you have under 100 objects to manage per cleanup and want to script repetitive admin work. For high-volume support queues, dedicated helpdesk platforms scale better.
When contractors need limited Onedesk access
A product manager hires a freelance designer for a 3-week sprint and needs to give them access to specific Onedesk tasks and requirements without full account permissions. The Delete Requirement and Delete Project tools let the PM clean up draft work or remove test projects after the engagement ends, while the API key setup means the freelancer never touches the main Onedesk account. This works when you're onboarding short-term contributors who only need to see their assigned work—Switchy becomes the controlled interface. The trade-off: if your freelancer needs to create new tasks or comment extensively, the 28-tool set feels limiting compared to full Onedesk access. Use this MCP when you want to script post-project cleanup and keep contractors in a read-mostly workflow. For ongoing external collaborators, native Onedesk guest accounts are simpler.
Frequently asked
What does the Onedesk MCP do in Switchy?
It connects your Onedesk project management workspace to Switchy's AI agents. Your team can create and delete tickets, tasks, projects, and requirements through natural language. Agents can also log time entries, manage comments and attachments, and handle customer records — all without switching between tools or remembering Onedesk's interface conventions.
Do I need admin access to connect Onedesk?
You need an API key from Onedesk, which typically requires admin or account owner permissions to generate. The key grants full access to your Onedesk workspace — creating, reading, updating, and deleting all object types. If your Onedesk admin restricts API key generation, you'll need to request one from them before connecting.
Can the MCP update existing tasks or only create new ones?
The current tool set focuses on creation and deletion — you can create worklog entries, delete tasks, projects, requirements, comments, attachments, messages, and customers. If you need to update a task's status, assignee, or description, you'll need to do that directly in Onedesk or via their API. The MCP doesn't expose update operations yet.
Why use this instead of just opening Onedesk?
It's faster when you're already working in Switchy and need to log time, create a task from a conversation, or delete outdated requirements. Instead of context-switching to Onedesk's interface, you ask an agent. The trade-off: you lose Onedesk's visual project views and bulk editing features, so use the MCP for quick transactional work, not project planning.
Who on the team should connect the Onedesk MCP?
Whoever has access to generate an API key — usually a project admin or account owner. Once connected, any Switchy workspace member can use the MCP through shared agents. If your team has strict Onedesk permissions, consider whether you want everyone deleting projects and customers through AI, or if you should limit this to leads.