MCP connectorsTripletex

Tripletex MCP: connect Tripletex to Claude and ChatGPT

Ask Claude or ChatGPT which customers have overdue invoices, how many hours a project has used or what is posted on an account this month. The answer comes straight from Tripletex, without a report or an export.

We build the connector for your company on Tripletex’s own API. Each person connects with their own Tripletex user, so the AI sees only what that person may see in Tripletex, and it only reads.

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

In practice

What your team can do with Tripletex in Claude and ChatGPT

Finance

What is unpaid, by customer

Open and overdue invoices per customer and due date, with a reminder drafted in the same chat for you to send.
Project managers

Hours against the project

Hours logged on a project, by person and activity, and how the project stands, before the status meeting.
Sales and account managers

Know the customer before the call

The customer’s details, their orders and what has been invoiced, without asking finance.
Management

The numbers behind the question

Postings on an account or for a period, summarised in plain language before the board meeting.
Examples

Ask it like this

  • “Which customers have invoices more than 30 days overdue in Tripletex?”

  • “How many hours have we logged on the Bergli Eiendom project this month, and by whom?”

  • “What has Fjordvik Rør ordered from us this year, and what is not yet invoiced?”

  • “Show the postings on account 6300 for September.”

  • “Which projects have had no hours logged in the last two weeks?”

  • “Draft a friendly reminder to Haugen Bygg AS about invoice 10482. I will send it myself.”

The connector

What we build for Tripletex

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

Customers and invoices
Customers, and outgoing invoices with their amounts, due dates and whether they are paid.
Orders
Orders with their lines, so the AI can say what has been ordered and what is left to invoice.
Projects and hours
Projects, and timesheet entries per project, person and activity.
Ledger
Postings per account and period, for the people whose Tripletex access allows it.
Security

Who sees what

Read-only
The connector reads. It does not post, create invoices, register hours or change a customer.
Each person’s own Tripletex user
Everyone connects with an employee token for their own Tripletex user. Tripletex does not let a token have rights its owner lacks, so someone who cannot see the ledger in Tripletex does not see it through the AI either.
Your company decides who gets it
Admins choose which groups get Tripletex in Deployed OS. A group without access never sees the connector.
Every call logged
Who asked, what was read and when. Deployed OS keeps the log, and it can be exported.
Setup

Set up the Tripletex connector in three steps

01
We go through which questions matter most with you and build the connector on Tripletex’s API for your company.
02
Your Tripletex administrator turns on API access, and you choose which groups get Tripletex in Deployed OS.
03
Each person connects with an employee token for their own Tripletex user. From then on they just ask.
Compared

Tripletex’s own MCP server or Deployed OS?

Tripletex runs its own MCP server, in beta. An administrator turns it on under My subscription, and each person signs in to Tripletex from Claude or ChatGPT. In the beta it can register and search hours, create and search orders, find, create and update customers and suppliers, and show your own payslips. If one person wants to log hours or look up a customer from their AI tool, it is a good fit.

Deployed OS is for when Tripletex is one system among several and the company wants a say in how it is used. It sits next to your CRM, email and other tools in one company connection, reads invoices, projects and the ledger as well, admins decide which groups get it, and every call is logged in one place, in Claude and ChatGPT alike.

Their documentation: Tripletex MCP (beta)

Questions

Tripletex MCP: common questions

Yes. Tripletex has its own MCP server, in beta, with a limited set of tools for hours, orders, customers, suppliers and your own payslips. Deployed OS adds Tripletex to one company connection with your other systems, with access per group and one log.

No. The connector we build reads customers, invoices, orders, projects, hours and ledger postings. It does not post, invoice or register hours, and we only add writing if you ask for it.

Yes. Everyone connects with an employee token for their own Tripletex user, and a token cannot have rights its owner does not have. The AI cannot see more than the person could in Tripletex.

Either, or both. If people mainly want to log hours from Claude or ChatGPT, Tripletex’s own server does that. If you want invoices, projects and the ledger read next to your other systems, with access per group and one log, we build the connector for you.

Deployed is an EU company and fully GDPR compliant, and you choose where your data is stored, down to the city. Tripletex 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.