Skip to main content
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:
There is also an index of every page, meant to be fetched whole:
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 is bound to the administration it was made for.
Authenticate with OAuth through the consent screen, or with a bearer token from an API key. See Connect Claude or ChatGPT.

What an agent can usefully answer

What an agent cannot do

  • Approve or decline an invoice.
  • Book anything in Exact Online.
  • Change a setting, a rule, or a contract.
  • See another administration, 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.
  • The due date is derived from the invoice date and the payment condition. It is not copied off the document.
  • 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.