Six connections, all writing real records

Connected to where the work already happens

Gmail, Calendly, a REST API, MCP and your own Anthropic key. Each one creates or updates real CRM records rather than just showing you a feed.

Gmail

Send from your own address, keep the thread

Connect your own Gmail, or one shared mailbox for the whole account. Mail you send goes out through Gmail as normal, so it lands in your Sent folder and looks like you sent it, because you did.

Replies sync back automatically every few minutes
Threads attach to the contact as a conversation, and appear in a shared inbox
Quoted reply text is stripped, so the thread stays readable
Sent and received mail is written into the contact's activity timeline
An inbound reply notifies whoever sent the last message

Access tokens are encrypted at rest. Disconnecting deactivates the connection rather than deleting your mail history.

Calendly

A booking becomes a deal, not a calendar entry

Connect your Calendly organisation and choose which event types should reach the CRM. Everything else is ignored, so an internal one-to-one does not create a sales record.

The invitee is matched by email, or created as a new contact
Their latest open deal is reused, or a new one is opened in your first open stage
A confirmed appointment is created with the meeting link
Both are assigned to the teammate who hosted the booking
A cancellation in Calendly cancels the appointment here

Incoming callbacks must come from Calendly's published address range and carry a valid signature.

MCP

Connect an AI assistant, on your terms

The CRM runs a remote MCP server. Connect an MCP-compatible assistant such as Claude Code and it can look things up in your CRM and, if you allow it, create and update records, as you, within your permissions.

What it can reach

Contacts, deals, offerings and appointments: list, read, create and update, and cancel an appointment
Comments on contacts and deals: read and post
Files: list what is attached, and upload a new one
A deal's additional contacts and offerings, and assigning by a teammate's email

What it can never do

Delete anything. There is no delete tool and no delete permission, so no instruction can reach one.
Write unless you allow it. A new connection is read-only. Write permissions sit in their own panel and need an extra confirmation.
Go beyond your role. Every call is checked as you, when it is made. Hidden fields stay hidden.
Reach another account, or change more than one record in a call.

How to connect, with every tool

Changes show up in history as Your Name (MCP). An assistant reads whatever is in your records, so connect only assistants you trust.

Your Anthropic key, for SWARECO AI

SWARECO AI, the assistant built into the CRM, runs on your account's own Anthropic API key. Model use is billed to you, with a monthly dollar budget you set. The key is encrypted at rest, and only its last four characters are ever shown.

It answers from your records, shows what it read, and changes nothing until someone clicks Confirm.

About SWARECO AI

REST API

Push contacts, deals and appointments in from a landing page, an automation tool or your own product. Issue a bearer token from settings, revoke it whenever you like.

Nested contact details are matched or created for you, new deals land in your first open stage, and an email-domain blocklist keeps obvious junk out.

API documentation

Cloudflare Turnstile

Add your Turnstile keys and every public capture form is protected against automated submissions, verified on the server rather than in the browser. Keys are stored encrypted, and configured per account.

Something else you need connected?

The REST API covers one-way ingest and MCP covers assistants that read and update. Tell us what you are trying to join up and we will tell you honestly whether it is possible now, soon, or not on the cards.

Request a demo Read the docs