Integrations, tools & MCP

Connect the systems your operation already runs on.

Email, files, SMS numbers and your own systems connect to the same records your team works from, so information and actions stay on the record. Each connection is authorised for your workspace.

Tell us what you use

How it’s governed

The catalogue

Email, files and your own systems.

Grouped by what each connection brings onto the record.

Communication

Customer conversations and your team’s mailboxes.

SMS & voice numbers

Provisioned in Muvix with A2P registration; texting stays blocked until it’s approved.

Gmail

Send, receive and log email threads on the record.

Outlook

The same for Microsoft 365 mailboxes.

Documents

How files reach the record.

Secure upload links

Time-limited links for customers to send documents straight to the file.

Google Drive

Find files and attach documents to records.

Your systems

Forms, partners, reporting and the tools you already use.

Webhooks

Inbound webhooks for lead capture; outbound connectors with delivery logs.

API

Contacts, tasks and pipeline endpoints for your own systems.

CRM import

Bring contacts and history across from your current CRM.

Need something that isn’t listed? Tell us what you use.

Tell us what you use

How it fits together

Two directions, one set of records.

Integrations bring email, files and your own systems into the workspace. Tools let AI act on the workspace. Both land on the same records, under the same rules.

Integrations

Bring work in

Email

Gmail · Outlook

Files

Google Drive · secure upload links

SMS numbers

Registered for your workspace

Webhooks, API & import

Your own systems and your current CRM

The workspace

One set of records

One record per contact

Profile, documents, messages, tasks

Consent and contact windows

Rules set once, for outreach

Approved knowledge

What AI may answer from

Audit log

Who or what did what

Tools & MCP

Let AI act

Named tools

Read, create, update, move

Granted per capability

At build or at hire

Every call logged

In runs and on the record

Other MCP servers

Attached with their own secrets

In detail

Tools, knowledge and your own systems.

Tools & MCP

AI acts through named tools, not by clicking around a screen.

The Muvix MCP server exposes workspace actions as tools AI can call: read a contact, see where it sits in its journey, create a task, move a stage. Each tool is granted per capability, and each call is attributable.

Tools are granted per capability at build or hire — one that creates leads never moves a closing stage.

Other MCP servers and custom tools can be attached, each with its own secrets.

Tool calls show in runs and, where they change a record, on the record’s timeline.

How tools are governed

Document Intelligence · tools

Illustration

Read a contact and what’s on file

Granted

See where a contact sits in its journey

Granted

Create a follow-up task

Granted

Update a contact’s fields

With review

Move a contact to another stage

Not granted

Last call · ok · 140 ms · Scope: Purchase pipeline · Dallas

Knowledge · Customer FAQ

Illustration

Bound to 2 capabilities · 4 sources

Self-employed income — what we ask for.pdf

Updated 2 May

Indexed

Rate lock policy.docx

Updated 28 Apr

Indexed

Closing costs explainer (2025).pdf

Updated in January

Outdated

Pricing sheet — internal

Not bound to this capability

Restricted

Knowledge

AI answers from what you approved.

Knowledge bases are built from folders, uploaded files and connected documents, with an ingestion status you can see. A stale or failed document shows as such — not as a confident wrong answer.

Approved sources — Guidelines, FAQs, templates and playbooks, organised by team and marked as approved.

Bound per capability — A customer-facing capability uses the customer FAQ; an internal one uses the processing playbook. Neither sees the pricing sheet unless you say so.

Freshness and permissions — Documents carry their status and access rules, and outdated sources are flagged.

Webhooks, API & import

Your own systems, on the same record.

Inbound webhooks capture leads from forms and partners. Outbound connectors send events to your systems. The API covers contacts, tasks and pipelines, and CRM import brings history from where you are today.

Inbound: website forms, lead vendors and partner referrals become a contact with a source.

Outbound: stage changes, document events and tasks go to your reporting or notification tools.

Tokens rotate, and every delivery is logged.

Connectors · Website leads

Illustration

Website lead connector

Inbound · token rotated 3 days ago

Healthy

Last 24 h

62 deliveries · 0 failed

Maps to

Contact · source: Website

Lead received · Jordan Lee

10:02 · purchase · Dallas

201

Lead received · Sam Okafor

09:47 · refinance · Dallas

201

Token rotated by Maria Rodriguez

Yesterday

audit

Keep going

What happens once it’s connected.

Tools and knowledge fall under the same governance as everything else in the workspace.

Governance & control

Tools AI may call sit under the same roles, reviews and audit log as your team. Nothing switches on by itself.

How governance works

Security & trust

How documents reach the record through secure upload links, and what the audit log keeps.

See security

AI agents

The capabilities that call these tools and read this knowledge — and how one is approved for your workspace.

See AI agents

Tell us what your operation runs on.

We’ll show you what connects directly and what runs through webhooks and the API.

Book a demo

Tell us what you use