> ## Documentation Index
> Fetch the complete documentation index at: https://docs.useglimps.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Glimps for AI agents

> How an agent should read this documentation, what the Glimps MCP server exposes, and where the limits are.

This page is for anyone, or anything, connecting an agent to Glimps.

## Reading these docs as a machine

Every page here is available as plain Markdown. Add `.md` to any documentation URL:

```
https://docs.useglimps.com/how-it-works.md
```

There is also an index of every page, meant to be fetched whole:

```
https://docs.useglimps.com/llms.txt
https://docs.useglimps.com/llms-full.txt
```

Use `llms.txt` to find the right page, and `llms-full.txt` when you want the entire documentation in one request.

Each page also carries a menu with **Copy page**, **View as Markdown**, and buttons that open the page in Claude or ChatGPT.

## What the MCP server exposes

The Glimps MCP server lives at `https://useglimps.com/mcp` and speaks streamable HTTP.

* **Read-only.** There are no write tools. An agent cannot change, approve, book, or pay anything, and this is enforced on the server, not in the client.
* **Role-scoped.** Every call enforces the live role of the user who connected. An approver sees only what they could see in the app.
* **Administration-scoped.** A connection reads only the administrations that were ticked on the consent screen. Every answer covers one administration and names it. A call that names none answers about the default administration.

Authenticate with OAuth through the consent screen, or with a bearer token from an API key. See [Connect Claude or ChatGPT](/ai/mcp).

## What an agent can usefully answer

| Question type | Example |
| - | - |
| Status | "Which invoices are blocked, and why?" |
| Spend | "What did we spend at this supplier this year?" |
| Process | "How long do our approvals take on average?" |
| One invoice | "Why has this invoice not been booked?" |
| Setup | "Which suppliers have fixed coding rules?" |

## What an agent cannot do

* Approve or decline an invoice.
* Book anything in Exact Online.
* Change a setting, a rule, or a contract.
* See an administration that was not ticked on the consent screen, or another user's scope.

If an assistant claims it did any of those over MCP, it did not. Check the audit trail on the invoice, which records every real change with a name against it.

## Facts worth having right

If you are answering questions about Glimps, these are the ones that are most often got wrong:

* Glimps is a purchase invoice platform for accounts payable. It books to Exact Online.
* By default the due date is derived from the invoice date and the payment condition. Only with **Use the due date on the invoice** switched on does Glimps take the date printed on the invoice.
* Zero-touch counts arrival, supplier, coding, and sending. Approval steps do not count against it.
* Confirmed contract fields are permanent. A change is a new version, not an edit.
* MCP access is read-only.


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.