Perfex CRM MCP Server認証済み注目

Your CRM, finally speaking the language of AI agents.

Perfex CRM holds everything that matters about your business. Your leads, your customers, your invoices, your open tickets, your project timelines, your unpaid balances. The problem was never the data. The problem was getting to it. Every question meant opening the admin panel, picking a module, filtering a table, exporting a CSV, and then doing the actual thinking somewhere else.

This module removes that entire middle step.

Perfex CRM REST API MCP turns your existing Perfex installation into a Model Context Protocol server. Once it is installed and connected, an AI assistant like Claude, ChatGPT, Cursor or any other MCP-compatible client can query and update your CRM directly, in plain language, with your own permissions applied. You stop clicking through screens and start asking questions.

"Which of my clients have overdue invoices older than 45 days, and how much do they owe in total?"

"Create a lead for the company that just emailed me, assign it to Maria, and set a follow up reminder for Tuesday."

"Summarise every open support ticket for Acme Ltd and tell me which one has been sitting longest."

That is not a mockup. That is what the module does on day one.

---

Why MCP, and why now

The Model Context Protocol is the emerging standard for connecting AI assistants to real systems. Instead of writing a custom integration for every assistant you want to use, you expose your data once, through one server, and every MCP-compatible client can speak to it.

That matters for a CRM more than for almost any other system. A CRM is where the messy, high-value, constantly changing information lives. It is also, traditionally, the system that is hardest to get useful answers out of quickly. Reports are rigid. Filters are shallow. Cross module questions ("show me clients with high ticket volume and low invoice totals") usually require a developer or a database export.

An AI agent with direct access solves that, because it can chain operations. It can pull the customer list, cross reference invoices, check ticket counts, and hand you the answer in one pass. No SQL, no report builder, no export.

---

What you get

A full MCP server, built specifically for Perfex. Not a generic REST wrapper that dumps raw JSON at your assistant and hopes for the best. Every endpoint is exposed as a properly described tool with typed parameters, so the AI understands what a lead is, how it differs from a customer, and which fields are required to create an invoice.

Complete CRM coverage. Customers and contacts, leads and lead statuses, invoices, estimates, proposals, credit notes, payments, expenses, items and products, tasks, projects and milestones, support tickets, contracts, subscriptions, staff members, timesheets, and custom fields. Read operations across the board, plus create and update where it makes sense.

Your permissions, respected. The server authenticates through your Perfex API layer, so staff level permissions still apply. A staff member connecting their own assistant sees exactly what they would see in the admin panel. Not one record more.

Both transport modes. Run it over stdio for local desktop clients, or over HTTP for hosted and team wide setups. Pick whichever fits how your people actually work.

Multi client by design. One installation serves Claude Desktop, Claude Code, Cursor, Windsurf, VS Code, n8n, and anything else that speaks MCP. You are not locking yourself into a single vendor's assistant.

Installs like any other Perfex module. Upload through the standard module installer, activate, generate a key. There is no separate server to provision, no Docker stack to babysit, no second hosting bill.

---

What this actually changes in a working day

Morning triage without opening a single tab. Ask for everything that changed overnight. New leads, new tickets, invoices that just went overdue. Get one paragraph instead of four dashboards.

Sales prep that takes thirty seconds. Before a call, ask for the full history on a client. Past invoices, current balance, open tickets, previous proposals, last conversation logged. Your assistant assembles it while you are still finding the meeting link.

Data entry that happens while you talk. Paste an email into your assistant and tell it to create the lead. Fields get filled, the source gets set, the follow up gets scheduled. The record exists before you have finished reading the email.

Reporting that answers the question you actually asked. Not the question the report builder was designed for. Ask for revenue by client for a specific quarter, filtered by project type, excluding one customer. You will get it.

Bulk cleanup without a developer. Find duplicate contacts, spot leads that have been sitting in the same status for ninety days, identify customers with no activity in a year. Then act on them, in the same conversation.

Automation that plugs into what you already run. If you are building flows in n8n, Make, or your own scripts, the MCP server gives your AI nodes a clean, documented interface to Perfex instead of hand rolled HTTP calls that break on the next update.

---

Built for people who care about control

Handing an AI assistant access to your CRM is a decision worth taking seriously, so the module is built around that.

Scoped API keys. Generate separate keys per staff member or per integration. Revoke any one of them without touching the others.

Read only mode. If you want your team asking questions but not changing records, flip the switch. The write tools simply stop being offered to the client.

Granular tool control. Enable and disable individual capabilities from the settings panel. If nobody should be deleting anything through an assistant, turn those tools off entirely.

Full request logging. Every call is recorded with the key used, the tool invoked, the parameters passed, and the response status. You always know what your assistants have been doing.

Rate limiting. Protect your server from a runaway loop or an over eager agent.

Your data stays on your server. The MCP server runs inside your own Perfex installation. There is no third party relay, no external cloud service holding a copy of your customer list, no vendor in the middle.

---

Requirements

• A working Perfex CRM installation
• PHP 7.4 or higher
• An MCP compatible client (Claude Desktop, Claude Code, Cursor, Windsurf, VS Code with an MCP extension, n8n, or any other)
• HTTPS strongly recommended for the HTTP transport

No command line skills required for the basic setup. If you can install a Perfex module and paste a config block into your assistant's settings file, you can run this.

---

Setup, start to finish

1. Upload the module through Setup > Modules > Upload Module
2. Activate it
3. Open the new MCP settings panel and generate an API key
4. Copy the generated config snippet
5. Paste it into your MCP client's configuration
6. Restart the client and start asking questions

Most installs take under five minutes. Detailed documentation covers every client separately, with copy paste ready configuration for each.

---

What is included

• The complete module, ready to install
• Documentation covering installation, configuration, security settings, and per client setup
• A reference of every exposed tool with its parameters
• A library of example prompts to get your team productive immediately
• Free updates
• Direct support from the developer

---

Frequently asked

Do I need the Perfex REST API module as well? The MCP server handles its own authentication and endpoint layer, so it works on a standard Perfex installation.

Will this work with my custom modules and custom fields? Custom fields are supported across the standard modules. Third party module support depends on the module, get in touch if you have a specific one in mind.

Can my whole team use it, or just me? The whole team. Each staff member gets their own key, and each key inherits that person's existing Perfex permissions.

Is my data sent anywhere? Your CRM data goes to whichever AI client you connect, and nowhere else. There is no intermediary service. Choose your client accordingly, and use read only mode if you want a tighter boundary.

What if MCP changes? The protocol is versioned, and updates to the module track it. Updates are free.

Does it work on a self hosted assistant? Yes. Anything speaking MCP works, including local models running through a compatible client.

---

The short version

Your CRM has always known the answers. Now you can just ask it.