MCP connectorsAFAS

AFAS MCP: connect AFAS to Claude and ChatGPT

Ask Claude or ChatGPT who starts next month, which invoices are still open or how a project stands. The answer comes straight from AFAS Profit, without building a report or asking the application manager for a list.

We build the connector for your company on AFAS’s own REST API. You decide exactly which data it can read, down to the single GetConnector, and salary data stays out unless you choose otherwise. It only reads.

Built for your company · Works in Claude, ChatGPT and Copilot

In practice

What your team can do with AFAS in Claude and ChatGPT

Staff questions without a list

Who starts or leaves this quarter, who works in which department, and who reports to whom. Read from AFAS when you need it, not exported to a spreadsheet that goes out of date.

Finance

Open items at a glance

Outstanding sales invoices by debtor and what is still to be paid to creditors, summarised the way you ask.

Sales and account management

The customer before the call

The organisation, its contacts and its recent invoices from AFAS CRM, in one answer before you pick up the phone.

Project management

Where a project stands

Projects with their hours and status, so you can see what has been spent before the client asks.

Examples

Ask it like this

“Who starts at our Amersfoort office in the next two months?”
“Which debtors have invoices more than 60 days overdue?”
“Give me the contacts and last three invoices for Jansen Installatietechniek.”
“How many people work in the Finance department, and who leads it?”
“Which projects for Gemeente Zwolle are still open, and how many hours are on them?”
“Who is on leave next week in the support team?”

The connector

What we build for AFAS

Deployed OS has no ready AFAS connector yet. We build it for your company when you start, on AFAS’s own API, with the same rules as every other connector: each person’s own login, access decided by group, every call logged.

Employees and organisation: Employees with their department, role, start and end dates and manager. No salary or other payroll data unless you choose to add it.
Leave and absence: Leave and absence per person or team, where your company wants that in the AI.
Relations and CRM: Organisations and contacts with their details.
Finance: Sales and purchase invoices with what is still open, per debtor or creditor.
Projects: Projects with their status and hours.

Security

Who sees what

Read-only, through your own GetConnectors: The connector reads through an app connector in AFAS that holds only the GetConnectors you pick. No UpdateConnectors are switched on, so it cannot create or change anything in AFAS. We only build writing if your company asks for it.
Salary data stays out by default: Payroll and salary data is the most sensitive part of AFAS. We leave it out of the connector unless you ask for it, and if you do, you can limit it to a single group such as payroll.
Access per group in Deployed OS: AFAS gives the connection its own token, so AFAS does not check each question against the asking person’s own AFAS rights. Admins decide in Deployed OS which groups get AFAS, and which data each group can reach.
Every call logged: Who asked, what was read and when. Deployed OS keeps the log, and it can be exported.

Setup

Set up the AFAS connector in three steps

We go through which questions matter most with you and agree which data the connector may read, with HR and payroll data decided separately.

Your AFAS application manager creates an app connector with those GetConnectors and a token, and you choose which groups get AFAS in Deployed OS.

We connect it to Deployed OS and test it with you. From then on people just ask.

Questions

AFAS MCP: common questions

Not as far as we know. AFAS has not published its own MCP server. There are MCP servers for AFAS Profit from other companies, such as iWebDevelopment and Peliqan, and an open-source one from Schuberg Philis. We build the connector on AFAS’s own REST API, so the answers can be used in Claude and ChatGPT next to your other systems.

No. The connector only uses GetConnectors, which read. Writing in AFAS goes through UpdateConnectors, which have to be switched on in the app connector, and we only build that if you ask for it.

Only if you decide it should. Salary and payroll data is left out of the connector by default. If your payroll team wants it, we add it for that group only, and every question about it is in the log.

Not through AFAS itself. The connection uses an AFAS token, and AFAS limits it to the GetConnectors in its app connector. Deployed OS then decides which groups can use AFAS and which data each group can reach, so you set the boundaries per group.

Deployed is an EU company and fully GDPR compliant, and you choose where your data is stored, down to the city. AFAS data is fetched when someone asks for it.

It depends on the size of your team. Get in touch and we will walk you through it.

More connectorsAll connectors

Let’s talk

See it on your own tools.

Tell us which systems your company runs on. We’ll show you what your team can ask, and what IT gets to control.