EvoERP MCP Server
Disclaimer: The EvoERP MCP Server provides read-only help and reference information. It does not access your company database or make changes in EvoERP. AI-generated answers and SQL queries may contain errors or may not apply to your installed version. Verify instructions against the linked documentation and review queries against your actual database before running them. No EvoERP login or database credentials are required for this MCP server; do not share passwords or other sensitive information. If you separately grant your AI assistant access to your EvoERP installation or data, you are responsible for the actions it takes and any resulting changes.
The EvoERP MCP Server lets compatible AI assistants search EvoERP help, read public forum discussions, and look up database table and field names. You can ask questions in ordinary language, get explanations with links to supporting documentation, and draft read-only SQL queries for reporting.
The current server provides help and reference information. It does not connect to your company database or change anything in EvoERP. It currently references the live forum content and the help content for 2025.1 and 2026.1.
What is Model Context Procool (MCP)?
Model Context Protocol, or MCP, is an open standard that lets AI applications connect to external tools and information sources. A compatible assistant discovers the tools a server provides and can use them when answering your questions. Learn more about MCP.
For EvoERP, this gives your assistant a way to retrieve relevant documentation during a conversation instead of relying entirely on its general knowledge. You ask the question; the assistant searches the available sources and uses the results to explain the answer.
Installing the MCP Server
For some common clients, see the list below.
Any client that supports remote MCP servers over HTTP / Streamable HTTP can use the EvoERP server. The names of settings vary, but the basic process is:
-
Open your client’s settings and look for MCP Servers, Connectors, Integrations, or Tools.
-
Choose Add Server or the equivalent option.
-
Select a remote, HTTP, or Streamable HTTP connection.
-
Enter these details:
Setting Value Server name EvoERP Help Server URL https://mcp.evoerp.cloud/mcpAuthentication None API key, credentials, or custom headers Leave empty -
Save the connection and enable the server. Some clients require a refresh, restart, or tool-discovery step.
-
Enable the EvoERP tools in your conversation if your client requires it, and approve tool calls when prompted.
-
Test the connection with:
Use EvoERP Help to list the available help versions.
Use the complete URL, including /mcp. If your client only asks for an executable or startup command, consult its documentation for remote MCP support.
Once connected, ask questions naturally. You do not need to memorize tool names.
ChatGPT Codex
- Open Plugins.
- Select +, then Add custom MCP server.
- Enter EvoERP Help as the name and
https://mcp.evoerp.cloud/mcpas the server URL. - Select No authentication.
- Review the connection notice and select Create as a plugin.
- Open the new plugin in your personal plugins and install it using the + button.
- Start a Work chat, type
@, and select EvoERP Help.
You can then ask an EvoERP question. These steps follow OpenAI’s current MCP setup guide.
Claude
- Open Customize → Connectors.
- Select + Add → Add custom connector.
- Enter EvoERP Help and
https://mcp.evoerp.cloud/mcp. - Continue through setup and choose No sign in for authentication. Leave request headers empty.
- Select Add.
- In a conversation, open + → Connectors and enable EvoERP Help.
For Team and Enterprise organizations, an authorized owner or administrator must add the connector first. See Claude’s custom connector instructions.
Visual Studio Code / GitHub Copilot
- Open the Command Palette with Ctrl+Shift+P, or Cmd+Shift+P on macOS.
- Run MCP: Add Server.
- Follow the prompts to add an HTTP server using
https://mcp.evoerp.cloud/mcp. - Choose a global configuration to use it across projects, or a project configuration for the current project.
- Run MCP: List Servers and start the server if needed.
- Open Copilot Chat and check Configure Tools to confirm the EvoERP tools are available.
Ask Copilot an EvoERP question and allow the relevant tool calls when prompted. See Microsoft’s MCP setup instructions.
Cursor
Create or open ~/.cursor/mcp.json for access across projects, or .cursor/mcp.json inside a specific project. Add this configuration:
{
"mcpServers": {
"evoerp-help": {
"url": "https://mcp.evoerp.cloud/mcp"
}
}
}
If the file already contains other servers, add evoerp-help to the existing mcpServers object.
Open Customize → MCPs, confirm the server is enabled, and ask Cursor Agent an EvoERP question. See Cursor’s MCP documentation.
What It Doesn’t Do
The current server does not:
- Access your company’s customers, inventory, orders, balances, or other business records.
- Connect to a customer database or execute SQL.
- Run EvoERP programs, create records, post transactions, or change settings.
- Guarantee that generated SQL matches your installed database or implements the correct business calculations.
AI answers can still contain mistakes. Review the linked documentation, and verify reporting queries against your database structure and business requirements before using them. If you have any issues or questions with an AI’s response, please contact tech support.
Examples
Keep in mind this MCP server is simply adding tools to your general-purpose AI client. When asking questions, you will need to ensure the AI assistant knows the context of the question, i.e., you are asking specifically about something in EvoERP. We also recommend giving the exact database version (e.g., Actian Zen 15) you are using if you want it to assist in creating queries for exporting data to make it more likely to generate compliant query text.
Once connected, try questions like these:
Use EvoERP Help to explain how to create a customer in EvoERP 2026.1. Include prerequisites and links to the documentation.
Find the help for WO-C and explain the work order creation procedure for my installed release.
Show me the latest public forum posts.
Find the tables and fields used to store customer codes and names.
I use Actian Zen through ODBC. Draft a read-only query that returns up to 100 customer codes and names.
You can follow up naturally:
Explain that step in more detail.
Read the related help articles and explain the prerequisites.
Show me the source that supports that answer.