You want to ask Claude or ChatGPT about the numbers in POHODA: who owes you, how sales are going, what is in stock. There are now four ways to connect AI to POHODA. They differ in which POHODA they work with, how much work they take and whether the AI can also write.<\/p>\n
The least work is a hosted MCP server<\/strong> that connects to POHODA via mServer or straight to the SQL database. An open-source server pays off if you have your own IT and want to manage it yourself. Manual export into the chat is fine for trying things out, not for daily work.<\/p>\n<\/div>\n You export a report from POHODA to Excel or PDF and upload it to the chat. It works with any POHODA and costs nothing.<\/p>\n The downsides: the data is out of date the moment you export it, the AI only sees what you uploaded, and you send company data into the chat without access control. Good for a one-off analysis.<\/p>\n A connection built into mPohoda, launched in October 2026. It works only for online mPohoda<\/strong>, the invoicing app. It can’t reach the accounts, stock and orders in desktop POHODA. We explain the difference in mPohoda MCP and desktop POHODA<\/a>.<\/p>\n There are freely available MCP servers for POHODA on GitHub. They talk to POHODA through mServer.<\/p>\n What you need: a running mServer, a computer or server where the MCP server runs, and someone to install, secure and update it. The software is free, the work isn’t. Suits companies with their own IT. How mServer works is explained in POHODA mServer<\/a>.<\/p>\n A vendor runs the MCP server and you install nothing. This is how POHODA MCP<\/a> works. We connect to POHODA in one of two ways:<\/p>\n Your IT just opens access to mServer or the database. The AI sees only the modules you allow, and writing happens only after you confirm.<\/p>\nRoute 1: manual export into the chat<\/h2>\n
Route 2: mPohoda MCP<\/h2>\n
Route 3: an open-source MCP server<\/h2>\n
Route 4: a hosted MCP server<\/h2>\n
\n
Side-by-side comparison<\/h2>\n