









































Works out-of-box with your favorite AI agents

Tyler ERP Pro is a public sector ERP suite from Tyler Technologies for local governments, covering financials, payroll, human resources, utility billing, and cash receipting. Makini's MCP server gives AI agents direct access to Tyler ERP Pro data and workflows, with no custom development.
Have any questions? We’re here to help You
Yes, Tyler ERP Pro is the product Tyler Technologies sold for years as Incode; Tyler now brands it ERP Pro, powered by Incode, still runs ERP Pro 9 and ERP Pro 10 user groups, and offers ERP Pro 10 as a Tyler hosted cloud edition. It is a public sector ERP for small and mid sized cities, counties, utilities and special districts, covering multi fund accounting, payroll and HR, utility billing, cash receipting and permitting.
Tyler ERP Pro and Enterprise ERP are Tyler Technologies public sector ERPs for different sizes: ERP Pro, powered by Incode, targets small and mid sized local governments with more than 50 natively connected modules, while Enterprise ERP, powered by Munis, serves larger cities, counties and school districts. Tyler publishes an API catalog for Enterprise ERP but none for ERP Pro. Gartner named ERP Pro a Visionary in its 2025 local government cloud ERP Magic Quadrant.
Tyler does not publish a public developer API for ERP Pro the way it publishes an API catalog for Enterprise ERP; integration has traditionally run through Tyler's own connected products, such as Permitting and Licensing Pro, Content Manager, My Civic and Tyler payment processing, and through vendor arranged interfaces. For an AI agent this blocks nothing on your side: you authorize your ERP Pro login through Makini Link and get_connection_details shows what the connection exposes.
To connect Tyler ERP Pro to Claude or ChatGPT, sign in with your ERP Pro credentials through Makini Link, then paste the MCP endpoint Makini issues into Claude, ChatGPT, Cursor or another MCP client; the credentials are entered in Makini Link, not in the chat client. Run get_connection_details to see which objects are exposed. Makini's unified models include invoices, journal entries, payables, receivables, purchase orders, vendors and budgets where the connection supports them.
Tyler ERP Pro handles utility billing for electricity, gas, water and other services run by municipal and independent authorities, including customer accounts and consumption history, and cash receipting through its point of sale cashiering tools, which post counter payments against utility and other receivables. Both are among the 50 plus modules Tyler calls natively connected, so a payment taken at the counter updates the customer account and the general ledger without re keying.
An AI agent can answer budget and accounts payable questions from Tyler ERP Pro by reading budgets, journal entries, payables and vendor records where the connection exposes them: remaining budget by fund and department, invoices past their due date, a vendor's payments this fiscal year, or purchase orders with no matching invoice. ERP Pro's own Smart Cards and dashboards already push some of these alerts; the agent adds free form questions across funds.
No, an AI agent should not post journal entries or payments in Tyler ERP Pro on its own. Public sector finance depends on segregation of duties and approval chains, and a posting by a shared agent login would be hard to defend in an audit. Keep the agent reading and drafting: it can prepare a journal entry or a batch for a clerk to review. Where writes are allowed at all, test them outside production.
Scope a Tyler ERP Pro security role for an AI agent to the funds, departments and modules it must see, then create a dedicated user with that role, because the MCP endpoint Makini issues is scoped to that login. Payroll, HR and utility customer records hold personal data, so exclude them unless needed. If ERP Pro runs on your own servers, IT may also need to allowlist Makini's IP addresses or set up a VPN.