SysAid logo sysaid.com

Live

SysAid API and MCP server

The SysAid API cannot merge tickets, and you write all the agent code around it yourself. Sign in to SysAid once in your own Cloud Browser, and your AI agent does the work there for you. The same tools work over MCP for agents and as a REST API for scripts.

Sign up free View as Markdown

Not affiliated with SysAid.

SysAid's own API leaves this out. So we run one for you.

SysAid's own API, a GitHub MCP server and Cotlet compared
What you need SysAid's APIGitHub MCP serverCotlet
MCP access, merging No No Yes, 12 tools
Acts as you, signed in 24/7 No No Yes, Cloud Browser
Fixed for you when SysAid changes N/A No Yes, tested every 6h
Runs with your laptop off N/A No Yes, hosted

Checked Oct 23, 2026. Sources: SysAid Developers: Getting Started · SysAid Developers: Authentication Guide · SysAid Developers: Search Service Records · SysAid blog: AI Agent Center

Your own Cloud Browser, on 24/7. Sign in once. We keep it connected.

  1. 01Sign in to SysAid in your own Cloud Browser

  2. 02Connect it for your agents

  3. 03Cotlet keeps it signed in and working

How do I connect SysAid to Claude, ChatGPT or my code?

AI agents connect over MCP, scripts call the REST API. Both reach the same 12 tools with one API key.

For AI agents: MCP

Add Cotlet to your agent once. SysAid and every other app you connect show up as its tools.

  • Claude
  • ChatGPT
  • OpenClaw
  • Hermes
  • GrokBot
  • Cursor
  • n8n
  • Any MCP client
  1. 1

    Add Cotlet to your agent

    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"

    Paste the snippet for your client. The same server and key serve every app you connect, so you do this once.

For scripts: REST API

Every tool is an endpoint under /api/v1/sysaid with its own method and path, such as POST /api/v1/sysaid/records/{record_id}/notes, with the same API key. Our open-source repo has ready scripts to start from.

REST API docs

What can the SysAid API and MCP server do?

12 tools on your own SysAid account. Agents call them as operations of the MCP tools sysaid_read and sysaid_write; scripts call each one at its own REST endpoint, with the same inputs and answers.

API reference
SysAid tools in Cotlet's MCP server and REST API
Tool What it does Access
search_service_records List the records in your SysAid queue that match a text search and filters. read
get_service_record Read one service record with its fields. read
list_service_record_notes Read the notes written on a service record. read
list_field_values List the values your SysAid offers for a field, as its dropdown shows them. read
list_agents_and_groups List the agents and groups a record can be assigned to. read
create_service_record Open a new incident or request. writeasks first
update_service_record Change the title, description, priority, impact or category of a record. write
assign_service_record Assign a record to an agent, a group, or both. writeasks first
add_note Write a note on a service record, internal by default. writeasks first
send_message Email an agent, a user or a group from inside a service record. writeasks first
resolve_service_record Resolve a record with a solution and closure information. writeasks first
merge_service_records Merge duplicate records into one primary record. writeasks first

Scroll the table for all 12 tools.

Ask in plain words. Your agent does the rest.

All SysAid use cases

Is it safe to connect SysAid?

You sign in yourself in your own Cloud Browser, we never save your password, and anything that reaches your readers waits for your OK. The browser profile is encrypted in the EU. Independent scanners grade cotlet.dev A+.

Security overview

How much do the SysAid API and MCP server cost?

One price for both: a tool call costs the same over MCP or REST. Free 7-day trial with 2,000 credits, no card needed. Then one-time credit packs, no subscription, valid 12 months. Each call uses 10 credits, and your Cloud Browser uses 50 credits a day while SysAid is enabled for agents, so 20 calls a day come to 250 credits.

See full pricing
Cotlet credit packs: price, credits and calls at 10 credits each
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.

Questions

Does SysAid have an 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.

How do I get access?

Sign up free, open SysAid under Integrations in the console and press Request access. Your free trial starts with your account, no card needed.

Is the MCP server different from the API?

No, only the way in. Cotlet builds each integration as a REST API and puts an MCP server on top, so both have the same 12 tools, the same inputs and answers, one API key and one price. AI agents such as Claude, ChatGPT or Cursor use MCP; scripts, cron jobs and HTTP steps in n8n, Make or Zapier use the REST API.

What is the Cloud Browser?

Your own Chrome that Cotlet runs for you in the EU, around the clock. You open it from the console, sign in to SysAid yourself and press Enable for agents. Your agent's calls go through it, from its IP with its cookies, so SysAid sees the browser you signed in with. Password saving is off and the profile is stored encrypted with AES-256-GCM.

Can my agent act without asking me?

Not on anything that reaches other people: create_service_record, assign_service_record, add_note, send_message, resolve_service_record, merge_service_records wait for your OK by default. You can switch that off per tool for scheduled runs.

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.

Should I use a SysAid MCP server from GitHub instead?

Pick one if you want the code on your own computer and do not mind the upkeep: you install it, sign it in and fix it when SysAid changes. Pick Cotlet if you want it hosted and kept working for you.

Can I use it in n8n, Make or Zapier?

Yes. Add https://cotlet.dev/mcp/v1 in n8n's MCP Client node, or call the REST endpoints from an HTTP step in Make or Zapier.

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 Cotlet affiliated with SysAid?

No. Cotlet is independent and not affiliated with SysAid.

Give your agent access to SysAid.

Free 7-day trial with 2,000 credits, no card needed.

Sign up free