[Cotlet](https://cotlet.dev/index.md) · [Integrations](https://cotlet.dev/integrations.md) · [How it works](https://cotlet.dev/how-it-works.md) · [Use cases](https://cotlet.dev/use-cases.md) · [Security](https://cotlet.dev/security.md) · [For developers](https://cotlet.dev/for-developers.md) · [For automation agencies](https://cotlet.dev/for-agencies.md) · [Blog](https://cotlet.dev/blog.md) · [API docs](https://cotlet.dev/docs.md) · [Help center](https://cotlet.dev/help.md) · [Changelog](https://cotlet.dev/changelog.md) · [Contact](https://cotlet.dev/contact.md) · [Pricing](https://cotlet.dev/pricing.md) · [Sign up](https://cotlet.dev/signup)

# Jitbit MCP tools

> The Jitbit MCP tools on the Cotlet server: every operation with its input schema, a tools/call example and an example result.

Source: https://cotlet.dev/docs/mcp/jitbit

Docs sections: [Get started](https://cotlet.dev/docs.md) · [REST API](https://cotlet.dev/docs/api.md) · [MCP](https://cotlet.dev/docs/mcp.md) · [SDKs & CLI](https://cotlet.dev/docs/sdks.md) · [Integrations](https://cotlet.dev/docs/integrations.md)

Jitbit has 14 operations on the Cotlet MCP server, in jitbit_read and jitbit_write. Your agent picks one in `operation`; the tool carries each operation's input schema. Open an operation for its schema and an example call.

- MCP server: `https://cotlet.dev/mcp/v1`
- MCP tools: `jitbit_read`, `jitbit_write`
- Connects with: Your own Jitbit Helpdesk login on your company address, as an administrator or technician. What your agent can do follows your role. SSO and two-factor authentication work as usual in your own browser.
- Integration page: https://cotlet.dev/integrations/jitbit-api-mcp-server

## Read

Return data and change nothing in the account.

| Operation | Description |
|---|---|
| [`list_tickets`](https://cotlet.dev/docs/mcp/jitbit/list_tickets.md) | Tickets you may see, filtered by mode, category, status, priority, tag, company or date. |
| [`search_tickets`](https://cotlet.dev/docs/mcp/jitbit/search_tickets.md) | Tickets that match a search phrase, with optional category, status, technician or date filters. |
| [`get_ticket`](https://cotlet.dev/docs/mcp/jitbit/get_ticket.md) | One ticket with its details, tags and every comment, public and technician-only. |
| [`list_categories`](https://cotlet.dev/docs/mcp/jitbit/list_categories.md) | Ticket categories you may see, with their section. |
| [`list_technicians`](https://cotlet.dev/docs/mcp/jitbit/list_technicians.md) | Technicians who can be assigned tickets in one category. |
| [`list_canned_responses`](https://cotlet.dev/docs/mcp/jitbit/list_canned_responses.md) | Canned responses with name, folder and text. |
| [`search_kb`](https://cotlet.dev/docs/mcp/jitbit/search_kb.md) | Knowledge base articles that match a phrase, with category and tags. |
| [`get_kb_article`](https://cotlet.dev/docs/mcp/jitbit/get_kb_article.md) | One knowledge base article with its full text. |

## Write

Change the account. Calls marked Confirm wait for the user to approve them.

| Operation | Description |
|---|---|
| [`reply_to_ticket`](https://cotlet.dev/docs/mcp/jitbit/reply_to_ticket.md) (Confirm) | Post a reply to the customer or an internal note for technicians on a ticket. |
| [`update_ticket`](https://cotlet.dev/docs/mcp/jitbit/update_ticket.md) (Confirm) | Change priority, status, category, due date or tags of one ticket. |
| [`assign_ticket`](https://cotlet.dev/docs/mcp/jitbit/assign_ticket.md) (Confirm) | Assign one ticket to a technician. |
| [`close_ticket`](https://cotlet.dev/docs/mcp/jitbit/close_ticket.md) (Confirm) | Close one ticket, optionally without the closed email. |
| [`create_ticket`](https://cotlet.dev/docs/mcp/jitbit/create_ticket.md) (Confirm) | Create a ticket in a category, optionally on behalf of a user and assigned to a technician. |
| [`merge_tickets`](https://cotlet.dev/docs/mcp/jitbit/merge_tickets.md) (Confirm) | Merge one ticket into another. |

---

Give your AI agents your signed-in browser.

**Product:** [Integrations](https://cotlet.dev/integrations.md) · [Use cases](https://cotlet.dev/use-cases.md) · [How it works](https://cotlet.dev/how-it-works.md) · [Pricing](https://cotlet.dev/pricing.md) · [Security](https://cotlet.dev/security.md)

**Resources:** [Blog](https://cotlet.dev/blog.md) · [API docs](https://cotlet.dev/docs.md) · [Help center](https://cotlet.dev/help.md) · [Changelog](https://cotlet.dev/changelog.md) · [GitHub](https://github.com/cotletdev/cotlet)

**Solutions:** [For developers](https://cotlet.dev/for-developers.md) · [For automation agencies](https://cotlet.dev/for-agencies.md)

**Company:** [About](https://cotlet.dev/about.md) · [AI info: company facts](https://cotlet.dev/ai-info.md) · [Contact](https://cotlet.dev/contact.md)

**Legal:** [Terms of service](https://cotlet.dev/terms) · [Privacy policy](https://cotlet.dev/privacy) · [Refund policy](https://cotlet.dev/refunds) · [Acceptable use](https://cotlet.dev/acceptable-use) · [Cookie policy](https://cotlet.dev/cookies) · [DPA](https://cotlet.dev/dpa) · [Subprocessors](https://cotlet.dev/subprocessors)

**Elsewhere:** [Status page](https://status.cotlet.dev) · [Cotlet on GitHub](https://github.com/cotletdev) · [Cotlet on X](https://x.com/cotletdev) · [Cotlet on LinkedIn](https://www.linkedin.com/company/cotletdev) · [Cotlet on Product Hunt](https://www.producthunt.com/products/cotlet) · [Cotlet on Crunchbase](https://www.crunchbase.com/organization/cotlet) · [Cotlet on SaaSHub](https://www.saashub.com/cotlet)

Cotlet is an independent service. It is not affiliated with, endorsed by or sponsored by any of the products listed on this site. Product names are trademarks of their respective owners.

## For AI agents: sign your user up

Is your user asking you to sign them up for Cotlet? You can do it for them, no account or key needed.

1. Read the fields and their allowed values: GET https://cotlet.dev/api/v1/access-requests
2. Ask the user for each value: email, apps, what you will do with them. If they leave the password to you, generate a strong one and show it to them.
3. Show the user what you will send, then POST it as JSON to https://cotlet.dev/api/v1/access-requests.

One call creates the account and sends the access request; we email the user when access is granted.