AI Plugins & MCP
Prerak connects to external AI assistants through the Model Context Protocol (MCP). Once connected, an assistant like Claude or ChatGPT can read and act on your CRM data on your behalf — answering questions, creating records, sending emails, and running tasks through Prerak's 100+ tools.
There are two ways to connect:
| Remote connector (recommended) | Local server (advanced) | |
|---|---|---|
| Works with | Claude (web/Desktop), ChatGPT, any remote MCP client | Claude Desktop, Cursor, other stdio clients |
| Sign-in | Your normal Prerak login + a consent screen | Workspace API key |
| Access scope | One workspace, chosen at consent | Whatever the API key allows |
| Setup | Paste one URL into the assistant | Edit a local config file |
| Revoke | Settings → Integrations → MCP | Delete the key in Settings → Apps |
Remote connector (Claude, ChatGPT)
Your Prerak deployment exposes an MCP endpoint at:
https://<your-prerak-domain>/mcp
No API key is needed — the assistant sends you through Prerak's secure OAuth sign-in the first time it connects.
Claude
- Open Settings → Connectors → Add custom connector (available on Pro, Max, Team, and Enterprise plans).
- Enter the URL above and click Add, then Connect.
- Your browser opens Prerak. Log in if needed, choose the workspace to grant access to, review the permissions, and click Allow.
- In a chat, enable the connector from the tools menu and try: "How many deals do I have closing this month?"
ChatGPT
- Enable Developer mode (Settings → Apps & Connectors → Advanced).
- Create a connector with the MCP server URL above; authentication is detected automatically (OAuth).
- Complete the same Prerak login + workspace consent flow in your browser.
Managing connections
Every connected assistant appears in Settings → Integrations → MCP with the client name, workspace, and connection date. Disconnect one at any time — its access stops immediately. Access is always limited to the single workspace you approved; connect again to grant a different workspace.
Tip: Access tokens expire after one hour and refresh automatically. If an assistant loses access (for example after being disconnected), remove and re-add the connector on the assistant side.
Local server with an API key (advanced)
For clients that launch MCP servers locally over stdio, Prerak's MCP server can authenticate with a workspace API key instead of OAuth.
Warning: An API key grants programmatic access to your workspace data. Treat it like a password, scope it to only what's needed, and revoke it from Settings → Apps if it's ever exposed.
-
In Prerak, create an API key: Settings → Apps.
-
In Claude Desktop, open the MCP server configuration (Settings → Developer → Local MCP servers → edit config) and add:
{ "mcpServers": { "prerak-crm": { "command": "node", "args": ["/path/to/prerak-mcp-server/dist/index.js"], "env": { "CRM_MCP_API_KEY": "<your-api-key>", "CRM_MCP_API_BASE_URL": "https://<your-prerak-domain>" } } } } -
Fully quit and reopen Claude Desktop (it reads the config only at launch).
-
Start a new conversation — Claude now has access to your CRM through Prerak's tools.
Configuration reference
| Variable | Required | Default | Purpose |
|---|---|---|---|
CRM_MCP_API_KEY | Yes | — | Workspace API key from Settings → Apps |
CRM_MCP_API_BASE_URL | No | http://localhost:3000 | Prerak backend URL |
CRM_MCP_TRANSPORT | No | stdio | stdio (local clients) or http (remote connectors — configured by your administrator) |
CRM_MCP_REQUEST_TIMEOUT_MS | No | 30000 | Request timeout |
What the assistant can do
Once connected, the assistant has tools covering contacts, companies, deals (including line items and revenue splits), tasks, activity and notes, lists and segments, forms, meetings, email and templates, sequences, marketing emails, playbooks, agents, Ask Prerak, notifications, billing usage, audit, and compliance. A few examples:
- "Find contacts at Acme with no activity in 30 days and add them to a list."
- "Create a follow-up task for Jane Chen tomorrow."
- "Draft and send a check-in email to my top three open deals' contacts."
- "How did last week's sequence perform?"
Write actions (creating, updating, sending) run with your permissions in the approved workspace — the assistant can't see or touch other workspaces.