Flespi MCP Server

MCP server for Flespi telematics platform API - provides 157 tools for fleet management, device tracking, and telemetry data processing

Local serverstdio

What is the Flespi MCP server?

Flespi MCP server exists for a simple reason — assistants are far more useful when they can act on Flespi directly instead of describing what you should do. MCP server for Flespi telematics platform API - provides 157 tools for fleet management, device tracking, and telemetry data processing.

What you get

Un servidor MCP (Model Context Protocol) para la API completa de Flespi, que permite a los LLMs interactuar con la plataforma de telemática Flespi.

What the assistant can call

Once Flespi is connected, these are the calls the assistant has available:

  • Devices — Gestión de dispositivos de rastreo
  • Channels — Canales de entrada para protocolos de telemetría
  • Streams — Transmisión de datos hacia sistemas externos
  • Calculators — Motor de análisis e informes
  • Assets — Entidades virtuales para seguimiento multi-dispositivo
  • Plugins — Extensiones de funcionalidad
  • Geofences — Geocercas para análisis geoespacial
  • Groups — Organización y gestión masiva
  • Modems — Envío de SMS y comandos
  • flespi_get_devices — Listar dispositivos
  • flespi_post_devices — Crear nuevos dispositivos
  • flespi_get_devices_messages — Obtener mensajes de dispositivos

Setting it up

Installation goes through your MCP client rather than a global install: point it at @modelcontextprotocol/inspector on npm and it is fetched when the client starts. The copy-paste blocks for Claude Desktop, Claude Code and Cursor are further down this page.

Choosing this one

Among the developer tooling options, the useful question is rarely "what can it do" but "what does it cost you to run" — permissions, credentials, and how much of your context its toolset consumes. Flespi's toolset — Devices, Channels, Streams and 11 more — is a fair guide to whether it matches your workflow. It is maintained by gperezt222; worth a glance at recent repository activity before you build anything load-bearing on it.

SyncDev reviews every entry in this directory against the project's own documentation before publishing, and revisits them as servers change.

Before you rely on it

  • It runs with your machine's permissions. That is convenient and also the reason to think about what you point it at before you approve a tool call.
  • With 14 tools registered it takes up a noticeable share of the context window; turn it off in projects that never touch Flespi.
  • MCP clients confirm each tool call by default. Leave that on until you have watched what the flespi mcp server does with a few real requests.

Available tools

ToolWhat it does
DevicesGestión de dispositivos de rastreo
ChannelsCanales de entrada para protocolos de telemetría
StreamsTransmisión de datos hacia sistemas externos
CalculatorsMotor de análisis e informes
AssetsEntidades virtuales para seguimiento multi-dispositivo
PluginsExtensiones de funcionalidad
GeofencesGeocercas para análisis geoespacial
GroupsOrganización y gestión masiva
ModemsEnvío de SMS y comandos
flespi_get_devicesListar dispositivos
flespi_post_devicesCrear nuevos dispositivos
flespi_get_devices_messagesObtener mensajes de dispositivos
flespi_put_channelsActualizar canales
flespi_delete_streamsEliminar streams

How to install the Flespi MCP server

{
  "mcpServers": {
    "flespi": {
      "command": "npx",
      "args": ["-y", "@modelcontextprotocol/inspector"]
    }
  }
}

Add to claude_desktop_config.json, then restart Claude Desktop.

Example prompts to try

  • Use Flespi to Devices.
  • Use Flespi to Channels.
  • Use Flespi to Streams.

Frequently asked questions

It connects Flespi to MCP-compatible AI assistants such as Claude and Cursor, exposing 14 tools (Devices, Channels, Streams, and more) that the assistant can call on your behalf. Instead of copying data back and forth by hand, the assistant works with Flespi directly.