Logflare MCP Code Mode
Related Servers
Alternatives to Logflare MCP Code Mode
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityFmaintenanceEnables 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 npm128Apache 2.0

@roarkanalytics/sdk-mcpofficial
AlicenseNot gradedqualityAmaintenanceEnables 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 npmApache 2.0- FlicenseNot gradedqualityBmaintenanceA 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.-
- AlicenseAqualityFmaintenanceEnables 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.510MIT
- FlicenseNot gradedqualityBmaintenanceEnables 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.-
- FlicenseCqualityDmaintenanceEnables on-demand generation of TypeScript tools using an LLM with human-in-the-loop approval and safe sandboxed execution. It allows users to create and persist custom functionality through natural language requests.81-
TDQS
Scored across 3 tools
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.
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.
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.
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.