Skip to main content
Connect your Flespi account so CloudThinker can answer questions about your telematics fleet: which devices stopped reporting, what a device sent in the last day, whether a channel is receiving data, and whether streams are delivering it. Flespi is a telematics backend that receives data from GPS trackers and other IoT devices. CloudThinker talks to Flespi’s own hosted MCP server, signed in with one Flespi token you create.

Supported platforms

Prerequisites

  • A Flespi account with access to the Flespi panel at flespi.io.
  • Permission to create tokens in that account.

Choose a token type

For a read-only ACL token, grant GET on each module agents should see: Leave out any module agents don’t need. Grant write methods (POST, PUT, DELETE) only if you want agents to change things. See Write access.
ACL tokens deny by default, and permissions don’t imply each other. Write access on devices doesn’t include read on devices unless you grant read too.

Setup

1

Create a token in Flespi

In the Flespi panel, open Tokens in the left menu and click +. Set:
  • Name: CloudThinker
  • Type: ACL. In the ACL editor, add one entry per module from the ACL table and allow the GET method on each
  • Expiration: Flespi requires every token to have a TTL or an expiration date. Use a 90-day inactivity TTL. It resets on every call, so a token in active use stays valid, and an idle one is cleaned up
Save the token and copy its value.
2

Add the connection in CloudThinker

Open More → Workspace settings → Connections, stay on the Builtin Connections tab, and select Flespi. Paste the token into FLESPI_TOKEN. Paste only the token value, without a FlespiToken prefix. CloudThinker adds that header itself.Click Connect.Success state: the connection shows Connecting and Verifying, then Connected. If verification fails, it shows Failed and an error message appears. Match the message to Troubleshooting.

Connection details

Agent capabilities

What agents can do depends on what the token allows: Some of Flespi’s AI-assisted tools, such as searching Flespi documentation, draw on your Flespi account’s AI usage allowance. Check the AI tile in the Flespi panel if you rely on them. Plain device, channel, and stream reads don’t.

Verify the connection

Expect a list of device names or IDs with a last-message time for each. A device the token can’t read won’t appear.

Example prompts

Write access

A read-only ACL token is the recommended setup, and Flespi refuses any write it doesn’t permit. If you grant write methods, each write an agent attempts goes through Approvals. Your Rules and Approval mode decide whether it runs, waits for a person, or is refused. Reads never need approval.

Troubleshooting

Flespi deletes a token when it expires. Check the token’s TTL in the Flespi panel, create a new one if it’s gone, and update FLESPI_TOKEN on the connection.
The ACL token lacks the module and method for that request. Add the permission to the token in the Flespi panel. Remember that read and write are granted separately.
The token has an IP allowlist that doesn’t include CloudThinker. Add CloudThinker’s egress IPs to the token’s IP whitelist in the Flespi panel, or remove the restriction. These docs don’t publish CloudThinker’s egress IP list: ask your CloudThinker contact, or contact us.
Flespi limits usage per minute across API, MQTT, and traffic on your account. Ask for narrower ranges or fewer devices at once, or wait a minute and retry.
Your Flespi AI allowance for the month is used up. Device, channel, and stream reads keep working. Check the AI tile in the Flespi panel for your usage.

Security

  • Least privilege — grant only the permissions the agents need for your use case; start read-only and widen later.
  • Read-only by default — use read-only credentials unless you want agents to make changes through this connection.
  • Rotate credentials — rotate keys and tokens on your normal schedule; CloudThinker picks up the new value when you update the connection.
  • Revoke on offboarding — remove the credential at the provider when you delete a connection or a teammate leaves.
  • One token for CloudThinker: don’t share it with other integrations, so you can revoke it on its own.
  • Never a Master token: use ACL with only the modules and methods agents need.
  • Keep the 90-day inactivity TTL: a token in use stays valid. If the connection sits idle that long, Flespi deletes the token and you’ll need a new one. Rotate it on your usual credential schedule as well.

Connections overview

See every service you can connect and how connections work.

Approvals

Decide which writes run, wait for a person, or are refused.