Perfex CRM

com.themesic由 themesic.com 发布v3.1.0更新于 Oct 24, 2026

Read and write a self-hosted Perfex CRM from an AI agent: 148 permission-filtered tools.

已验证Streamable HTTP可网页运行效率与工作流商业与电商

概览

AI 生成的概览

面向自建 Perfex CRM 的 MCP 服务器,为助手提供 148 个按权限过滤的工具,可读写 CRM 数据。

可以做什么
  • 读写客户、联系人、线索、发票、报价、提案、合同、付款与贷项通知等核心 CRM 记录
  • 管理项目、任务、里程碑、工时、订阅、商品、费用、员工与日历条目
  • 查询国家、税种、货币、状态与自定义字段等基础数据
  • 处理知识库文章与分组,以及挂在不同实体类型上的备注
  • 列表接口支持分页、字段筛选、排序与日期范围过滤
适用场景
适合团队使用自建 Perfex CRM,并希望 AI 助手直接查询或更新客户、线索、发票、项目与任务,例如在 Claude、ChatGPT、Cursor 或自动化代理中使用。
运行要求
需要已安装并授权商业版 REST API 模块、且已启用 MCP 服务器的自建 Perfex CRM。端点为自己域名下的 /api/mcp(或厂商托管的 MCP 地址)。需在 Perfex 的 Setup > API > API Management 创建 API 令牌,通过 authtoken 请求头发送,并为需要暴露的资源勾选权限。
安装前请注意
该令牌可读写 CRM 数据,包括创建、更新和删除客户、发票、付款与员工;建议尽量使用限定范围甚至只读的令牌。工具列表按令牌权限过滤,新增权限行需先勾选,相应工具才会出现。该模块为付费产品,需要有效授权,且 CRM 数据会经过 MCP 端点。

安装

在 SourceWeft 中

  1. 打开 控制台中的 Perfex CRM,将其添加到工作区。
  2. 连接 authtoken 凭据。它们会被私密存储,绝不会在公开页面上展示。
  3. 为需要使用其工具的对话启用该服务。

Web executable,通过 Streamable HTTP。 远程服务在工作区中配置后即可从网页运行时运行。

其他 MCP 客户端

参照 仓库 中的启动说明。

README

[REST API for Perfex CRM — connect Perfex CRM with AI agents, Zapier, WooCommerce, n8n and third-party apps]

Perfex CRM REST API — Examples, Postman Collection & Code Snippets

🌐 English · 简体中文 · Español · Português (BR) · Italiano · Français · Deutsch · Türkçe · Tiếng Việt · ไทย · العربية

Ready-to-use Postman collection, code snippets (cURL, PHP, Python, JavaScript) and a resource catalogue for the REST API module for Perfex CRM — the fastest way to connect Perfex CRM with AI agents and third-party applications.

[Postman] [OpenAPI 3.0] [License: MIT] [Perfex CRM]

The Perfex CRM REST API lets you read and write customers, leads, invoices, estimates, projects, tasks and more over a clean HTTP/JSON interface — perfect for CRM integration, automation and custom apps. v3.0 adds an MCP server for AI agents, production-grade webhooks, ready-made Zapier / Make / n8n polling, batch operations and smarter list endpoints. This repository is the practical companion to the REST API for Perfex CRM module by Themesic Interactive: copy-paste examples, an importable Postman collection, and a full endpoint catalogue.


🚀 What's new in v3.0

