Epicor Kinetic FAQs

Question 1

How does it connect to Epicor Kinetic data?

Accepted Answer

It leverages CData JDBC Drivers to expose Epicor Kinetic data as relational SQL models. These models are then made accessible to LLMs via a standardized Model Context Protocol (MCP) interface.

Question 2

Which AI clients are compatible with the Epicor Kinetic MCP Server?

Accepted Answer

The server is compatible with any AI client that supports the Model Context Protocol (MCP). Claude Desktop is specifically mentioned as a compatible example.

Question 3

What are the main benefits of using this server for data access?

Accepted Answer

Key benefits include enabling natural language data querying for LLMs, direct access to live Epicor Kinetic data without SQL, and seamless integration with AI clients supporting the Model Context Protocol (MCP).

Question 4

Does this server support read/write operations for Epicor Kinetic data?

Accepted Answer

No, this specific project (epicor-kinetic-mcp-server-by-cdata) is designed as a read-only MCP server for querying. For full read, write, update, and delete capabilities, CData offers a separate, dedicated MCP Server for Epicor Kinetic.

Question 5

What is the Epicor Kinetic MCP Server?

Accepted Answer

The Epicor Kinetic MCP Server enables large language models (LLMs) to query live Epicor Kinetic data using natural language, eliminating the need for manual SQL queries.

Epicor Kinetic

Epicor Kinetic

Key Features

Use Cases

Key Features

Use Cases