Syncro MCP Server

An MCP server for the Syncro (SyncroMSP) REST API, the PSA + RMM platform for MSPs. It lets an AI agent read customers, contacts, tickets with their comments, assets and invoices and, on explicit request, create customers, contacts, tickets and invoices, update tickets, add ticket comments and email invoices.

• Transport: MCP Streamable HTTP at POST /mcp, health probe at GET /health

• Stateless and multi-tenant: credentials arrive on every request as HTTP headers and are never stored; every tool is listed from the first tools/list

• Python 3.12, uv, FastMCP, httpx

• License: Apache-2.0, Copyright 2026 MSPbots.ai

MSPbots Connector

The MCP Gateway built for MSPs: visible, controlled, and your data stays where it belongs.

Get started at connect.mspbots.ai →

MSPbots Connector gives your AI clients one MCP URL to reach your entire MSP stack (RMM, PSA, documentation, security, finance), and gives you control over who can call which tool and a record of everything that was called.

Hosted service: connect.mspbots.ai · Free to use.

Why Connector

Quick start

1. Sign up at connect.mspbots.ai.

2. Connect your vendors. Pick from 150+ connectors and authorize each one on the vendor's own page, or bring your own API keys. No extra vendor accounts needed.

3. Set access. Create roles and decide which tools each role may call. Nothing is allowed until you allow it.

4. Add your MCP URL to your AI client. Copy the URL from your Connector dashboard into Claude, ChatGPT, Cursor, VS Code, Gemini, Codex, or any MCP-capable client.

5. Ask your AI to do real work, and watch every call appear in the audit log.

Features

Unified gateway

• One MCP URL for all your AI clients

• 150+ connectors across the MSP stack

• Custom MCP servers supported, free

• Authorization happens on each vendor's own page; the AI never sees passwords or tokens

• Bring your own credentials: use the vendor API keys you already have

• Multiple accounts per app; connect once, reuse across AI clients

• Tool search: finds the right action for the task

• One sign-in; vendor credentials are injected behind the scenes and OAuth tokens refresh automatically

Visibility

• Audit log for every tool call (who, which vendor, when)

• Usage dashboard: call volume, top vendors, error rate, per-user activity

• Export audit logs to CSV, or stream to Loki, Graylog, or LogScale (SIEM)

• Optional recording of tool arguments and result summaries (off by default, enabled per organization)

Control

• Per-role, per-tool allowlist, deny by default

• owner / admin / member roles

• SCIM provisioning with Entra ID, Okta, JumpCloud, and Google Workspace

Security

• Credentials encrypted one record at a time (AES-256-GCM, per-record key)

• AI clients authenticate with OAuth 2.1 + PKCE

• Vendor responses are scanned for prompt-injection patterns and returned as structured data. This is one layer of defense, not a guarantee against every attack.

• Static egress IP for customer firewall and API allowlisting

Pricing

Free.

Links: connect.mspbots.ai · mspbots.ai

Related MCP server: Simpro MCP Server

Authentication headers

Where to get them:

• In Syncro open Admin -> API Tokens and create a token with the permissions the agent needs: view rights on Customers, Contacts, Tickets, Assets and Invoices for the read tools; create / edit rights only for the areas it should change.

• The subdomain is the first part of the address you log in to Syncro with.

How the key is sent to Syncro: as Authorization: Bearer <token> to https://{subdomain}.syncromsp.com/api/v1/..., never as a query parameter, so it does not appear in URLs or access logs. Values that look like unresolved templates (${...}) are treated as missing.

A request to /mcp without both headers gets HTTP 401 listing them; a subdomain that is not a plain account name gets HTTP 400.

Tools

All tools return a JSON string. Syncro pages its lists with a fixed size per list (customers 100, tickets 50, contacts 50, invoices 25, assets 25; the response's meta.per_page is used when it differs) and, except for invoices, does not let the caller choose it. List tools take per_page (1-100, default: Syncro's own size) and either page or offset, and map that window onto Syncro pages, so any size works. Results carry {count, total_entries, total_pages, page, per_page, offset, has_more, next_page, next_offset}; follow next_page (or next_offset) until has_more is false - no record is skipped or repeated, also when a large page is cut to fit the response size limit (then only next_offset is returned). A few filters the Syncro API does not offer (marked * below) are applied by this server: it reads up to 5 Syncro pages from the start position and returns at most per_page matches; next_offset points to the record right after the last match returned (or after the last record read), so following it until has_more is false returns every match exactly once, also when a result is cut to fit the size limit. scanned_pages names the Syncro pages read.

* applied by this server, as described above.

Errors come back as a JSON envelope instead of an exception:

{"error": {"code": "unauthorized", "message": "Syncro returned HTTP 401 for me: the API key was rejected ...", "retryable": false}}

code is one of not_configured, unauthorized, not_found, invalid_argument, rate_limited, upstream_error. Syncro allows 180 requests per minute per source IP address, so every account served from the same egress IP shares that budget; reads are retried with backoff on 429 (honouring Retry-After), 5xx and network errors, writes only on 429.

Run locally

uv sync
uv run python -m syncro_mcp          # listens on 0.0.0.0:8080

or with Docker:

docker build --platform linux/amd64 -t syncro-mcp:dev .
docker run --rm -p 8080:8080 syncro-mcp:dev

Configuration (environment variables, all optional): MCP_HTTP_HOST (default 0.0.0.0), MCP_HTTP_PORT (default 8080), LOG_LEVEL (default INFO). Credentials are never read from the environment.

Testing example

# list tools
curl -s http://localhost:8080/mcp \
  -H "Content-Type: application/json" \
  -H "Accept: application/json, text/event-stream" \
  -H "X-Syncro-Subdomain: yourcompany" \
  -H "X-Syncro-API-Key: your-syncro-api-key" \
  -d '{"jsonrpc":"2.0","id":1,"method":"tools/list","params":{}}'

# open tickets of one customer
curl -s http://localhost:8080/mcp \
  -H "Content-Type: application/json" \
  -H "Accept: application/json, text/event-stream" \
  -H "X-Syncro-Subdomain: yourcompany" \
  -H "X-Syncro-API-Key: your-syncro-api-key" \
  -d '{"jsonrpc":"2.0","id":2,"method":"tools/call","params":{"name":"syncro_tickets_list","arguments":{"customer_id":123,"resolved":false}}}'

Unit tests (no network access needed):

uv run pytest

Delivery notes

• Built on the published API reference. Every call follows Syncro's OpenAPI document (api-docs.syncromsp.com). Where the older version sent filters that endpoint does not have, they are now mapped to the documented ones (since -> since_updated_at, invoice paid / unpaid) or applied by this server and flagged with scanned_pages.

• Tool count (21). Tool names and required parameters are unchanged.

• Invoice states. Syncro exposes paid / unpaid amounts, not draft / sent / viewed / void states; those values now return a clear invalid_argument instead of being ignored.

• Accepted but ignored. syncro_invoices_email still takes cc_emails, subject and message for compatibility, but does not send them: POST /invoices/{id}/email has no request body (it uses the account's invoice email settings); the result lists them under ignored_params.

• Write tools. The 7 tools marked write change records or contact the customer; their descriptions tell the agent to use them only on explicit request. There are no delete tools.

• No interactive prompts. Older versions asked the user for a date range before an unfiltered ticket list, which a stateless gateway cannot relay; lists now page instead.

License

Apache License 2.0 - see LICENSE and NOTICE.