The Tesylate connector for Claude

In plain English: Connect Claude to Tesylate once, and Claude can answer questions from your own numbers, show you a dashboard inside the conversation, and read or update records in your business apps. It signs you in with your own Tesylate account, so it can only see what you can see. You can disconnect at any time.

What the connector does

Tesylate puts the systems your business already runs on — accounting, CRM, ERP, ecommerce, support — into one governed data model. This connector exposes that model to Claude, so you can work with it in conversation instead of opening the app:

• Ask questions of your data. Metrics over a time window, broken down the way you’d ask a colleague, with the same definitions the Tesylate reports use.
• Open a dashboard in the chat. Your Tesylate dashboards render inside Claude, and you can drill from a number to the rows behind it.
• Work with Module Builder records. List and read the modules your team has built, create an entry, update one, or move an entry’s status.

It is a read-first connector. The three write operations — create an entry, update an entry, set an entry status — are marked as writes, so Claude can ask for your approval before it runs one.

Before you start

You need:

1. A Tesylate account with access to at least one tenant. If your organisation isn’t a Tesylate customer yet, book a demo — the connector reads a Tesylate workspace, so there’s nothing for it to connect to without one.
2. Claude on a plan that allows connectors, on the web, desktop or mobile. On a Team or Enterprise plan, an owner may need to add the connector for your organisation first.
3. Nothing else. There is no API key to generate, no token to paste and no software to install.

Connecting

You can add Tesylate in either of two ways. Both use the same connector and the same sign-in.

From Claude’s connector directory (once Tesylate is listed there):

1. In Claude, open Settings → Connectors and browse the connector directory.
2. Find Tesylate and select Connect.

As a custom connector:

1. In Claude, open Settings → Connectors → Add custom connector.

2. Enter the connector URL:

   https://app.tesylate.com/mcp/directory

Either way, sign-in then works like this:

1. Claude opens Tesylate in your browser. Sign in with the account you normally use for the Tesylate app — you never type your Tesylate password into Claude.
2. Review the access screen. It shows the tenant the connection will use and the permissions being requested. Approve them and you’re returned to Claude.
3. Start a new conversation and ask Claude something about your data. If you’re not sure where to start, try one of the example prompts below.

To disconnect, remove the connector in Claude’s connector settings. You can also disconnect from the MCP connectors page in your Tesylate settings, and every token on that connection stops working straight away.

How sign-in works

The connector uses OAuth with PKCE. Claude registers itself with Tesylate’s authorisation server, you sign in to Tesylate, and Tesylate issues a token bound to your user, your tenant and this connector. The token carries exactly these permissions:

Scope	What it allows
mcp.modules.read	Read module definitions and their fields
mcp.modules.entries.read	Read entries in modules you can access
mcp.modules.entries.write	Create and update entries, and set entry status
mcp.dashboards.read	List and render dashboards you can access
mcp.matrix.read	Query metrics and drill into the rows behind them
offline_access	Keep the connection working between sessions

Your Tesylate roles and permissions still apply on every call. The connector cannot see a module, dashboard or figure that you couldn’t open in the app yourself, and it never receives the credentials for your underlying source systems — those stay server-side in Tesylate.

Working with more than one tenant

If your account reaches more than one Tesylate tenant, the connection has a default tenant, and every tool except List Tenants accepts an optional tenant argument. Ask Claude “which Tesylate tenants can you see?” to list them, then name one in your question — “…in the Manufacturing tenant” — to work there for that request.

Example prompts

• “What did we invoice last month, and how does that compare with the month before?”
• “Open the sales wallboard dashboard.”
• “Which orders make up that £48k figure? Show me the rows.”
• “What modules do we have, and what fields are on the site visits one?”
• “Log a site visit for tomorrow morning against the Riverside project.”
• “Search Tesylate for anything to do with returns.”

What the connector exposes

Fourteen tools, all of them scoped to your permissions:

Tool	Reads or writes
List Tenants	Read
Search Tesylate	Read
Ask Data	Read
List Modules	Read
Get Module	Read
List Entries	Read
Get Entry	Read
Get Entry Status	Read
List HTML Dashboards	Read
Render HTML Dashboard	Read
Drill Down Matrix Data	Read
Create Entry	Write
Update Entry	Write
Set Entry Status	Write

There are no delete operations. Administrative surfaces — building modules, editing dashboards, changing tenant settings, running actions against your source systems — are deliberately not part of this connector. They stay in the Tesylate app.

Data handling

• Requests are made by you, in your conversation, against your own tenant. Tesylate returns only the data the tool was asked for.
• Tesylate receives the requests Claude makes, with their arguments. It does not receive your conversation with Claude or your Claude account details.
• What Claude reads from Tesylate goes to Anthropic, under your organisation’s own agreement with them.
• Each request is logged for security and support — who, when, which tool, whether it was allowed and whether it worked — but not the data sent or returned. Full detail is in our privacy notice.
• We don’t use your business data to train models or to improve the service; clause 7 of our terms allows only aggregated, non-identifying operational statistics.
• The endpoint accepts up to 100 requests a minute per access token. Beyond that it answers with HTTP 429 and a Retry-After header.

Troubleshooting

Claude can’t reach the server. Check the URL is exactly https://app.tesylate.com/mcp/directory, with no trailing slash or extra path.

Sign-in completes but nothing is visible. You’re probably connected to a tenant where your account has no module or dashboard permissions. Ask Claude which tenants it can see, or ask your Tesylate administrator to check your role.

A dashboard won’t open. Claude can show a dashboard once it has been published in Tesylate. A dashboard built as a custom interface opens only in the Tesylate app; Claude says so and gives you the link.

A write is refused. Create, update and status changes need the mcp.modules.entries.write permission and the matching role in Tesylate. Read access alone will decline them.

Support

Email support@tesylate.com or call 020 3880 9872. We answer connector questions the same way we answer anything else on the platform — from a person who knows your data model.