Let your AI assistant work inside your CRM.
vemix ships an MCP server: connect it once via OAuth — with Claude, ChatGPT or any other MCP client. Then research, draft and create. Companies, contacts, leads, tasks, documents and presentations land straight in vemix — ready to act on.
Research, create, prepare
Your AI assistant researches a prospect and writes the result straight into vemix — and prepares the next step so your team can start right away.
Research
Market, people and context on the prospect — gathered by the assistant.
Create in the CRM
Company, contacts and a lead in the right pipeline — written via MCP.
Prepare the task
A follow-up task with a ready-to-send email draft on the contact.
Generate the deck
A tailored presentation or document — filed in vemix.
Draft, send — and auto-file
Prepare the documents in your AI assistant, send from your own mailbox and BCC your vemix archive address. vemix creates the contact and company and links the email automatically.
Draft in the assistant
Offer, memo or letter in the chat.
Send via M365 / Google
From Outlook or Gmail — BCC the CRM.
Recipient
Receives the mail from your mailbox.
Auto-filed
vemix creates contact & company and links the email.
The MCP toolset
Every action runs in your name, bound to one tenant, and respects your roles and permissions — the assistant only sees and does what you may.
Companies & contacts
Read + writeCreate and update companies, contacts, emails and phone numbers straight from the chat.
Leads & pipelines
Read + writeRead pipelines, create leads in the right stage and move them as the deal progresses.
Tasks with drafts
Read + writeCreate follow-up tasks and prepare the matching email draft so the work is ready to go.
Documents & decks
GenerateGenerate Word documents and PowerPoint presentations and file them on the record.
Contracts & signatures
with the module onDraft contracts and kick off signature requests by tool.
Role- & tenant-bound
Every tool respects roles, ownership and module access — bound to one tenant.
Connected once, governed always
The MCP server uses OAuth 2.1 / PKCE with a tenant picker on consent. Every tool call is permission-checked — and removing a user revokes it instantly.
For server-to-server use (for example an n8n chatbot that creates a contact on a callback request) vemix offers a scoped public API with self-managed keys — separate from the interactive MCP connector.
Frequently asked questions
Which AI assistants work with vemix?
How does an AI assistant connect to vemix?
Can the AI only read, or also create data?
How do email drafts and presentations reach the user?
What about unattended automation?
Put your AI assistant to work in vemix.
Start free and connect the MCP server with API & MCP access.