How to Connect Claude to FleetSnap (MCP Server)

What MCP actually is, in host terms

MCP stands for Model Context Protocol. It is a standard way for an AI assistant to talk to an outside system. You can think of it as giving Claude a read-only login to your FleetSnap account.

Without it, an assistant knows nothing about your fleet, so you end up copying and pasting numbers into a chat window. With it, the assistant asks FleetSnap directly and answers from your real data - your cars, your trips, your messages, your costs.

It is not a chatbot inside FleetSnap. FleetSnap already has one of those, called Ask AI. MCP is the opposite direction: it brings your FleetSnap data out to the assistant you already use for everything else, so your fleet can sit in the same conversation as the rest of your work.

Step 1: create a token

1. Open FleetSnap and go to Account, then the MCP tab.
2. Under Your tokens, type a name that tells you which client it is for, such as Claude Desktop - MacBook. A name is required.
3. Press Create token.
4. Copy the token immediately. It is shown once and never again.

FleetSnap stores only a hash of the token, so there is no way to look it up later. If you lose it, revoke it and create another. Tokens start with fsmcp_ and expire after 90 days.

If the tab tells you to verify your email address first, do that and come back - creating a token requires a verified email.

Step 2: point your client at the server

Your server URL is your FleetSnap address with /mcp on the end. The Account > MCP page shows it, right above the snippets, and that is the one to copy: it always matches the FleetSnap you are signed in to and therefore the token you just created. On fleetsnap.ai it reads https://fleetsnap.ai/mcp.

It speaks Streamable HTTP and accepts POST only. Both snippets below are shown on the Account > MCP page with your server URL and token already filled in, so the easiest path is to copy them from there. If you are typing them by hand, replace YOUR_SERVER_URL and fsmcp_YOUR_TOKEN_HERE with the two values on that page.

Claude Code

claude mcp add --transport http fleetsnap YOUR_SERVER_URL \
  --header "Authorization: Bearer fsmcp_YOUR_TOKEN_HERE"

Claude Desktop and other MCP clients

{
  "mcpServers": {
    "fleetsnap": {
      "type": "http",
      "url": "YOUR_SERVER_URL",
      "headers": {
        "Authorization": "Bearer fsmcp_YOUR_TOKEN_HERE"
      }
    }
  }
}

The same config works in the MCP Inspector and in any other client that supports an HTTP MCP server with a bearer token.

Step 3: ask it something

Start with this, every time you open a new conversation:

Call fleetsnap_get_context and tell me what you can see.

That tool reports which account is connected, which plan it is on, the timezone your days are measured in, how many vehicles you have, and exactly which of the other tools that plan can use. Everything else depends on it, so it is worth making it the first thing your assistant does.

On Free, fleetsnap_get_fleet_today returns your trips for the day but marks urgent messages, open maintenance and open claims as unavailable. That is deliberate, and it is different from saying there are none. A tool your plan does not cover refuses with an upgrade note rather than handing back an empty list, so an assistant can never tell you "no urgent messages" when the truth is "this plan cannot see them".

Your plan is checked live on every single call. If you upgrade, your existing token widens immediately - you do not need to create a new one.

What you can ask

These all work through the tools above. Your assistant picks the tool; you just ask the question.

The morning check

• What needs my attention on the fleet today?
• Is anything overdue right now?
• Are there any urgent guest messages I have not handled?

Money

• Which of my cars is losing money after depreciation?
• What is my best earner this year?
• Which car costs the most to run relative to what it brings in?

Planning

• What trips do I have next week?
• Show me every trip for the Transit this month.
• Which cars have not been booked recently?

Using FleetSnap itself

• How do I import my Turo earnings statement?
• How do I file a damage claim in FleetSnap?

That last group is answered from FleetSnap's public help docs through fleetsnap_search_docs, which works on every plan and needs no fleet data at all.

Best use cases

Two jobs are worth connecting for on their own. Both came from a real host describing how he wanted to work.

The monthly earnings close-out

At the end of the month you want to know what the fleet actually made, not what it grossed. Ask your assistant to pull your true profit per vehicle after depreciation, your attributed costs, and anything that looks wrong. fleetsnap_ask answers the money questions from your own numbers, and fleetsnap_get_recommendations flags the specific things worth acting on - a car whose depreciation is outrunning its earnings, a monthly cost more than double the fleet median, a car sitting idle while the rest of the fleet booked.

The reading half of that close-out works today. The writing half does not: uploading the statement and entering your costs still happens in FleetSnap, and the assistant will link you to the right screen rather than doing it for you.

The maintenance and claims round

Once a month you go through what is open and decide what to chase. Ask for everything outstanding - on Pro and Concierge, fleetsnap_get_fleet_today returns open maintenance issues and open damage claims alongside the day's trips, and fleetsnap_get_recommendations surfaces claims that have been open 30 days or more with no update in the last 14. From there your assistant can help you think, prioritize, and draft the messages you are going to send.

Again, the round ends in FleetSnap. Assigning work, updating a claim and marking a thread handled are all things you do in the app, and every record comes back with a link to the screen that does it.

Looking after your tokens

• One token per client. If you connect a laptop and a desktop, give each its own. Revoking one then leaves the other working.
• Tokens expire after 90 days. Nothing renews on its own, which is the point.
• Revoking is instant. A revoked token stops working on its very next call, not at the end of the day.
• You cannot retrieve a token. FleetSnap keeps only a hash. Lost it? Revoke and create another.
• Treat it like a password. Anyone holding it can read everything your plan can read. It never expires into something harmless.

Account > MCP lists every token you have ever created, with when it was last used, so you can see at a glance whether an old one is still in play.

If it is not working

The MCP tab is not in my Account page. The server is switched on per environment. If the tab is absent, MCP is not enabled for your account yet.

My client says unauthorized, or 401. The token is wrong, revoked, expired, pasted with a character missing, or pointed at a different FleetSnap than the one that issued it - check the server URL in your client still matches the one on your Account > MCP page. FleetSnap answers all of those the same way on purpose, so the fix is the same too: create a fresh token and paste it again, carefully. Check it still starts with fsmcp_.

I opened the server URL in my browser and got an error. That is expected. The endpoint accepts POST only, so a browser visiting it gets a 405. It is not a sign anything is broken.

A tool says it needs Pro or Concierge. That is your plan, not a fault. fleetsnap_list_trips and fleetsnap_list_messages need a paid plan. Upgrading widens the token you already have.

It says my email is not verified. Verify it from the email FleetSnap sent when you signed up, then create the token.

Everything slowed down or started failing. Each token is limited to 60 calls a minute. A client looping over your whole fleet can reach that; wait a minute and ask for less at a time.