Equipo de ingeniería web con +20 años de experiencia. Creamos, mantenemos y escalamos tu presencia digital con código limpio y soporte continuo.
This listing identifies a third-party MCP server. MCPBundles is not affiliated with, sponsored by, or endorsed by the service or its operator unless stated on this page.
This server may ask you to sign in when your AI client connects.
Last probed Nov 16, 2026 · zabu.es
158tools discovered
For AI agents — MCPBundles Directory API
For MCP client apps (human connect):
MCP connect URL: https://zabu.es/mcp
Skill page: https://www.mcpbundles.com/skills/zabu-mcp-aa4deaa184
Explore capabilities (158)
other 25
Showing 25 of 158
Showing 25 of 158 tools from the public preview. Connect the server to inspect the full live tool list.
List7
Create3
Get3
Show2
Update2
Upload2
Other capabilities6
Api Endpoint Tool
other
login
Authenticate and obtain a bearer token for API access.
Api Endpoint Tool — Authenticate and obtain a bearer token for API access.
Api Endpoint Tool — Invalidate the current bearer token. Requires auth (Authorization: Basic header or _meta.api_token).
Api Endpoint Tool — List tickets with optional filters. Returns paginated results with data[] and meta{} (current_page, last_page, per_page, total). Each ticket includes draft_switch (boolean) — true when the ticket is a draft. By default only published, active tickets are returned: drafts and archived tickets are excluded unless explicitly opted in via draft_switch / include_drafts / include_archived. Each ticket also carries stucked_at / stuck_reason — the stuck mark, filterable with is_stuck. Requires auth (Auth
Api Endpoint Tool — List tickets assigned to a team member, consolidated in a single call: each item already carries the project (id + domain, plus its Work Time as `fulltime` and `work_time`) and the member's role in that ticket's team, so no per-ticket get-ticket-team / show-project follow-up is needed. The Work Time rides along so a dispatcher can decide per candidate whether it may work that project now without a call per project; read it with the same rules show-project documents. All filters are optional and
Api Endpoint Tool — Create a new ticket. Content field accepts Markdown (CommonMark) only — never HTML. The content is rendered with Milkdown in the client portal. created_by is the person who REQUESTED the task. When you are filing this task because somebody asked you to, send their phone number in requester_phone — do it whenever you have the number, which is the normal case for an assistant relaying a request. Omitting it files the task under the authenticated account instead, losing the trace of who asked. Pass
Api Endpoint Tool — Get a single ticket by UUID. Returns raw Markdown in content field, and the boolean draft_switch — true while the ticket is a draft pending approval (hidden from list-tickets and from the automation crons), false once it is published. Three fields answer who is behind the ticket, and they mean different things: created_by is the person who REQUESTED it, filed_by the account that materially filed it when that is somebody else (null when they are the same person), and requester_phone the number th
Get your MCP into directories
A working endpoint is step one. Directory coverage is the coordinated launch across ChatGPT, Claude, Cursor, the MCP Registry, and community indexes.
Equipo de ingeniería web con +20 años de experiencia. Creamos, mantenemos y escalamos tu presencia digital con código limpio y soporte continuo.
How do I connect ZABU Operations to my AI agent?
Use the MCP endpoint listed on this page in your MCP client configuration. One-click install pills support Claude, Cursor, VS Code, and other hosts. Copy the remote MCP URL if your client needs a manual entry.
How many tools does ZABU Operations provide?
Operate this server?
Request removal if you do not want ZABU Operations listed here, or claim the listing if you want to manage it on MCPBundles.
Operate ZABU Operations?
This server appears in the MCPBundles directory. Verify you operate it to take over the listing — name, description, logo, contact email, and skill content. We email a 6-digit code to a maintainer address your server publishes in /.well-known/security.txt or /.well-known/mcpbundles.json. Free, takes about a minute.
MCPBundles publishes this directory for MCP discovery. Except where we host or operate an offering, third-party services run under their own terms. Product and company names on this page are used in a descriptive, identifying way (including under nominative fair use where applicable); they remain the property of their owners. Nothing here grants you rights in those marks, and nothing here is an offer to sell a third party's services. Terms · Request removal
More in developer tools
Other MCP servers in this category from the directory index
Api Endpoint Tool — Update a ticket. PATCH semantic — only send fields you want to change. Content accepts Markdown only. Use parent_id to link as sub-task (pass null to detach); that field is closed to client accounts, and a sub-task carries no budget of its own — the parent is the unit that is quoted and billed. Set archived_at to an ISO 8601 timestamp to archive the ticket (removes it from active pipelines), or null to unarchive. Set approved_at to an ISO 8601 timestamp to override the approval date (normally au
Api Endpoint Tool — Get team members assigned to a ticket. Returns user_id, name, and role for each member. Requires auth (Authorization: Basic header or _meta.api_token).
Api Endpoint Tool — Assign a team member to a ticket. Idempotent — does not duplicate if the user is already assigned. Requires auth (Authorization: Basic header or _meta.api_token).
Api Endpoint Tool — Start a timelog timer for a backend user on a ticket. The `email` body field identifies the human to whom the timer is attributed (independent of the authenticated service account). Idempotent per (ticket, user): if an active timer already exists, the existing timelog is returned with `created=false` and an advisory message. Returns 200 with data, created (bool) and message (?string). Requires auth (Authorization: Basic header or _meta.api_token).
Api Endpoint Tool — Stop the active timelog timer for a backend user on a ticket. When no active timer exists for the (ticket, user) pair the call returns 200 with `data: null`, `closed=false` and an advisory message (does not error) so the caller can prompt for a manual timelog. On success returns 200 with the closed timelog and elapsed `time` in decimal hours. Requires auth (Authorization: Basic header or _meta.api_token).
Api Endpoint Tool — List attachments on a ticket. Requires auth (Authorization: Basic header or _meta.api_token).
Api Endpoint Tool — Attach a file to a ticket. Inverse of download-attachment-binary: the bytes travel as base64 through JSON-RPC. Send `file_base64` (a `data:` URI prefix is accepted and stripped) plus `filename` — the name the file is stored under, e.g. "infographic.png". `mime_type` is advisory only: the server detects the content type from the bytes, and that detected type is what gets validated and stored. Rejects with 422 when the base64 is malformed, the detected type is outside the whitelist (images, docume
Api Endpoint Tool — List the available ticket priority levels (read-only catalog). Returns 5 options in ascending order: 1=Crítica (most important) to 5=Mínima (least important). Each option includes `priority` (integer), `label`, `description`, `criteria` (array of disambiguation rules), and `color`. Use this to classify tickets by impact instead of by the client's label. Requires auth (Authorization: Basic header or _meta.api_token).
Api Endpoint Tool — List the available ticket types (read-only catalog). Returns 3 options in the order defined by the system configuration: feature (Cambio), support (Soporte), bug (Bug). Each option includes `type` (string key used by create-ticket and update-ticket), `label`, `description`, and `color`. Requires auth (Authorization: Basic header or _meta.api_token).
Api Endpoint Tool — List the available ticket statuses and the sub-statuses each one declares (read-only catalog). Returns the main statuses in workflow order (new, quoted, pending, in-progress, feedback, done); each option includes `status` (string key used by create-ticket and update-ticket), `label`, `description`, `color`, and a `sub_statuses` array. A status without a sub-status level returns an empty `sub_statuses` array; `new` declares plan, clarify and budget, and `in-progress` declares develop, test and re
Api Endpoint Tool — List ticket comments (client-visible channel). The client sees these in their portal. Filter by ticket_id to get comments for a specific ticket. Requires auth (Authorization: Basic header or _meta.api_token).
Api Endpoint Tool — Create a ticket comment visible to the client. Content in Markdown. user_id is auto-set from the authenticated user. Requires auth (Authorization: Basic header or _meta.api_token).
Api Endpoint Tool — Get a single comment by ID. Requires auth (Authorization: Basic header or _meta.api_token).
Api Endpoint Tool — Update a comment. Content in Markdown. Requires auth (Authorization: Basic header or _meta.api_token).
Api Endpoint Tool — List attachments on a comment, including voice notes. Each item exposes id, filename, size, mime_type, description, download_url and created_at. Requires auth (Authorization: Basic header or _meta.api_token).
Api Endpoint Tool — Attach a file to a comment, so the client sees it next to the comment in their portal. Inverse of download-attachment-binary: the bytes travel as base64 through JSON-RPC. Send `file_base64` (a `data:` URI prefix is accepted and stripped) plus `filename` — the name the file is stored under, e.g. "screenshot.png". `mime_type` is advisory only: the server detects the content type from the bytes, and that detected type is what gets validated and stored. Rejects with 422 when the base64 is malformed,
Api Endpoint Tool — Delete an attachment from a comment by file ID. Hard delete (no soft-delete). Requires auth (Authorization: Basic header or _meta.api_token).
Api Endpoint Tool — List ticket internal updates (team-only channel, NOT visible to clients). Use for technical notes, commit references, QA checklists. Filter by ticket_id. Requires auth (Authorization: Basic header or _meta.api_token).
Api Endpoint Tool — Create an internal ticket update NOT visible to the client. Use for technical notes, commit logs, progress tracking. Content in Markdown. user_id is auto-set. Requires auth (Authorization: Basic header or _meta.api_token).
Showing the first 25 tools — full list and schemas: Directory API.
MCPBundles probed 158 tools on the live server. The tool list on this page reflects what was discovered at the last refresh — connect your client to see the full set available to your session.
What authentication does ZABU Operations require?
ZABU Operations may require signing in to the provider before tools can run. Connect through MCPBundles or your MCP client and complete any provider login when prompted.
Don't want this listed?
Request removal from the MCPBundles directory. We stop publishing this listing on mcpbundles.com.
MCPBundles is an independent platform built on the open Model Context Protocol standard. MCPBundles is not affiliated with, sponsored by, or endorsed by Anthropic PBC.