fireboard-mcp
Click on "Install Server".
Wait a few minutes for the server to deploy. Once ready, it will show a "Started" state.
In the chat, type
@followed by the MCP server name and your instructions, e.g., "@fireboard-mcpshow me the current probe temperatures"
That's it! The server will respond to your query, and you can continue using it as needed.
Here is a step-by-step guide with screenshots.
Fireboard MCP
MCP server for the Fireboard BBQ temperature monitoring API. Exposes tools for querying devices, live probe temperatures, Drive fan controller status, and historical cook sessions from any MCP-compatible AI assistant.
Live endpoint: https://fireboard-mcp.up.railway.app/mcp
Authentication
This server uses OAuth 2.0 with PKCE and Dynamic Client Registration — the standard required by MCP clients such as ChatGPT and Claude.
Fireboard's own API has no OAuth support; it only issues tokens via a username/password exchange. This server wraps that exchange behind a proper OAuth 2.0 flow: when you connect your AI assistant it opens a login page hosted by the MCP server, you enter your Fireboard credentials, and the server exchanges them with the Fireboard API for an access token. Your credentials are forwarded directly and are never stored — only the resulting API token is held in memory to authenticate tool calls on your behalf.
Note: The token is stored in memory only. If the server restarts (e.g. after a deploy), you will need to re-authenticate.
Related MCP server: flamerobin-mcp-server
Connecting your AI assistant
Visit https://fireboard-mcp.up.railway.app for setup instructions for ChatGPT, Claude, Claude Code, and Gemini.
The MCP endpoint is: https://fireboard-mcp.up.railway.app/mcp
Tools
Rate limit: 17 calls per 5-minute window. See Fireboard API docs.
Tool | What it does | API calls |
| All Fireboard devices on the account | Cached (2 min TTL); 1 call on cache miss |
| Current probe readings for all devices or a named device | Cached (2 min TTL); 1 call on cache miss |
| Real-time Fireboard Drive fan %, setpoint, and control mode | 1 |
| Recent cook sessions | 1 |
| Session metadata and cook notes | 1 |
| Full temperature time-series | 1 |
| Metadata, notes, and time-series in one call | 2 |
Running locally
npm install
npm run devServer starts at http://localhost:3000. MCP endpoint: http://localhost:3000/mcp.
Environment variables
Variable | Required | Default | Description |
| In production |
| Hostname (no protocol) used to build OAuth redirect URLs and the MCP endpoint. Must be set correctly in production — wrong value breaks OAuth. |
| No |
| Port the HTTP server listens on. |
| No | — | Set to |
| No |
| Override the Fireboard API base URL (useful for testing). |
| No |
| Device list cache TTL in milliseconds. |
This server cannot be installed
Maintenance
Resources
Unclaimed servers have limited discoverability.
Looking for Admin?
If you are the server author, to access and configure the admin panel.
Latest Blog Posts
MCP directory API
We provide all the information about MCP servers via our MCP API.
curl -X GET 'https://glama.ai/api/mcp/v1/servers/benhodgson87/fireboard-mcp'
If you have feedback or need assistance with the MCP directory API, please join our Discord server