Skip to main content
Glama
Rodriguespn

Logflare MCP Code Mode

by Rodriguespn

Related Servers

Alternatives to Logflare MCP Code Mode

No user-submitted related servers found.

    Related Servers

    • A
      license
      Not graded
      quality
      F
      maintenance
      Enables interaction with the complete Cloudflare API using a codemode pattern that allows agents to search the OpenAPI spec and execute API calls via JavaScript. This approach minimizes token usage by keeping the massive specification on the server and only returning relevant results.
      5 npm
      128
      Apache 2.0
    • A
      license
      Not graded
      quality
      A
      maintenance
      Enables AI agents to interact with the Roark API by writing and executing TypeScript SDK code in an isolated sandbox, with built-in documentation search to guide those tasks.
      2,393 npm
      Apache 2.0
    • F
      license
      Not graded
      quality
      B
      maintenance
      A Code Mode MCP server for the e2b API, giving agents three tools (search, execute_read, execute_write) to write and run JavaScript functions inside sandboxed environments for API discovery and calls.
      -
    • A
      license
      A
      quality
      F
      maintenance
      Enables AI models to dynamically create and execute their own custom tools through a meta-function architecture, supporting JavaScript, Python, and Shell runtimes with sandboxed security and human approval flows.
      5
      10
      MIT
    • F
      license
      Not graded
      quality
      B
      maintenance
      Enables AI coding agents and other MCP hosts to read Elastic Cloud logs across multiple regions using six read-only tools for overviews, deduplicated error patterns, compact searches, context lookup, full log retrieval, and bulk JSONL export.
      -

    TDQS

    A4.6/5.0

    Scored across 3 tools

    Disambiguation5/5

    The three tools have clearly distinct purposes: execute_read for read-only GET requests, execute_write for state-changing requests, and search for exploring the API spec. There is no overlap.

    Naming Consistency3/5

    The naming pattern is inconsistent: two tools use the 'execute_' prefix (execute_read, execute_write), while the third is simply 'search', breaking the verb_noun pattern.

    Tool Count3/5

    Three tools is borderline for a server that aims to cover a full API. While the number is not excessive, it feels minimal, and a typical server might include more dedicated tools instead of relying on generic code execution.

    Completeness5/5

    The tool set covers all possible operations on the Logflare Management API: read, write, and spec exploration. Users can perform any CRUD action via execute_read and execute_write, making the surface complete.

    Maintenance

    ActivityStale
    ResponsivenessNo issues