logflare-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| LOGFLARE_API_KEY | Yes | Access token for Logflare API | |
| LOGFLARE_BASE_URL | No | Base URL for self-hosted Logflare | https://logflare.app |
| LOGFLARE_AUTH_STYLE | No | Authentication style: 'bearer' (default) or 'x-api-key' | bearer |
| LOGFLARE_DEFAULT_SOURCE_TOKEN | No | Default source token used when tool argument is omitted |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": true
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| list_sourcesA | List all sources (log streams) accessible to the configured API key. |
| get_sourceB | Get a single source by its token. |
| get_source_schemaB | Return the inferred schema (field names and types) for a source. |
| get_recent_eventsA | Fetch the most recent log events for a source. Useful for tailing and incident triage. |
| list_endpointsB | List saved query endpoints for the account. |
| query_endpointC | Execute a Logflare endpoint by UUID or name. Pass endpoint parameters as a flat key/value object. |
| execute_queryA | Run an ad-hoc SQL query. Provide exactly one dialect: BigQuery, Postgres, or ClickHouse. Prefer query_endpoint when a saved endpoint exists. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 7 tools
Each tool targets a distinct operation: ad-hoc queries, saved endpoint execution, source retrieval, schema inspection, recent events, and listing. No two tools have overlapping purposes; descriptions clearly differentiate them.
All tool names follow a consistent verb_noun pattern with lowercase and underscores (e.g., execute_query, list_sources). The prefixes 'get', 'list', 'execute', and 'query' are uniformly used for similar actions.
With 7 tools, the server is well-scoped for a logging/query domain. Each tool serves a clear purpose without redundancy, and the count is neither too sparse nor overwhelming.
The tool set covers core operations: listing and inspecting sources, querying via ad-hoc SQL or saved endpoints, and fetching recent events. Missing create/update/delete for sources and endpoints, but these may be out of scope for a read-focused MCP server.