Skip to content
Intlexl

MCP and connectivity

Bring your own AI. Keep your own rules.

Any MCP client can work with your projects through a token you create, limit and can revoke. Intlexl checks every call against the same permissions a person would face.

Book a demoRead about security

One conversation, real changes

A client asks. Intlexl does it, and logs it.

The client picks the tools. Intlexl applies your permissions, runs them, and records what happened.

MCP client · connected to Intlexl
Tools on the server
100+
Token scopes
4
Read, edit, structural, admin
Areas covered
8
Sheets to sharing

Set up

From nothing to a working client in four steps.

  1. 1

    Create a token

    In Settings, name it and choose a scope. It is shown once.

  2. 2

    Add it to your client

    Point an MCP client at the Intlexl endpoint with the token as a bearer credential.

  3. 3

    Ask

    The client lists the tools it may use and calls them for you.

  4. 4

    Review

    See calls in the audit log, and revoke or refresh the token whenever you like.

Tokens

Personal tokens with a scope you choose.

Read to look, edit to change cells and rows, structural to change sheets and workspaces, admin for administrators only. Higher scopes include the lower ones.

  • Revoke or refresh

    Refresh a token after a role change without changing the string in your client.

  • Admin is guarded

    Only an organisation administrator can create an admin token, and admin tools re-check on each call.

What a client can reach

Sheets, schedules, capacity, automations and forms, through the same permissions.

Sheets and rows

List, read, search, edit, create, delete, copy, sort.

Columns and formulas

Add, change type, reorder, fill and compute.

Workspaces and recycle bin

Create, rename, delete and restore.

Schedules

Dependencies, critical path, what-if and dates.

Resource managers

Sources, columns, scope and utilisation.

Automations

Create, switch on and off, read the logs.

Forms

Create, edit and read submissions.

Sharing and roles

For administrators, with the same checks.

FAQ

Questions people ask.

The Model Context Protocol is an open standard that lets AI clients such as Claude call tools on another system. Intlexl runs an MCP server, so a client can look up and change your projects through the same permissions a person would have.

More than 100 tools cover listing workspaces and sheets, reading and searching rows, editing cells and rows, filling and computing columns, creating sheets, editing dependencies, managing resource managers, forms and automations, and, for admins, sharing and roles.

A person creates a personal token with a scope of read, edit, structural or admin. Admin scope can only be created by an organisation administrator, and admin tools check the admin permission on every call. Tokens can be revoked or refreshed at any time.

Yes. MCP calls are written to an audit log, and writes are recorded in the activity log as MCP writes. Write tools accept an idempotency key so a retry does not repeat a change.

Any client that speaks MCP over HTTP with a bearer token, including Claude. The token goes in the client's configuration.

Bring one plan. See it run.

In 30 minutes we set up a workspace like yours and show sheets, Gantt, dashboards, capacity and a PM agent at work.

Book a demoExplore the platform