MCP Server

Connect FlorianAI to your Claude, ChatGPT, or Copilot.

Ask the assistant your department already uses about your records, dispatch, scheduling, reporting, and training data. It reads from your actual systems. It never writes back.

  • Lovable
  • Microsoft Copilot
  • Claude
  • ChatGPT

01 System Access

Your AI tool is the only thing without access to your data.

You already use Claude or ChatGPT. It will draft a grant narrative, summarize a standard, and clean up a memo to the city manager. It cannot tell you how much overtime Station 3 ran last month, because it has never seen your systems.

That answer lives across platforms that do not talk to each other. Getting it means exporting from each one and stitching them together by hand.

FlorianAI MCP closes that gap. Once your department connects it, the assistant you already open can reach your systems directly and answer from your actual records.

It can write your grant narrative. It can’t tell you what Station 3 ran last month.

RMS Reports
Incident Reports (CAD)
Staffing Schedules
SOPs
NERIS
Certifications & Training
FlorianAI MCP
Answered in your own Claude
Answered in your own ChatGPT
Answered in your own Copilot
Every answer naming the systems behind it

02 What You Can Do

Not just answers. Reports and charts too.

  1. 01

    Ask questions straight from your department’s data.

    Questions that used to take four exports, answered in one.

    Staffing and coverage

    • How many engines are in service tonight?
    • Who's qualified to staff the ladder company today?

    Reporting and incidents

    • What's our NERIS reporting status this month?
    • Summarize last shift's incident reports.

    Training and certification

    • Which members are due for SCBA recertification?
    • Which certifications lapse before the next apparatus assignment?

    The ones no single system can answer

    • Is response quality slipping on minimum-staffing days?
    • Where do incident types outrun what our training records cover?
  2. 02

    Generate dynamic reports.

    Ask for the report in plain language. It is built from your current records, not last month’s export. Change the question and you get a new report instead of a new request to somebody else.

    • Incident volume
    • Unit workload
    • Coverage gaps

    Station 4 Overtime Summary — Last 90 Days

    Station 4 accounted for 31% of department overtime hours over the last quarter, the highest of any station, driven by shift coverage rather than incident holdover.

    Key Findings
    • Overtime hours: 614 total, up 8% over the prior quarter
    • Coverage: 11 shifts filled below minimum staffing before callback
    • Driver: 74% of overtime traced to unfilled vacancies, not incidents

    Callback volume concentrates on the C shift, where two vacancies remain unfilled. Holdover hours held flat across all three shifts.

    Trend

    Overtime has risen for three consecutive quarters at Station 4 while holding steady department-wide, which points to a staffing gap local to...

  3. 03

    Populate interactive charts and dashboards.

    The same answer, drawn. Ask for run volume by station or overtime by month and you get a chart you can push on. Change the window or split it by shift and it redraws.

You are not waiting on a report somebody else builds. You ask the question and you get the answer, and the export-and-stitch step is gone rather than moved somewhere else. Records management, dispatch, scheduling, SOPs, NERIS, and certifications are where it reaches today, and that is not a closed list. If your department runs a system that is not there, ask us about it.

03 Control

Read-only, with sources on every answer.

It reads. It never writes.

The first release retrieves data and nothing else. It cannot create, edit, close, or delete a record in any system it reaches. Nothing it does changes an incident, a schedule, a certification, or a policy.

Every answer names its sources.

Answers name every system consulted and link you straight to the source policy document, so you can go read the passage yourself instead of taking the output on faith.

04 Governance

Your people are already asking AI questions. This is the version you can govern.

A CPSE survey of 156 chiefs at accredited departments found that only 14% have a formal AI policy, while 40% already work in an agency that provides access to AI tools. The question in most departments is not whether AI is in the firehouse. It is whether it is connected to anything the chief controls.

Exports pasted into a personal chatbot

  • Department data leaves on a personal account
  • Whatever was pasted in is outside your control
  • The answer cites nothing, so nobody can check it
  • Stale the moment the export is made
  • Runs on department-provisioned access
  • Scoped to the access your department grants
  • Every answer names the systems behind it
  • Reads current records, not last month's spreadsheet

Nothing here requires you to have an AI policy first. It does give you something a policy can point at. See the full comparison →

05 Frequently Asked Questions

FAQ

What chiefs ask before connecting FlorianAI to their own assistant.

What is MCP?

MCP stands for Model Context Protocol, an open standard that lets an AI assistant reach data held in systems outside itself. FlorianAI, an AI operations assistant built for fire departments, uses it to give your Claude, ChatGPT, or Copilot account access to the systems your department already runs. You do not need to understand the protocol to use it.

Do I need a Claude, ChatGPT, or Copilot account?

Yes. You ask the question inside the assistant you already use, so your department needs an account with one of those providers, or with another assistant that supports MCP. If you do not have one yet, we will walk you through it during setup.

Does this require my IT department?

No. We handle the connection with you during setup. There is nothing to install on a station computer and nothing for your personnel to configure.

Can it change anything in FirstDue, our RMS, or our schedule?

No. The first release is read-only. It retrieves data and answers questions. It cannot create, edit, close, or delete a record in any system it reads.

Where does my department's data go?

Your question and its answer pass through the AI account your department connects, the same way anything else typed into that assistant does. FlorianAI retrieves only what is needed to answer, using access your department provisions. If your department has an AI use policy, review this the way you would any other approved tool. We are glad to be part of that conversation.

What systems does it reach today, and what is coming?

It reaches the systems FlorianAI already connects to, including records management, dispatch, scheduling, reporting, policy libraries, and training platforms, with more added continuously. The first release focuses on retrieving data. Additional FlorianAI capabilities will open through the same connection over time.

What does it cost?

The connection is part of FlorianAI. Book a demo and we will walk through what it looks like for your department.

Bring the question you can’t answer today.

Come to the demo with the question that currently takes four exports and a morning. We will show you what it looks like when you can just ask it, in the assistant you already have open.