Nozbe Teams
Cloud-based task management tool helping individuals and teams get organized.
Verdict
Common use cases
- Capture action items during video standups
- Tag and triage tasks from Slack threads
- Set reminders for follow-ups without leaving chat
- Organize sprint tasks into project sections
- Add status comments to tasks in progress
Integration
- Vendor
- Nozbe Teams
- Category
- other
- Auth
- API_KEY
- Tools
- 48
- Composio slug
nozbe_teams
Tools
- Create Attachment
Tool to add attachment metadata to a comment. Use when you need to create attachment metadata for a file associated with a comment. This creates the metadata record; actual file upload may be a separate step depending on the workflow.
- Create Comment
Tool to add a comment to a task in Nozbe Teams. Use when you need to add feedback, notes, or updates to a specific task.
- Create Project Section
Tool to create a new project section in Nozbe Teams. Use when you need to add a section to organize tasks within a project.
- Create Reminder
Tool to add a reminder to a task in Nozbe Teams. Use when you need to set up a notification for a specific task at a given time.
- Create Tag Assignment
Tool to add a tag assignment to a task. Use when you need to tag or label a task for organization or categorization purposes.
- Create Task
Tool to create a new task in Nozbe Teams. Use when you need to add a task to a project or personal task list. Only the task name is required; all other fields are optional.
- Create Team Member
Tool to add a team member in Nozbe Teams. Use when you need to add an existing user to a team with a specific role and status. The user must already exist in the system before they can be added to a team.
- Create User
Tool to create a new placeholder user in Nozbe Teams. Use when you need to add a placeholder user to the system. Note: Only placeholder users can be created via API - attempting to create non-placeholder users will fail with a 400 error.
- Delete Commentdestructive
Tool to permanently delete a comment by its ID. Use when you need to remove a comment from a task. Returns the deleted comment object with all its properties.
- Delete Projectdestructive
Tool to delete a project in Nozbe Teams by its ID. Use when you need to permanently remove a project from the workspace.
- Delete Reminderdestructive
Tool to delete a reminder by its unique ID. Use when you need to remove a reminder from Nozbe Teams.
- Delete Tag Assignmentdestructive
Tool to delete a tag assignment by its ID. Use when you need to remove a tag from a task or project.
- Delete Taskdestructive
Tool to delete a task in Nozbe Teams by its ID. Use when you need to permanently remove a task from the workspace.
- Get Attachment
Tool to get attachment metadata by its ID. Use when you need to retrieve details about a specific file attached to a comment.
- Get Comment by ID
Tool to retrieve a comment by its ID from Nozbe Teams. Use when you need to fetch details of a specific comment on a task.
- Get Project Access
Tool to retrieve project access details by ID. Use when you need to check a team member's access permissions and manager status for a specific project.
- Get Project by ID
Tool to retrieve a project by its ID from Nozbe Teams. Use when you need to fetch details about a specific project.
- Get Project Section
Tool to retrieve a project section by ID from Nozbe Teams. Use when you need to fetch details of a specific section within a project, including its name, position, and timestamps.
- Get Reminder
Tool to get a reminder by ID from Nozbe Teams. Use when you need to retrieve details about a specific reminder.
- Get Tag
Tool to get a tag by ID from Nozbe Teams. Use when you need to retrieve details about a specific tag.
- Get Tag Assignment
Tool to retrieve a tag assignment by its ID. Use when you need to fetch details about a specific tag-task relationship in Nozbe Teams.
- Get Task by ID
Tool to retrieve a task by its ID from Nozbe Teams. Use when you need to fetch details about a specific task.
- Get Task Event
Tool to get a task event by ID. Use when you need to retrieve details about a specific task event.
- Get Team by ID
Tool to retrieve a team by its ID from Nozbe Teams. Use when you need to fetch details about a specific team.
- Get Team Member by ID
Tool to retrieve a team member by ID from Nozbe Teams. Use when you need to fetch details about a specific team member.
- Get User by ID
Tool to retrieve a user by their ID from Nozbe Teams. Use when you need to fetch details about a specific user.
- List Comment Attachments
Tool to get all attachments related to a specific comment in Nozbe Teams. Use when you need to retrieve attachment metadata (ID, name, size, MIME type, etc.) for a comment. Returns an array of attachment objects with their properties.
- List Comments
Tool to get accessible comments with optional filtering by task_id and pagination support. Use when you need to retrieve comments, optionally filtered by task, with control over pagination and field selection.
- List Group Assignments
Tool to get accessible group assignments from Nozbe Teams. Use when you need to retrieve assignments between groups and projects/members, with optional filtering by group_id, object_id, or group_type.
- List Project Accesses
Tool to get accessible project accesses in Nozbe Teams. Use when you need to retrieve project access records, optionally filtered by sorting or field selection. Returns a list of project access objects showing which team members have access
- List Project Groups
Tool to get accessible project groups from Nozbe Teams. Use when you need to list or search for project groups with optional filtering by name, team, or other criteria.
- List Projects
Tool to retrieve accessible projects with optional filtering. Use when you need to list projects, optionally filtered by team_id or is_open status.
- List Project Sections
Tool to retrieve accessible project sections with optional filtering. Use when you need to list sections within projects, optionally filtered by project_id.
- List Reminders
Tool to get accessible reminders from Nozbe Teams. Use when you need to retrieve reminders, optionally filtered by task ID, all-day status, or other parameters.
- List Tag Assignments
Tool to get accessible tag assignments with optional filtering by tag_id or task_id. Use when you need to retrieve associations between tags and tasks, optionally filtered by specific tag or task identifiers.
- List Tags
Tool to get accessible tags from Nozbe Teams. Use when you need to retrieve tags, optionally filtered by name, favorite status, or task association.
- List Task Events
Tool to get accessible task events from Nozbe Teams. Use when you need to retrieve task activity history or audit trail. Filter by task_id to get events for a specific task.
- List Tasks
Tool to retrieve accessible tasks from Nozbe Teams. Use when you need to query tasks with optional filters like project_id or review_reason. Supports pagination and sorting of results.
- List Users
Tool to retrieve accessible users from Nozbe Teams. Use when you need to query users with optional filters like name. Supports pagination and sorting of results.
- Poll for new tasks
Tool to poll for new tasks created since the last call. Use when you need to retrieve recently created tasks in Nozbe Teams. Optionally filter by project or responsible user, and specify which fields to return.
- Poll Updated Tasks
Tool to poll for tasks that have been updated since the last call. Use when you need to retrieve recently modified tasks from Nozbe Teams.
- Update Comment
Tool to update an existing comment in Nozbe Teams. Use when you need to modify a comment's text, pin status, deletion status, or extra metadata.
- Update Project
Tool to update a project in Nozbe Teams. Use when you need to modify project properties such as name, status, color, or description. All fields except the project ID are optional - only provide fields you want to update.
- Update Project Access
Tool to update project access permissions in Nozbe Teams. Use when modifying member privileges for a specific project.
- Update Task
Tool to update a task in Nozbe Teams. Use when you need to modify task properties such as name, project, responsible user, due date, or other attributes. All fields except the task ID are optional - only provide fields you want to update.
- Update Team
Tool to update a team in Nozbe Teams. Use when you need to modify team properties such as name, color, or sidebar position. All fields except the team ID are optional - only provide fields you want to update.
- Update Team Member
Tool to update a team member in Nozbe Teams. Use when you need to modify team member properties such as role, status, alias, or description. All fields except the team member ID are optional - only provide fields you want to update.
- Update User
Tool to update a user in Nozbe Teams. Use when you need to modify user properties such as name, avatar color, placeholder status, or contact information. All fields except the user ID are optional - only provide fields you want to update.
Setup
Setup guide
- 11. Open your Switchy workspace and navigate to Settings > Integrations > MCP Servers. 2. Select 'Add MCP Server' and choose Nozbe Teams from the directory. 3. Log into your Nozbe Teams account in a separate browser tab and navigate to Settings > API to generate a new API key. 4. Copy the API key and paste it into the Switchy connection dialog, then click 'Connect'. 5. Switchy will verify the key and confirm the connection — you'll see 'Nozbe Teams' listed as active. 6. Open any Space, type '@Nozbe Teams create a task called Test Task' and send the message. 7. The MCP will respond with confirmation and a task ID — check your Nozbe Teams workspace to verify the task appears. 8. You're ready to create tasks, add comments, set reminders, and manage projects directly from chat.
What teammates see: by default, memories from Nozbe Teams 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 Meeting Actions
@Nozbe Teams create tasks for these action items: 1) Draft Q2 roadmap by Friday, 2) Schedule design review with Sarah, 3) Update pricing doc with new tiers. Tag them all 'meeting-followup'.Open in a Space →
Set Weekly Reminders
@Nozbe Teams find the task 'Send weekly metrics email' and add a reminder for every Monday at 9am.Open in a Space →
Organize Sprint Backlog
@Nozbe Teams in the 'Q1 Launch' project, create sections called 'Design', 'Engineering', and 'Marketing', then move all tasks tagged 'design' into the Design section.Open in a Space →
Comment on Blocked Tasks
@Nozbe Teams add a comment to the task 'Finalize API docs' saying 'Blocked until legal approves data retention policy — escalating to Jane'.Open in a Space →
Snapshot Project Status
@Nozbe Teams list all open tasks in the 'Website Redesign' project, grouped by section, and show the last comment on each.Open in a Space →
Example outputs
Illustrative - representative of the model's voice and quality, not literal recordings.
@nozbe show me all tasks tagged 'urgent' across my projects and tell me which ones have no comments yet
I found 7 tasks tagged 'urgent' across 4 active projects. Three tasks have no comments: 'Finalize Q1 budget' in Finance Planning (due March 15), 'Review vendor contracts' in Operations (due March 10), and 'Update security protocols' in IT Infrastructure (no due date set). The other 4 urgent tasks have active discussion threads. Would you like me to add reminder notifications to the uncommented tasks?
This example demonstrates cross-project search and filtering by tags, plus the ability to surface metadata like comment counts. Requires read access to all projects mentioned. The MCP can query task attributes but won't show comment content unless explicitly requested.
@nozbe create a task in the Marketing project called 'Draft launch announcement' due next Friday, assign it to Sarah, and tag it with 'content' and 'Q1-launch'
Task created successfully in the Marketing project. 'Draft launch announcement' is now assigned to Sarah Chen with a due date of March 21, 2025. I've applied both tags ('content' and 'Q1-launch') and set the task to active status. The task ID is #MT-847. Sarah will receive a notification about this assignment. Would you like me to add a reminder or create a comment with additional context?
This write operation showcases task creation with multiple attributes in one prompt. Requires API key with write permissions to the Marketing project. The MCP will validate that Sarah exists as a team member before assignment. Tag names must match existing tags or will be created if your permissions allow.
@nozbe look at all completed tasks in the Product Development project from the last two weeks and draft a progress summary for our stakeholder update
From March 1-14, the Product Development team completed 23 tasks across 3 project sections. Key accomplishments: 8 tasks in 'Feature Development' (including the new dashboard UI and API rate limiting), 9 tasks in 'Bug Fixes' (mostly addressing user-reported issues from v2.3), and 6 tasks in 'Documentation'. The team closed 4 tasks tagged 'high-priority'. Notable: 3 tasks were completed ahead of schedule. Suggested summary: 'Strong two-week sprint with 23 deliverables completed, emphasizing feature work and bug resolution. Dashboard UI and API improvements now ready for QA.'
This synthesis example pairs Nozbe's task data with AI reasoning to generate stakeholder-ready summaries. The MCP retrieves structured task metadata (completion dates, sections, tags), then the AI interprets patterns and drafts prose. Date-range queries depend on accurate task completion timestamps in your Nozbe workspace.
Use-case deep-dives
When Nozbe Teams works for agency client handoffs
A 6-person creative agency hands off 3-4 client projects per month, each with 20-40 tasks, file attachments, and handoff notes. Nozbe Teams is a solid fit here because the Create Comment and Create Attachment tools let you script the entire handoff checklist—add final deliverables, tag outstanding items, set reminders for the client's first check-in. The 48-tool scope means you can automate project section creation and task assignment without leaving the MCP. The threshold: if your handoffs involve more than 2-3 external tools (Figma, Google Drive, Slack), you'll spend more time wiring integrations than Nozbe saves. For agencies that live inside one task manager and need repeatable handoff rituals, this MCP turns a 90-minute manual process into a 10-minute script.
Why Nozbe Teams falls short for high-volume support triage
A 4-person support team triages 80-120 inbound tickets per week, tagging by urgency and assigning to specialists. Nozbe Teams has the Create Tag Assignment and Create Task tools, but the MCP doesn't expose bulk operations or ticket-queue filtering—you're creating tasks one at a time. If your triage workflow is "scan 30 tickets, batch-tag 10 as urgent, assign 5 to engineering," this MCP adds friction instead of removing it. The API_KEY auth is simple, but the tool design assumes you're managing discrete projects, not a high-throughput queue. Use Nozbe Teams for support if your volume is under 20 tickets per week and each ticket becomes a tracked project task. Above that threshold, a dedicated support MCP (or Linear/GitHub Issues) will save you hours per week.
When Nozbe Teams wins for small-team OKR check-ins
A 5-person startup tracks 12 quarterly OKRs, each broken into 3-5 key results with weekly progress updates. Nozbe Teams is a strong match because the Create Project Section and Create Reminder tools let you structure OKRs as projects, key results as sections, and weekly check-ins as recurring task reminders. The Create Comment tool captures progress notes without switching contexts. The 48-tool count means you can script the entire OKR setup at quarter-start—create projects, assign owners, set all 12 weeks of reminders—in one MCP call. The limit: if your OKRs require live dashboards or roll-up metrics, Nozbe doesn't expose read/aggregate tools in this MCP. For teams under 10 people who treat OKRs as structured task lists, not BI dashboards, this MCP turns quarterly setup from a half-day workshop into a 15-minute automation.
Frequently asked
What does the Nozbe Teams MCP let me do in Switchy?
It connects your Nozbe Teams workspace so AI agents can create tasks, add comments, set reminders, organize projects with sections, and manage tags — all without leaving the chat. You can ask an agent to draft a project plan and it'll create the tasks, assign tags, and set due dates directly in Nozbe. Useful for turning meeting notes or brainstorms into actionable work.
Do I need admin access to connect Nozbe Teams?
You need an API key from Nozbe Teams, which typically requires admin or owner permissions to generate. The key gives Switchy full read-write access to your workspace — tasks, projects, comments, team members. If you're not an admin, ask whoever manages your Nozbe account to create the key and share it with you securely.
Can the MCP assign tasks to specific team members?
Yes, but only to users who already exist in your Nozbe Teams workspace. The MCP can create placeholder users and add existing users to teams, but it can't invite new people by email or manage their Nozbe login. If you need to assign a task to someone new, add them in Nozbe first, then reference them by ID in Switchy.
How is this different from just using Nozbe Teams directly?
Nozbe's UI is built for manual task entry. The MCP shines when you want AI to structure work for you — parsing a messy email thread into tasks, turning a voice memo into a project outline, or batch-creating reminders from a list. It's faster for bulk operations and integrates with other MCPs in the same Switchy thread, like pulling data from Notion or GitHub.
Who on the team should connect this MCP?
Whoever owns project planning or task coordination. The API key grants full workspace access, so this should be someone trusted to create, edit, and delete tasks across all projects. If multiple people need it, share the Switchy workspace — the MCP connection applies to everyone in that workspace, not per-user.