[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) # SysAid API and MCP server > SysAid has a full REST API, the Connect API, but no official MCP server (checked 23 Oct 2026). The API covers service records, notes, users, assets and more, and needs a SysAid Spaces account and an app key, and its guides ask for administrator permissions. SysAid's own AI agents work inside SysAid; its documentation describes no MCP server for outside agents. IT service management platform: incidents, requests, problems and changes in one queue, with routing rules, SLAs, a knowledge base and AI agents for IT teams. ## What is the SysAid API? Cotlet's SysAid API exposes 12 endpoints for your own SysAid account: search service records, get a service record, list notes of a record, list values of a field, list agents and groups, create a service record, update a service record, assign a service record, add a note, send a message from a record, resolve a service record and merge service records. The search_service_records endpoint returns list the records in your SysAid queue that match a text search and filters. Each endpoint takes simple JSON inputs like record_id, status or priority and works both as an operation of the sysaid_read or sysaid_write MCP tool for agents and as a REST call for scripts. - **Category:** [Customer support](https://cotlet.dev/integrations/category/customer-support.md) - **Endpoints:** 12 (5 read, 7 write) - **Updated:** 2026-10-21 SysAid has a full REST API, the Connect API, but no official MCP server (checked 23 Oct 2026). Cotlet is a hosted MCP server and REST API for SysAid with 12 endpoints (5 read, 7 write): you sign in once in your own cloud browser, your AI agent does the work. ## Does SysAid have an official API? SysAid has a full REST API, the Connect API, but no official MCP server (checked 23 Oct 2026). The API covers service records, notes, users, assets and more, and needs a SysAid Spaces account and an app key, and its guides ask for administrator permissions. SysAid's own AI agents work inside SysAid; its documentation describes no MCP server for outside agents. | Task | SysAid official | Cotlet | |---|---|---| | Search and read service records | Yes: Connect API; status, priority and category are numeric IDs you look up per account | Yes | | Read and add notes | Yes: Connect API, internal or shared with the requester | Yes | | Change priority, status, assignee and group | Yes: Connect API, PATCH on the service record | Yes | | Resolve a record with a solution | Yes: Connect API, resolve endpoint | Yes | | Send a message from a record | Yes: Connect API | Yes | | Create a record | Yes: Connect API; you pass a template ID | Yes | | Merge duplicate records | No: No merge endpoint in the API reference; merging is a bulk action in the queue | Yes | | Work tickets from an MCP client | No: No official MCP server; you write the tool layer | Yes | Sources: [SysAid Developers: Getting Started](https://developers.sysaid.com/docs/sysaid-api-overview), [SysAid Developers: Authentication Guide](https://developers.sysaid.com/docs/authentication-guide), [SysAid Developers: Search Service Records](https://developers.sysaid.com/reference/searchservicerecords), [SysAid blog: AI Agent Center](https://www.sysaid.com/blog/sysaid-tech/ai-agent-center) ## Quick reference ```text SysAid has a full REST API, the Connect API, but no official MCP server (checked 23 Oct 2026). The API covers service records, notes, users, assets and more, and needs a SysAid Spaces account and an app key, and its guides ask for administrator permissions. SysAid's own AI agents work inside SysAid; its documentation describes no MCP server for outside agents. Cotlet provides a hosted MCP server and REST API for SysAid: 12 tools (5 read, 7 write). Access Sign up at https://cotlet.dev/app/signup?app=sysaid, then request the app and create API keys in the Cotlet console. MCP server https://cotlet.dev/mcp/v1 MCP tools sysaid_read, sysaid_write, reads and writes apart; call one with {"operation": "", "arguments": {...}} REST base https://cotlet.dev/api/v1/sysaid, each operation at its own route, e.g. POST /api/v1/sysaid/records/{record_id}/notes Auth Authorization: Bearer . Listing endpoints and schemas needs no key; calling an endpoint needs one. Over MCP the input schemas come with sign-in. Operations search_service_records, get_service_record, list_service_record_notes, list_field_values, list_agents_and_groups, create_service_record, update_service_record, assign_service_record, add_note, send_message, resolve_service_record, merge_service_records Confirm create_service_record, assign_service_record, add_note, send_message, resolve_service_record, merge_service_records (by default the user approves each call; the user can switch this off per tool, e.g. for scheduled automations) Markdown https://cotlet.dev/integrations/sysaid-api-mcp-server.md How access works: 1. The user signs up at https://cotlet.dev/app/signup?app=sysaid, requests SysAid in the Cotlet console and creates an API key there. 2. The user signs in to SysAid once in their Cotlet Cloud Browser (their own Chrome in the cloud, opened from the console) and enables SysAid for agents. An agent cannot do this step. 3. The API key goes into the MCP client or the REST call as a bearer token. Fits: people who want a hosted SysAid server that someone else maintains, including non-developers. Policy: Cotlet never stores passwords, never solves CAPTCHAs, never bypasses MFA. Company: legal details in the Terms of service at https://cotlet.dev/terms. Contact contact@cotlet.dev. Sign-in: the user signs in to SysAid in their own Cloud Browser, a Chrome Cotlet runs for them in the EU; password saving is off, the profile is AES-256-GCM encrypted, and agents get SysAid only after the user enables it. Calls are requests from that browser's IP with its cookies, each listed in the user's Background activity. Disable for agents, signing out in the browser or Reset browser cuts access. Cotlet is run by Take Group sp. z o.o. (EU VAT PL6342984273). API key: holds no SysAid login or cookies, only asks Cotlet to run a tool. Each key is scoped to chosen apps and tools, read only or read and write. Actions that reach other people wait for the user's approval by default, so a leaked key cannot post or message as the user. Every call is in the activity log; deleting the key ends access at once. Terms: the user stays responsible for following SysAid's terms; Cotlet is not affiliated with SysAid. ``` ## What can an AI agent do in SysAid? Cotlet is best for IT teams on SysAid who want an AI agent to triage, annotate, resolve and merge tickets without running or fixing a server. - **[Triage new service records](https://cotlet.dev/integrations/sysaid-api-mcp-server/triage-new-service-records.md)** (runs: daily): "Go through new SysAid tickets. Set priority and category from what the requester wrote, assign network problems to the Network group and access requests to IT Support, and leave an internal note with the reason. Leave unclear ones for me." → `search_service_records`, `get_service_record`, `list_service_record_notes`, `list_field_values`, `list_agents_and_groups`, `update_service_record`, `assign_service_record`, `add_note` - **[Resolve tickets the requester confirmed](https://cotlet.dev/integrations/sysaid-api-mcp-server/resolve-solved-tickets.md)** (runs: daily): "Find SysAid tickets in Pending where the requester wrote that it works now. Resolve each with a short solution from the notes and list the ones where the answer is unclear." → `search_service_records`, `list_service_record_notes`, `get_service_record`, `resolve_service_record` - **[Merge duplicate tickets](https://cotlet.dev/integrations/sysaid-api-mcp-server/merge-duplicate-tickets.md)** (runs: weekly): "Find open SysAid tickets about the same problem, for example five people reporting the same outage. Merge each group into the oldest ticket and keep the notes." → `search_service_records`, `get_service_record`, `list_service_record_notes`, `merge_service_records` - **List overdue tickets by assignee** (runs: weekly): "Every Monday, list open SysAid tickets past their due date, grouped by assignee, oldest first." → `search_service_records`, `get_service_record` - **Keep requesters updated on open tickets** (runs: daily): "For every open SysAid ticket with no update in 3 days, read the notes and send the requester a short status message. Show me the drafts first." → `search_service_records`, `list_service_record_notes`, `send_message` ## Can SysAid automations run on a schedule in n8n, Make or Zapier? Yes. Cotlet does not replace your automation platform: it gives it a SysAid connection it does not have, with the same API key as your agent. Write actions ask for your OK by default; switch that off in your dashboard for the tools you choose, for example to triage new service records, and the schedule runs on its own. Cotlet runs in the cloud, so it keeps going while your computer is off. | Where | How to connect | How to schedule | |---|---|---| | Your AI agent | Add https://cotlet.dev/mcp/v1 with your API key. | A scheduled agent run, for example a Claude Code routine. | | n8n | MCP Client node with https://cotlet.dev/mcp/v1, or an HTTP Request node with the endpoint's method and URL, such as GET https://cotlet.dev/api/v1/sysaid/service-records/search. | Schedule Trigger node. | | Make | HTTP module: the endpoint's method and URL with an Authorization: Bearer header, and a JSON body for POST, PUT and PATCH. | Scenario schedule. | | Zapier | Webhooks by Zapier, Custom Request: the same method, URL, header and body. | Schedule by Zapier trigger. | | Your own script | GET https://cotlet.dev/api/v1/sysaid/service-records/search with your API key. | cron or GitHub Actions. | ## Tools **For AI agents:** Every endpoint and its schema is public. The 12 endpoints on this page, with parameters and example responses, can be listed without an account. Calling one returns 401 without an API key and 403 while the key has no access to SysAid. ### search_service_records List the records in your SysAid queue that match a text search and filters. Access: read. REST: `GET /api/v1/sysaid/service-records/search`. MCP: `sysaid_read → search_service_records`. | Parameter | Type | Required | Description | |---|---|---|---| | `query` | string | no | Text to find in ID, title, description and notes, like the search field above the queue. | | `type` | string | no | incident, request, problem or change. | | `status` | string | no | Status name as list_field_values returns it, for example Open or Pending. | | `priority` | string | no | Priority name as list_field_values returns it. | | `assignee` | string | no | Name of an agent from list_agents_and_groups, or unassigned. | | `created_since` | string | no | ISO date. Only records created on or after it. | | `sort_by` | string | no | A queue column name, for example Due Date or Priority. Sorted ascending unless sort_dir is desc. | | `sort_dir` | string | no | asc or desc. | | `cursor` | string | no | Next page cursor from the previous call. | Returns one page of records with ID, type, title, status, priority, assignee, requester, due date and creation time, plus next_cursor while more remain. Filters combine: a record must match all of them, as with column filters in the queue. Your agent sees the records your SysAid account can see. Example response: ```json { "records": [ { "id": 48230, "type": "incident", "title": "VPN drops every hour", "status": "Open", "priority": "Priority 2", "assignee": null, "request_user": "Lena Ortiz", "due_date": "2026-10-26T17:00:00Z", "created_at": "2026-10-22T21:14:00Z" }, { "id": 48244, "type": "request", "title": "New laptop for onboarding", "status": "Open", "priority": "Priority 3", "assignee": null, "request_user": "Sam Okafor", "due_date": "2026-10-30T17:00:00Z", "created_at": "2026-10-23T06:02:00Z" } ], "next_cursor": null } ``` ### get_service_record Read one service record with its fields. Access: read. REST: `GET /api/v1/sysaid/records/{record_id}/service-record`. MCP: `sysaid_read → get_service_record`. | Parameter | Type | Required | Description | |---|---|---|---| | `record_id` | integer | yes | Service record ID from search_service_records. IDs are unique across incidents, requests, problems and changes. | Returns the record as the record page shows it: title, description, type, status, priority, impact, category, assignee, group, request user, company, department, due date, reopen counter, last modified time and who modified it. Notes come from list_service_record_notes. Fields your role cannot view are left out. Example response: ```json { "id": 48230, "type": "incident", "title": "VPN drops every hour", "description": "The VPN client disconnects about every 60 minutes since Monday. Reconnecting works. Windows 11 laptop, working from home.", "status": "Open", "priority": "Priority 2", "impact": "Medium", "category": "Access > VPN", "assignee": null, "group": null, "request_user": "Lena Ortiz", "company": "Northwind", "department": "Finance", "due_date": "2026-10-26T17:00:00Z", "reopen_counter": 0, "modified_at": "2026-10-22T21:14:00Z", "modified_by": "Lena Ortiz" } ``` ### list_service_record_notes Read the notes written on a service record. Access: read. REST: `GET /api/v1/sysaid/records/{record_id}/service-record-notes`. MCP: `sysaid_read → list_service_record_notes`. | Parameter | Type | Required | Description | |---|---|---|---| | `record_id` | integer | yes | Service record ID from search_service_records. IDs are unique across incidents, requests, problems and changes. | | `cursor` | string | no | Next page cursor from the previous call. | Returns notes oldest first with author, time, text and whether the note is shared with the request user. Notes are internal unless the author shared them. Journey events that are not notes, such as status changes, are not included. Example response: ```json { "notes": [ { "note_id": 9120, "author": "Jordan Reyes", "created_at": "2026-10-22T22:40:00Z", "shared_with_requester": false, "body": "Checked the VPN logs. The session timeout on the gateway is set to 60 minutes." }, { "note_id": 9131, "author": "Lena Ortiz", "created_at": "2026-10-23T07:15:00Z", "shared_with_requester": true, "body": "Thanks, it has not dropped since this morning." } ], "next_cursor": null } ``` ### list_field_values List the values your SysAid offers for a field, as its dropdown shows them. Access: read. REST: `GET /api/v1/sysaid/field-values`. MCP: `sysaid_read → list_field_values`. | Parameter | Type | Required | Description | |---|---|---|---| | `field` | string | yes | status, priority, impact or category. | Returns the values your account uses, in the order SysAid lists them. Values differ from account to account, so call this before filtering or updating by name. Categories come with their sub-categories as "Primary > Secondary". Example response: ```json { "field": "priority", "values": [ "Priority 1", "Priority 2", "Priority 3", "Priority 4" ] } ``` ### list_agents_and_groups List the agents and groups a record can be assigned to. Access: read. REST: `GET /api/v1/sysaid/agents-and-groups`. MCP: `sysaid_read → list_agents_and_groups`. | Parameter | Type | Required | Description | |---|---|---|---| | `kind` | string | no | agent or group. Both when left out. | | `query` | string | no | Part of a name to search for. | Returns each agent or group with its ID and name, and for groups the agents inside. Which of them can take a record depends on how assignees are configured for your account: a user, a group, or both. Example response: ```json { "groups": [ { "id": "g332", "name": "IT Support", "members": [ "Jordan Reyes", "Priya Nair" ] }, { "id": "g341", "name": "Network", "members": [ "Marcus Hill" ] } ], "agents": [ { "id": "u2342", "name": "Jordan Reyes" }, { "id": "u2351", "name": "Priya Nair" }, { "id": "u2360", "name": "Marcus Hill" } ] } ``` ### create_service_record Open a new incident or request. Access: write, asks the user first. REST: `POST /api/v1/sysaid/service-records`. MCP: `sysaid_write → create_service_record`. | Parameter | Type | Required | Description | |---|---|---|---| | `type` | string | yes | incident or request. | | `title` | string | yes | Title of the record. | | `description` | string | no | What happened or what is needed. | | `request_user` | string | no | Name of the person the record is for. Your own account when left out. | | `priority` | string | no | Priority name from list_field_values. The default priority of your SysAid when left out. | Creates the record with the template defaults of its type and returns its ID. Your SysAid rules then run on it: routing rules, priority rules and any notifications you set up can reach the request user and agents. By default you confirm each call; you can switch that off for this tool. Example response: ```json { "id": 48251, "type": "request", "title": "Access to the shared finance mailbox", "status": "Open", "priority": "Priority 3", "request_user": "Sam Okafor", "created_at": "2026-10-23T08:30:00Z" } ``` ### update_service_record Change the title, description, priority, impact or category of a record. Access: write. REST: `PATCH /api/v1/sysaid/records/{record_id}/service-record`. MCP: `sysaid_write → update_service_record`. | Parameter | Type | Required | Description | |---|---|---|---| | `record_id` | integer | yes | Service record ID from search_service_records. IDs are unique across incidents, requests, problems and changes. | | `title` | string | no | New title. | | `description` | string | no | New description. Replaces the old one. | | `priority` | string | no | Priority name from list_field_values. | | `impact` | string | no | Impact name from list_field_values. | | `category` | string | no | Category from list_field_values, "Primary > Secondary" for a sub-category. | | `reason` | string | no | Why the priority changes. Needed when your SysAid requires an audit trail for manual priority changes. | Returns the record after the change. Only the fields you pass change, and only fields your role may edit; which fields an agent can edit is set in the Template Designer. SysAid locks a record while someone edits it, so the call can fail and be retried. Every change is recorded in the record's Journey. The call sends no message itself and a second call with the old value undoes it, so it does not wait for your OK. Status and assignee have their own tools because they reach other people. Example response: ```json { "id": 48230, "title": "VPN drops every hour", "status": "Open", "priority": "Priority 2", "impact": "Medium", "category": "Access > VPN", "modified_at": "2026-10-23T08:41:00Z" } ``` ### assign_service_record Assign a record to an agent, a group, or both. Access: write, asks the user first. REST: `POST /api/v1/sysaid/records/{record_id}/service-record/assign`. MCP: `sysaid_write → assign_service_record`. | Parameter | Type | Required | Description | |---|---|---|---| | `record_id` | integer | yes | Service record ID from search_service_records. IDs are unique across incidents, requests, problems and changes. | | `assignee` | string | no | Agent name from list_agents_and_groups. | | `group` | string | no | Group name from list_agents_and_groups. | Returns the assignee and group after the change. Pass whichever your account uses; passing neither fails. The new assignee gets the instant message SysAid sends when a record is assigned to them, and the assignment appears in the Journey highlights. By default you confirm each call; you can switch that off for this tool. Example response: ```json { "id": 48230, "assignee": "Jordan Reyes", "group": "Network", "assigned_count": 1, "modified_at": "2026-10-23T08:42:00Z" } ``` ### add_note Write a note on a service record, internal by default. Access: write, asks the user first. REST: `POST /api/v1/sysaid/records/{record_id}/notes`. MCP: `sysaid_write → add_note`. | Parameter | Type | Required | Description | |---|---|---|---| | `record_id` | integer | yes | Service record ID from search_service_records. IDs are unique across incidents, requests, problems and changes. | | `body` | string | yes | Text of the note, 5,000 characters at most, no emojis. | | `share_with_requester` | boolean | no | true shows the note to the request user. A shared note cannot be made internal again. Default false. | Returns the note ID and whether it is internal or shared. Notes can notify users and groups your admin set up for "Notes are added", and an @mention in the text emails the person named. A shared note reaches the requester. By default you confirm each call; you can switch that off for this tool. Example response: ```json { "note_id": 9140, "record_id": 48230, "visibility": "internal", "created_at": "2026-10-23T08:43:00Z" } ``` ### send_message Email an agent, a user or a group from inside a service record. Access: write, asks the user first. REST: `POST /api/v1/sysaid/records/{record_id}/messages`. MCP: `sysaid_write → send_message`. | Parameter | Type | Required | Description | |---|---|---|---| | `record_id` | integer | yes | Service record ID from search_service_records. IDs are unique across incidents, requests, problems and changes. | | `to` | string[] | yes | IDs of users and groups, "u" before a user ID and "g" before a group ID, for example u2342 or g332. | | `subject` | string | yes | Subject line. | | `body` | string | yes | Message text. | | `cc` | string[] | no | IDs to copy, in the same format as to. | Sends an email notification from the record and returns the recipients. The message is logged on the record. An email cannot be recalled once sent. By default you confirm each call; you can switch that off for this tool. Example response: ```json { "record_id": 48230, "sent_to": [ "u2342" ], "cc": [], "subject": "Update on your VPN ticket", "sent_at": "2026-10-23T08:45:00Z" } ``` ### resolve_service_record Resolve a record with a solution and closure information. Access: write, asks the user first. REST: `POST /api/v1/sysaid/records/{record_id}/service-record/resolve`. MCP: `sysaid_write → resolve_service_record`. | Parameter | Type | Required | Description | |---|---|---|---| | `record_id` | integer | yes | Service record ID from search_service_records. IDs are unique across incidents, requests, problems and changes. | | `solution` | string | yes | Short summary of what fixed it. Usually shared with the request user. | | `closure_information` | string | yes | How the record was closed, for example Solved On-site. | | `status` | string | no | A closed status from list_field_values. Your default resolved status when left out. | | `share_with_requester` | boolean | no | true tells the request user the solution. Default false. | Returns the closed record. Solution and closure information are required, as on the Resolution tab. Closing a record sends the request user a satisfaction survey link when you enabled the survey in SysAid, and a shared solution reaches them too. You need edit permission on the record. By default you confirm each call; you can switch that off for this tool. Example response: ```json { "id": 48417, "status": "Closed", "closure_information": "Solved On-site", "shared_with_requester": true, "resolved_at": "2026-10-23T09:05:00Z" } ``` ### merge_service_records Merge duplicate records into one primary record. Access: write, asks the user first. REST: `POST /api/v1/sysaid/primaries/{primary_id}/service-records/merge`. MCP: `sysaid_write → merge_service_records`. | Parameter | Type | Required | Description | |---|---|---|---| | `primary_id` | integer | yes | ID of the record that stays in the queue. | | `secondary_ids` | integer[] | yes | IDs of the records merged into it. At most 49, so the whole merge is up to 50 records. | | `include` | string[] | no | What to copy into the primary record: attachments, messages, notes, activities. Nothing when left out. | | `status` | string | no | Status of the primary record after the merge, from list_field_values. | | `reason` | string | yes | Why the records are merged. Logged in the Journey. | Returns the primary record and the merged IDs. The merged records are closed and archived with the status "Merged-Archived", and the merge is written in the Journey of all of them. Your SysAid account needs the Merge service records permission. A merge cannot be undone. By default you confirm each call; you can switch that off for this tool. Example response: ```json { "primary_id": 48230, "merged_ids": [ 48236, 48241 ], "included": [ "notes", "attachments" ], "status": "Open", "merged_at": "2026-10-23T09:20:00Z" } ``` ## How do I connect SysAid to Claude Code, Codex or Cursor? Connecting SysAid takes three steps: sign up, sign in to SysAid once in your Cloud Browser and enable it for agents, then add one MCP server or call the REST API with the same key. ### Connect SysAid to your agent. 1. **Create an account** Sign up and add SysAid in the console. Your API key is there too. 2. **Sign in to SysAid in your Cloud Browser** Open your Cloud Browser in the console: your own Chrome in the cloud. Sign in to SysAid there yourself, the way you always do, then press Enable for agents, read only or read and write. We never save your password, and your agent keeps working even when your computer is off. 3. **Add Cotlet to your agent** Paste the snippet for your client. The same server and key serve every app you connect, so you do this once. Claude Code: ``` claude mcp add --transport http cotlet \ https://cotlet.dev/mcp/v1 \ --header "Authorization: Bearer $COTLET_API_KEY" ``` Cursor: ``` { "mcpServers": { "cotlet": { "url": "https://cotlet.dev/mcp/v1", "headers": { "Authorization": "Bearer ${COTLET_API_KEY}" } } } } ``` Codex: ``` # ~/.codex/config.toml [mcp_servers.cotlet] url = "https://cotlet.dev/mcp/v1" bearer_token_env_var = "COTLET_API_KEY" ``` 4. **Ask your agent** Ask in plain words. Your agent finds the SysAid tools on the server and calls them for you; anything that reaches other people waits for your OK unless you switch that off for a tool. ``` Go through new SysAid tickets. Set priority and category from what the requester wrote, assign network problems to the Network group and access requests to IT Support, and leave an internal note with the reason. Leave unclear ones for me. ``` ### Call SysAid from your scripts. 1. **Export your API key** Your scripts use the same API key as your agent. Keep it in an environment variable, never in your code. ``` export COTLET_API_KEY="cotlet_..." ``` 2. **Call a tool** Every tool is an endpoint under /api/v1/sysaid with its own method and path, listed with the endpoints above. Path parameters go in the URL; the other parameters go in the query for GET and DELETE and in a JSON body otherwise. ``` curl -X POST https://cotlet.dev/api/v1/sysaid/records/48230/notes \ -H "Authorization: Bearer $COTLET_API_KEY" \ -H "Content-Type: application/json" \ -d '{"body":"Gateway session timeout is 60 minutes, matching the reported drops. Network group to raise it.","share_with_requester":false}' ``` 3. **Read the result** You get plain JSON back, ready for your script. A failed call costs nothing. ``` { "note_id": 9140, "record_id": 48230, "visibility": "internal", "created_at": "2026-10-23T08:43:00Z" } ``` ## Why use Cotlet for SysAid? **Built for agents** - One MCP server for every app you connect. - The same tools as a REST API for scripts and cron jobs. - Works with Claude Code, Codex and Cursor. **Your login stays yours** - You sign in to SysAid yourself, in your own Cloud Browser. We never save your password; the profile is encrypted with AES-256-GCM, the cipher 1Password uses. - A+ on Qualys SSL Labs, securityheaders.com and Mozilla Observatory. - The model never sees a login. - No stored passwords, no CAPTCHA solving, no MFA bypass. **You stay in control** - Scope each API key: its apps, its tools, read only or read and write. - Anything that reaches other people waits for your OK, so a leaked key cannot post or message as you. - Every background request listed in your Background activity. Disable for agents in one click. **Kept working for you** - We test every integration every 6 hours. - When SysAid changes, the tool pauses until we fix it. - Failed calls cost nothing. ## Is it safe to connect SysAid to Cotlet? Yes. You sign in to SysAid yourself, in your own Cloud Browser, and we never save your password. Your agents only get SysAid once you enable it, and every background request is listed. The browser profile is stored encrypted with AES-256-GCM, the same cipher 1Password uses for its vaults and Apple for iCloud Keychain. Independent public scanners grade cotlet.dev A+ and find it clean; click a result to rerun it yourself. - **A+ on Qualys SSL Labs**: Encryption in transit: TLS setup and certificates, on all four server addresses. [Live result](https://www.ssllabs.com/ssltest/analyze.html?d=cotlet.dev) - **A+ on securityheaders.com**: Browser protections sent with every page, all six headers present. [Live result](https://securityheaders.com/?q=cotlet.dev&followRedirects=on) - **A+ on Mozilla Observatory**: Mozilla's web security baseline: score 120 of 100, 12 of 12 tests passed. [Live result](https://developer.mozilla.org/en-US/observatory/analyze?host=cotlet.dev) - **Clean on Sucuri SiteCheck**: No malware, spam or defacement, and not on any of 9 blocklists, Google Safe Browsing included. [Live result](https://sitecheck.sucuri.net/results/cotlet.dev) [How Cotlet protects your access](https://cotlet.dev/security.md) ### Common concerns **Who runs Cotlet?** Cotlet is run by Take Group, a Polish software company working since 2019. Take Group runs about 3,200 websites on its own systems and has its own DevOps team for infrastructure security. We built and used integrations like this inside the company for years before opening them as Cotlet. **Is this an official SysAid integration?** No, Cotlet is independent of SysAid. SysAid's own API is too limited for this work. Cotlet works through your own SysAid account, the way you use SysAid in the browser, so you need no partner approval and no developer setup. **What about client data and GDPR?** Cotlet is run from the EU and follows the GDPR. Cloud Browsers run in Finland, a Tier 1 country in the ITU Global Cybersecurity Index 2024. Data passes through a call and is not kept after it. **Can I start with read only?** Yes. Enable the app for agents as read only, or make the API key read only, and anything that reaches other people waits for your OK unless you switch that off per tool. **Is it reliable?** Every Cotlet service is checked every 3 minutes from Europe, North America, Asia and Australia. The live results and any outage are public at status.cotlet.dev. **How do I stop?** Press Disable for agents next to SysAid in your console: your agents lose access at once and you stay signed in. Signing out of SysAid in the browser works too, and Reset browser deletes the whole profile. ## Is there a SysAid MCP server on GitHub? SysAid has no official MCP server, so the realistic option is its own API. An administrator creates an app key, your code requests access tokens with it, and you write and host the tool layer for each call. Cotlet hosts that layer for you as an MCP server and a REST API, signed in as your agent user, and our team keeps it working. | | SysAid API | Cotlet | |---|---|---| | Setup | An administrator creates an app key under Connect > Manage App Keys, you request access tokens with it and write the code for each call | Sign up, sign in to SysAid once, add one MCP server or API key | | When SysAid changes | You read the changelog and update your code | Our team tests it daily and fixes it for you; failed calls are free | | Your SysAid access | App key client ID and secret in the config of your own code | Signed in inside your own Cloud Browser in the EU, profile encrypted, only for the apps you enable, disabled for agents in one click | | When access expires | Access tokens last 24 hours by default and 30 days at most; your code asks for a new one | Your Cloud Browser keeps you signed in; if SysAid logs you out, your agent gets a link to sign in again | | Upkeep | You host, monitor and update the code | Nothing to host or update | | Where it runs | Wherever you host your code | Hosted: Claude Code, Codex, Cursor, n8n and scripts, also on a schedule | | Price | Your own build and hosting time | Free 7-day trial, then pay-as-you-go credit packs, no subscription | ### Which one fits you **Pick Cotlet if** - you are not a developer, or you do not want to maintain a server - you need it to keep working when SysAid changes, without checking it yourself - your agent or a script should run it on a schedule, also while your computer is off **Pick an open-source server if** - you are comfortable installing, updating and fixing it yourself - you want your sign-in to stay on your own computer - you only need it now and then, from one MCP client ## How much does the SysAid API cost? Free 7-day trial with 2,000 credits, no card needed. After that, the SysAid API is pay as you go with no limit on apps: Credit packs from $29 for 5,000 credits, one-time, no subscription. A successful call uses 10 credits (about $0.04 to $0.06), your Cloud Browser uses 50 credits a day while it has an app enabled for agents, however many apps that is, and an agent driving the browser itself uses 5 credits a minute. Credit packs stay valid for 12 months and stack, so unused credits carry over. | Credits | Price, one time | Calls at 10 credits | Per 1,000 credits | |---|---|---|---| | 5,000 | $29 | 500 | $5.80 | | 15,000 | $79 | 1,500 | $5.27 | | 32,000 | $149 | 3,200 | $4.66 | | 60,000 | $249 | 6,000 | $4.15 | Only successful calls use credits; failed calls and timeouts cost nothing. At a balance of 0 calls pause, never a surprise charge. Authenticate with the `Authorization: Bearer` header. [See full pricing](https://cotlet.dev/pricing.md) ## How Cotlet holds your access Cotlet hosts MCP servers and REST APIs for apps with no usable API. Your agent works in your own SysAid account. - **Company details:** Cotlet is run by Take Group sp. z o.o., a company registered in Poland. Its full address and registration numbers are in the Terms of service. [Terms of service](https://cotlet.dev/terms) - **Your sign-in:** You sign in to SysAid yourself, in your own Cloud Browser: a Chrome we run for you in the EU, one per app. We never save your password (password saving is off), the profile is stored encrypted with AES-256-GCM, and your agents get SysAid only after you enable it. When SysAid signs you out, your agent gives you a link to sign in again. [Security](https://cotlet.dev/security.md) - **Revoking access:** Press Disable for agents next to SysAid, sign out of SysAid in your Cloud Browser, or reset the browser. Every background request is listed in your Background activity. Actions that reach other people wait for your OK unless you switch that off per tool. - **What we never do:** Store passwords, solve CAPTCHAs or bypass MFA. - **SysAid's terms:** You use your own SysAid account and stay responsible for following SysAid's terms. Cotlet is independent and not affiliated with SysAid. [Terms](https://cotlet.dev/terms) - **Contact:** Questions about the company, security or an app: [contact@cotlet.dev](mailto:contact@cotlet.dev) ## Frequently asked questions **How do I get access?** Sign up free, open SysAid in the console and press Request access. Then you create your API key and connect SysAid there. **Do I need to be technical?** No. You sign in to SysAid once in your Cloud Browser, a normal Chrome you open from the console, and paste one command into your agent, or one URL into n8n. Your agent can walk you through it. There is no server to install, update or fix. **Is it safe to connect SysAid to Cotlet?** Yes. You sign in to SysAid yourself, in your own Cloud Browser in the EU, and we never save your password. Your agents only get SysAid once you enable it, every background request is listed, and the browser profile is stored encrypted with AES-256-GCM, the cipher 1Password uses for its vaults. The AI model never sees a login, posts and messages wait for your OK, and Disable for agents cuts access in one click. Independent scanners grade cotlet.dev A+ on Qualys SSL Labs, securityheaders.com and Mozilla Observatory; live results are on https://cotlet.dev/security. **Is a hosted server safer than a local one? My SysAid sign-in would leave my computer.** On Cotlet you sign in inside your own Cloud Browser, which only you open, and its profile is stored encrypted with AES-256-GCM in the EU. Agents get only the apps you enable, and every background request is listed. A local server keeps your SysAid cookie in a plain file on your computer, readable by any program you run, and stops when your computer is off. **Why does Cotlet send requests instead of clicking in my browser?** To be fast, Cotlet doesn't click through SysAid's pages. It sends the same requests your browser would, from your browser's IP with its cookies, without opening a window. SysAid sees the same browser and IP you signed in with, and every request is listed in your Background activity. **What if someone gets my Cotlet API key?** The key holds no SysAid login or cookies, it only asks Cotlet to run a tool. It can call only the apps and tools you gave it, and a read-only key changes nothing. Anything that reaches other people, like posts, comments or messages, waits for your OK in the dashboard by default, so a leaked key cannot post or message as you. When you switch approval off for a scheduled job, give that job its own key limited to that one tool. Every call is in your activity log, and deleting the key ends access at once. **Why a signed-in browser and not OAuth, like other integration platforms?** SysAid offers no OAuth token you can simply grant for these tools: its official API leaves them out or needs a developer app, a plan or an approval first (see the official API section above). That is why Cotlet sets the limits itself: per key, per tool, with your approval before anything reaches other people. Cotlet is run by Take Group sp. z o.o., an EU company (VAT PL6342984273). **Do I need an app key or administrator rights?** No app key. Cotlet works in your own SysAid agent login, and what your agent can do follows your permissions: merging needs the Merge service records permission, resolving needs Edit permission on the record, and fields you may not edit stay locked. The SysAid API needs a Spaces account and an app key, and its getting-started guide lists administrator permissions as a requirement. **Does it work on SysAid Classic?** The tools follow the SysAid Spaces queue and the record Journey. Classic accounts use a different Help Desk list and record page, and are not covered. Accounts in hybrid mode, with both views, use the Spaces side. **Can my agent post or send messages in SysAid without asking me?** No. Every call to create_service_record, assign_service_record, add_note, send_message, resolve_service_record or merge_service_records waits for your OK by default. For scheduled automations you can switch confirmation off per tool in your dashboard, for example only for approvals. update_service_record runs without asking, because it sends nothing to anyone and one call undoes it. **Can I use the SysAid API in n8n?** Yes. Add https://cotlet.dev/mcp/v1 with your API key in n8n's MCP Client node, or call its endpoints under https://cotlet.dev/api/v1/sysaid from the HTTP Request node. --- 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.dev is built by Bart Krawczyk and Jake Slugocki, the founders of Take Group sp. z o.o., ul. Wincentego Janasa 4, 40-855 Katowice, Poland. KRS 0000871398, NIP 6342984273, VAT EU: PL6342984273. [About us](https://cotlet.dev/about.md) 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.