Firetiger MCP Server

Firetiger exposes an MCP (Model Context Protocol) server that allows AI assistants like Claude, Cursor, and other MCP-compatible clients to interact with your Firetiger data.

The server uses HTTP streaming transport and authenticates via OAuth with your normal Firetiger credentials. When you first connect from an MCP client, you’ll be redirected to sign in.

Quick start: Visit your deployment’s setup page at /mcp (e.g., https://ui.ft-scaletowin.firetigerapi.com/mcp) for copy-pastable setup commands.

Endpoint

Your MCP endpoint is:

https://api.ft-scaletowin.firetigerapi.com/mcp/v1

Client Configuration

Claude Desktop

Add to your Claude Desktop configuration file (~/Library/Application Support/Claude/claude_desktop_config.json on macOS):

{
  "mcpServers": {
    "firetiger": {
      "url": "https://api.ft-scaletowin.firetigerapi.com/mcp/v1"
    }
  }
}

Cursor

In Cursor settings, add the MCP server configuration:

{
  "mcpServers": {
    "firetiger": {
      "url": "https://api.ft-scaletowin.firetigerapi.com/mcp/v1"
    }
  }
}

Claude Code

Add the Firetiger MCP server using the CLI:

claude mcp add firetiger --transport http https://api.ft-scaletowin.firetigerapi.com/mcp/v1

Then authenticate by running /mcp in Claude Code and following the prompts.

Available Tools

Resource Tools

The MCP server exposes generic CRUD tools that work across all resource collections. Use schema to discover fields and types before creating or updating resources.

Tool	Description
`list`	List resources in a collection. Supports filtering, ordering, and pagination.
`get`	Get full details of a specific resource by name.
`schema`	Get the schema for a collection — field names, types, required/optional, enum values.
`create`	Create a new resource in a collection.
`update`	Partially update an existing resource. Only fields included in the request body are modified.
`delete`	Soft-delete a resource by name.

Resource Collections

Collection	Operations	Description
`known-issues`	List, Get, Create, Update, Delete	Track recurring problems for automatic correlation with future incidents
`notes`	List, Get, Create, Update, Delete	Knowledge base entries and documentation
`connections`	List, Get, Create, Update, Delete	External service connections (Postgres, HTTP, etc.)
`customers`	List, Get, Create, Update, Delete	Customer records and metadata
`investigations`	List, Get, Create, Update	Automated investigation runs
`runbooks`	List, Get, Create, Update, Delete	Operational runbooks
`triggers`	List, Get, Create, Update, Delete	Alert and automation triggers
`scheduled-agent-runs`	List, Get, Create, Update, Delete	Scheduled recurring agent tasks
`agents`	List, Get, Create, Update, Delete	Agent configurations
`sessions`	List, Get, Create, Delete	Agent sessions (nested under agents)
`issue-notification-policies`	List, Get, Update	Notification policy configuration (singleton)

Agent Tools

Tool	Description
`send_agent_message`	Send a message to an agent session and wait for a response.
`read_agent_messages`	Read the message history from an agent session.

Query Tool

Tool	Description
`query`	Execute DuckDB SQL against Firetiger’s Iceberg data warehouse. Supports standard SQL including JOINs, CTEs, and aggregate functions.

Credentials Tool

Tool	Description
`get_ingest_credentials`	Get OTLP ingest endpoint URL and authentication credentials.

Onboarding Tools

These tools appear only when the corresponding integration hasn’t been connected yet. Once you connect a provider, its onboarding tool is automatically hidden.

Tool	Description
`onboard_github`	Connect your GitHub account. Returns an authorization URL to open in your browser.
`onboard_slack`	Connect your Slack workspace. Returns an authorization URL to open in your browser.
`onboard_linear`	Connect your Linear workspace. Returns an authorization URL to open in your browser.

Example Workflows

Investigate issues

Ask Claude to query your logs and investigate problems:

“Figure out the reason the api server is crash looping in staging”

Claude will query your logs, analyze error patterns, and identify the root cause.

Fix a known issue

Ask Claude to work on a known issue tracked in Firetiger:

“Get the known issue ‘memory leak in worker pool’, verify it’s still happening, find the root cause, and fix it”

Claude will fetch the issue details, query recent logs and metrics to confirm the problem, analyze the patterns, and implement a fix.

Create and manage resources

Ask Claude to create or update Firetiger resources directly:

“Create a known issue for the Redis connection timeouts we’ve been seeing under high load”

Claude will call schema to learn the fields, then create to make the known issue.

“Resolve the Redis timeout known issue and add a note explaining the fix”

Claude will update the known issue status and create a note with the details.

Set up telemetry integration

The integrate-firetiger prompt provides a step-by-step guide for adding OpenTelemetry instrumentation to send data to Firetiger. It walks through fetching credentials, exploring your codebase, installing the SDK, and configuring the exporter.

In Claude Code, invoke it with the slash command:

/firetiger:integrate-firetiger

Or ask Claude directly:

“Help me integrate OpenTelemetry into this project to send data to Firetiger”

MCP Server Connections - Connect Firetiger to external MCP servers
OpenTelemetry Integration - Send telemetry data to Firetiger