FeatureEndpointWhat it does
🤖 MCP serverPOST /api/mcpModel Context Protocol (JSON-RPC 2.0) — exposes 148 permission-filtered CRM tools to Claude Desktop, ChatGPT, Cursor, n8n AI Agent and any MCP client
🪝 Webhooks 2.0/api/webhooks124 events, REST management, async delivery with retries, SSRF protection, HMAC-signed requests
🔌 Automation (polling)/api/zapier/*Ready-made polling triggers for Zapier, Make.com, n8n and any polling-based tool
⚡ BatchPOST /api/batchUp to 50 operations in one request (same tool names as MCP)
📚 Knowledge Base/api/knowledge_baseArticles + groups CRUD
🗒️ Notes/api/notesPolymorphic notes across 12 entity types
📄 Smarter listsany list endpointOpt-in ?page=&per_page=, ?fields=, ?sort=, ?created_after=&created_before=
🛡️ Safe writesany POSTIdempotency-Key replay, ignored-unknown-fields on PUT, X-RateLimit-* headers
📐 OpenAPI 3.0 specGET /api/openapiThe whole surface as one machine-readable document - 74 paths, 144 operations - import into Postman, Insomnia or Stoplight in seconds (reference copy in openapi/)

Everything is opt-in and backwards-compatible: requests without the new parameters return the exact same response as before.


Contents

FolderWhat's inside
postman/Importable Postman collection + environment ({{base_url}}, {{authtoken}}) — now with MCP, Webhooks, Batch, Automation, Knowledge Base & Notes
snippets/curl/Copy-paste curl commands for the most common calls
snippets/php/PHP (cURL) examples
snippets/python/Python (requests) examples
snippets/javascript/JavaScript / Node (fetch) examples
docs/Authentication, pagination & filtering, webhooks, MCP, automation, custom tables, errors & status codes

Each snippet language has examples for customers, invoices, leads plus the v3 features webhooks, mcp, batch, automation, knowledge_base and notes, and a list_features file showing pagination, field selection and sorting.


Quick start

Every request to the Perfex CRM REST API is authenticated with the Authtoken header. Create a token in your Perfex admin under API → API Management (after activating the REST API module), then call the API at https://yourdomain.com/api/...:

bash
curl -H "authtoken: YOUR_API_TOKEN" https://yourdomain.com/api/customers

That returns the list of customers as JSON. See docs/authentication.md for header vs. query-parameter auth, and snippets/ for the same call in PHP, Python and JavaScript.

Use the Postman collection

  1. Open Postman → Import → drop in postman/perfex-rest-api.postman_collection.json.
  2. Import the environment postman/perfex-rest-api.postman_environment.json.
  3. Set base_url to https://yourdomain.com/api and authtoken to your token.
  4. Pick any request and hit Send.

Connect an AI agent (MCP)

Point any MCP client (Claude Desktop, Cursor, ChatGPT, n8n AI Agent) at POST https://yourdomain.com/api/mcp and send your authtoken header. The server advertises permission-filtered tools for your CRM. See docs/mcp.md and snippets/curl/mcp.sh.

Use with Claude, ChatGPT and other AI assistants

Connect any assistant with one URL, https://perfex-mcp.themesic.com/mcp. Step-by-step setup for Claude, ChatGPT, Cursor and VS Code: docs/connect-ai-assistants.md.

A Claude plugin (connector + skills) for claude.ai, Cowork and Claude Code lives in claude-plugin/. It requires the REST API module with a valid license and the MCP server enabled. See claude-plugin/README.md for setup, permissions and the privacy policy.


Endpoint catalogue

All CRUD endpoints follow a RESTful convention: GET list, GET /:id single, POST create, PUT /:id update, DELETE /:id delete — under the base path https://yourdomain.com/api.

Core CRM resources

ResourceBase pathTypical operations
Customers/api/customerslist, get, create, update, delete
Contacts/api/contactslist, get, create, update, delete
Leads/api/leadslist, get, create, update, delete
Invoices/api/invoiceslist, get, create, update, delete
Estimates/api/estimateslist, get, create, update, delete
Credit Notes/api/credit_noteslist, get, create, update
Payments/api/paymentslist, get, create
Proposals/api/proposalslist, get, create, update, delete
Contracts/api/contractslist, get, create, update, delete
Projects/api/projectslist, get, create, update, delete
Tasks/api/taskslist, get, create, update, delete
Milestones/api/milestoneslist, get, create, update, delete
Timesheets/api/timesheetslist, get, create, update, delete
Subscriptions/api/subscriptionslist, get, create, update
Items/api/itemslist, get, create, update, delete
Expenses/api/expenseslist, get, create, update, delete
Staff/api/staffslist, get, create, update, delete
Calendar/api/calendarlist, get, create, update, delete
Custom Fields/api/custom_fieldslist per related type
Common (lookups)/api/commoncountries, taxes, currencies, statuses …

v3 platform & extra resources

ResourceBase pathTypical operations
MCP server/api/mcpPOST JSON-RPC 2.0: initialize, tools/list, tools/call
Batch/api/batchPOST up to 50 operations in one request
Webhooks/api/webhookslist, get, create, update, delete, POST /:id/toggle, GET /events, GET /:id/logs
Automation (polling)/api/zapierGET /resources, GET /poll/:resource, GET /test/:resource
Knowledge Base/api/knowledge_baselist, get, create, update, delete; /groups
Notes/api/noteslist by :rel_type/:rel_id, get, create, update, delete

The exact request fields per resource are documented in the official API guide. The snippets here cover the most common flows.


Smarter list endpoints (v3)

Every list endpoint accepts optional query parameters. Add them and you get a { data, meta } envelope; omit them and you get the exact legacy array.

bash
# Page 2, 20 per page, only id + company, newest first, created this yearcurl -H "authtoken: YOUR_API_TOKEN" \  "https://yourdomain.com/api/customers?page=2&per_page=20&fields=id,company&sort=-datecreated&created_after=2026-01-01"
ParameterExampleEffect
page, per_page?page=2&per_page=20Pagination → { data, meta }
fields?fields=id,companyReturn only these columns
sort?sort=-datecreated,companySort (- = descending)
created_after, created_before?created_after=2026-01-01Date-range filter

per_page is the parameter that sizes a page (1-100, default 25). limit is accepted as an alias only when page is sent too, so a bare ?limit=5 does not paginate - use ?page=1&per_page=5.

See docs/pagination-filtering.md and snippets/curl/list_features.sh.


Upgrading from 2.x

There are no breaking changes. Every v3 list feature is opt-in:

  • Send none of the parameters above and you get the same plain array 2.x returned. The { data, meta } envelope appears only when you send page or per_page.
  • No endpoint was renamed. Customers have always been at /api/customers.
  • Unknown fields on PUT are ignored instead of returning an error.
  • POST requests accept an optional Idempotency-Key header; identical retries replay the stored response rather than creating duplicates.

Two things worth knowing when adopting v3:

  • Custom tables moved behind an allowlist in 3.0.2 - see docs/custom-tables.md.
  • New permission rows (Webhooks, Notes, Knowledge Base) must be ticked on existing tokens before those endpoints answer, and before their MCP tools appear in tools/list.

Popular integrations & use cases

The Perfex CRM REST API is commonly used to connect Perfex CRM with AI agents and third-party applications:

  • AI assistants (MCP) — let Claude, ChatGPT or Cursor read and update your CRM through /api/mcp.
  • Zapier / Make / n8n — no-code automation via ready-made polling triggers (/api/zapier/*).
  • Webhooks — push Perfex events (new invoice, new lead, 124 events) to Slack, Discord or your own backend, signed with HMAC.
  • Google Sheets / Power Automate — sync customers, invoices or payments to spreadsheets and dashboards.
  • Custom apps & portals — build a mobile app or customer portal on top of your Perfex data.
  • Accounting & e-commerce — sync invoices and items with external billing or shop platforms.

All of these are powered by the REST API for Perfex CRM module.


Authentication (summary)

MethodHow
Header (recommended)Authtoken: YOUR_API_TOKEN
Query parameter?authtoken=YOUR_API_TOKEN (handy for quick tests / webhooks)

Tokens are created and scoped (per-resource permissions) in API → API Management. Full details in docs/authentication.md.


FAQ

Does Perfex CRM have a REST API? Yes. The REST API for Perfex CRM module adds a full RESTful HTTP/JSON API for customers, leads, invoices, estimates, projects, tasks and more, plus a v3 MCP server, webhooks, batch and automation endpoints.

Can I use Perfex CRM with AI agents / ChatGPT / Claude? Yes — v3 ships an MCP server at POST /api/mcp that exposes permission-filtered CRM tools to any Model Context Protocol client. See docs/mcp.md.

How do I authenticate with the Perfex CRM API? Send your token in the Authtoken HTTP header (or as an ?authtoken= query parameter). See docs/authentication.md.

What is the base URL of the Perfex CRM API? https://yourdomain.com/api — for example https://yourdomain.com/api/customers.

Can I connect Perfex CRM to Zapier, Make or n8n? Yes — v3 has ready-made polling triggers under /api/zapier/*, plus webhooks. See Popular integrations and docs/automation.md.

Is there a Postman collection for Perfex CRM? Yes — import postman/perfex-rest-api.postman_collection.json and the bundled environment, set your base_url and authtoken, and start sending requests.

How do I create an invoice via the Perfex CRM API? POST https://yourdomain.com/api/invoices with the invoice fields and an items[] array — v3 auto-calculates subtotal/total. See snippets/curl/invoices.sh.


About / Support

[Perfex CRM REST API icon]

This repository is an examples companion to the commercial module:

REST API for Perfex CRM — connect your Perfex CRM with third-party applications by Themesic Interactive.

Contributions of additional examples are welcome — see CONTRIBUTING.md.

License

Example code in this repository is released under the MIT License. "Perfex" is a trademark of its respective owner; the REST API module is a commercial product by Themesic Interactive.

来源:README.md,提交 0f4c4f7

工具

0
该服务器需要 API 密钥等凭据,因此 SourceWeft 无法在没有凭据的情况下读取其工具,也未收录。

版本历史

1
  1. v3.1.0最新Sep 16, 2026

评分

已满足适用检查项的 60%

该评分衡量此收录条目的完整程度,依据注册中心条目、端点与公开来源计算得出。它不是对服务器本身的评价,也不表示服务器安全或当前可用:可连通性是带日期的检查结果,评分也不包含安装量或用户评价。

  • 近 30 天内可连通必需25 分

    请保持端点能够响应 MCP 握手;SourceWeft 每 30 天探测一次。

  • 已声明认证方式必需10 分
  • 已列出工具15 分

    请让服务器在无凭据时响应 tools/list,或发布可在沙箱中无凭据启动的软件包。

  • 描述必需15 分
  • 图标10 分
  • 文档15 分
  • 许可证10 分