ClaudeChatGPTPerplexityGeminiMicrosoft CopilotRaycastMeta AIGrokZ.aiQwenKimi
DeepSeekMistralCursorVS CodeWindsurfJetBrainsClineLovableVercel AI SDKLangChain

Use Logflare with your AI.

Connect your account once and let the AI you already use work with it, without building another integration. Streamline log management and analytics via Logflare. ingest events, execute ad-hoc SQL queries, and trigger pre-configured endpoints directly from your AI age

Included with plan

Ask AI about this Connector

Developed, maintained, and hosted by Vinkius.

MCP VERIFIED · PRODUCTION READY · VINKIUS GUARANTEED

Waiting for input…

Works with modern AI clients that support MCP, including ChatGPT, Claude, Cursor, and more.

ChatGPTClaudeCursorPerplexityGeminiMicrosoft CopilotRaycastMeta AI

Complete set · 5 capabilities

The complete Logflare capability set.

These are the exact actions your AI can choose when you ask it to work with Logflare.

Capability set01 / 02

01-03

3 capabilities in this set.

Part of 5 available through Logflare.

  1. 01

    Query endpoint by name

    Pass interpolation parameters as a JSON object. Query a Logflare Endpoint by Name

  2. 02

    Ingest logs by ID

    Requires ingest scope. Ingest log events into a Logflare source by UUID

  3. 03

    Ingest logs by name

    Requires ingest scope. Ingest log events into a Logflare source by Name

Capability set02 / 02

04-05

2 capabilities in this set.

Part of 5 available through Logflare.

  1. 04

    Management query

    Requires management scope. Must include a WHERE filter on the timestamp field. Execute an ad-hoc SQL query against Logflare

  2. 05

    Query endpoint by ID

    Pass interpolation parameters as a JSON object. Query a Logflare Endpoint by UUID

Observed, not estimated

867ms average. Fast in production.

Logflare is checked daily against the live service.

Daily averagePeak 1082ms
Aug 20Today
Fastest day
694ms
Slowest day
1082ms
14-day trend
Slowing+11%

Connect your client

One URL. Every client.

Activate the Connector, copy your link, and paste it into the client you already use. 5 capabilities arrive ready to run.

Preview access · not provider authentication

The vk_preview_* token belongs to Vinkius preview infrastructure. It lets Claude discover and display the capabilities of Logflare, so you can see the experience inside your AI.

It does not authenticate your account with Logflare. Actions requiring credentials or live account data may not run until you activate the Connector and authorize the service.

Logflare Connector

You're all set. Choose your MCP client and follow the setup instructions.

Connector linkhttps://edge.vinkius.com/vk_preview_vSM9IZDkylvc37x5hEtMMSqMh2HqlPP3QUInZire/mcp

Claude Desktop

Follow the steps below to connect in seconds.

  1. 1In Claude Desktop, open Settings → Connectors.
  2. 2Click “Add custom connector” and paste the connector link above as the remote MCP server URL.
  3. 3Click Add and start a new chat — Logflare capabilities are ready to use.
Configuration · claude_desktop_config.jsonCopy
{
  "mcpServers": {
    "logflare-log-management-analytics-mcp": {
      "url": "https://edge.vinkius.com/vk_preview_vSM9IZDkylvc37x5hEtMMSqMh2HqlPP3QUInZire/mcp"
    }
  }
}
  • Claude
  • ChatGPT
  • Cursor
  • VS Code
  • Windsurf
  • Claude Code
  • JetBrains
  • Cline

Step-by-step instructions for each client are in the guide. How to connect

FAQ

Questions Logflare owners ask.

  • 01

    What are the requirements for running a management query?

    You must provide a valid BigQuery SQL string. Crucially, Logflare requires a WHERE filter on the timestamp field to optimize the query. You can also optionally provide a PostgreSQL version of the query using the management_query capability.

  • 02

    Can I ingest logs using just the source name instead of a UUID?

    Yes! You can use the ingest_logs_by_name capability. Simply provide the human-readable name of your source and the array of log events you wish to send.

  • 03

    How do I pass parameters to a pre-configured Logflare Endpoint?

    Use the query_endpoint_by_name or query_endpoint_by_id capabilities and provide a JSON object in the params field. For example: {"user_id": "123", "status": "active"}.