Skip to main content
Tempolia AI and MCP server

Query your data and perform actions within your permissions.

Tempolia AI helps users understand management data. The MCP server allows an authorised assistant to use Tempolia tools to search, analyse or update selected objects.

Product analyst and developer testing an assistant connected to Tempolia
Practical examples

Natural-language requests connected to Tempolia objects.

Invoicing

“Show me invoices awaiting approval that contain an anomaly.”

The assistant searches documents by status, company, customer or period, then summarises the points to review.

Profitability

“Which engagements are over their time budget this month?”

It brings together the budget, actuals, invoicing and remaining work within the scope available to the user.

Cash flow

“List customers whose invoices have been overdue for more than 30 days.”

It uses balances, due dates and payments to prepare a reminder review.

Time

“Add 1 hour 30 minutes for a meeting on the ACME engagement after I confirm.”

The MCP server can call the time-creation tool with the same validations and permissions as the interface.

Customers

“Prepare a 360-degree customer summary before my meeting.”

The response can bring together engagements, budgets, invoices, balances, events, documents and the latest authorised activities.

Management

“Which staff members have not completed their time entry for the week?”

The assistant identifies incomplete periods according to the manager's rules and scope.

Engagements

“Create the 2026 engagement for these customers from the approved template.”

A batch action can be prepared, presented for confirmation and executed with traceability.

Reports

“Export revenue and recovery by activity.”

Tempolia AI uses authorised reports and returns the results as a summary or file.

From text to action

A controlled four-step process.

1

Understand

The assistant identifies the object, filters, period and expected result.

2

Authorise

Tempolia checks the user, permissions and data scope.

3

Confirm

Creation or modification actions may require explicit confirmation.

4

Record

The call, result and sensitive operations are logged according to their nature.

MCP

A standard protocol for connecting assistants to Tempolia tools.

The MCP server exposes structured tools: searches, retrieval, creation or updates for customers, engagements, time, expenses, tasks, staff, documents and reports.

The protocol does not provide unrestricted database access. Every call passes through Tempolia authentication and permissions. The available tools can be restricted by profile.

Targeted read accessSearch and retrieve authorised objects.
Controlled actionsCreate or edit after validating parameters and permissions.
Structured responsesData that the assistant can use without direct SQL access.
TraceabilityLog calls and sensitive operations.
Necessary safeguards

AI must not circumvent the software's rules.

Permissions

The same scope as the user

The assistant cannot see data that the signed-in profile cannot access.

Approval

Confirmation before sensitive actions

A creation, modification or deletion may require explicit approval.

Compliance

No silent modifications

Approved objects, particularly tax-related records, remain subject to integrity and correction rules.

Quality

Verifiable results

The filters, sources and objects used must be explainable to the user.

Tempolia AI / MCP FAQ

Frequently asked questions before activation.

Does the assistant access the database directly?

No. It uses structured tools exposed by Tempolia, with authentication, permissions and controls.

Can it modify data?

Only if the corresponding tool is enabled and the user has permission. Confirmation may be required.

Which assistants can use the MCP server?

Assistants compatible with the MCP protocol and configured with authorised Tempolia access settings.

Can AI be restricted to read-only access?

Yes. The tool scope can be limited to retrieval and reports.

How should an initial use case be defined?

Choose a frequent question, a data scope, an expected result and the relevant permissions. The case is then tested in a controlled environment.

Begin with a measurable use case.

We define the question, data, permissions, actions and success criteria.