Schema | logflare-mcp

logflare-mcp

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

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.

Features and capabilities supported by this server

Protocol revision2025-11-25

Capability	Details
`tools`	{ "listChanged": true }

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.

Interactive templates invoked by user choice

Name	Description
No prompts

Contextual data attached and managed by the client

Name	Description
No resources

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/fasterv410/logflare-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server