MCP Servers

How it works

One Assistant, Many Servers

An MCP server (Model Context Protocol) gives an AI assistant a clear, limited set of actions on one system. The assistant asks, the server checks and answers — nothing more.

The assistant talks to each MCP server in turn: it sends a request, the server does the work and answers.

For Our Own Tools

We build MCP servers for the systems we run every day, so our assistants work with real data instead of copy and paste.

For Your Business

The same servers are available to customers, and we build new ones for your CRM, database, files or internal API.

Fully Developed In-House

Every MCP server is designed, written and tested by the SYNTHETIXMIND team — with guardrails, audit logs and human approval built in.

MCP Servers

Our MCP Servers

Available on request. Ask us for a demo or for access — we set it up with you.

MCP Server v0.1.1

Mautic MCP

Developer Tools / Marketing Automation

Connects Claude Code to your self-hosted Mautic 5 and turns lead research into personalised outreach emails — prepared by AI, approved by you.

One-call lead upsert with fields, tags, company and research note
Fills only the [[slots]] of your own Mautic templates
Drafts stored in Mautic, linked to the contact
Two-step send with a one-time confirm token, DNC check and daily cap
Analytics per email and template, plus the lead funnel

Nothing is sent without your explicit OK. The server runs locally, reads credentials only from the environment, talks only to your own Mautic and records every write and send in a local audit log.

Request a demo → Request access

TypeScript · Node.js ≥ 20 · Windows, macOS, Linux · available on request

MCP Server v0.1.0

SynthProfile MCP

Developer Tools

Lets Claude Code generate realistic, reproducible user profiles from the SynthProfile API — test and demo data without privacy risk.

"20 Swiss women aged 25–45 as CSV" in one sentence
Filters for gender, nationality, age range and fields
Reproducible seeds: same seed and filters, same people
Up to 200 profiles per call, saved as JSON or CSV
Quota aware, typed errors with request id, ETag caching

The API key is only sent in the request header — never logged, returned or written to disk. Inputs are checked before any quota is spent, CSV exports are protected against formula injection, and files are never overwritten silently.