A curl-like CLI and universal JavaScript client for GraphQL with autocomplete, subscriptions, and schema introspection.
Graphqurl is a command-line interface and JavaScript library designed for interacting with GraphQL APIs. It functions like curl for GraphQL, allowing developers to execute queries, mutations, and subscriptions from the terminal or programmatically. It solves the problem of needing a simple, scriptable tool to test, debug, and work with GraphQL endpoints without heavy setup.
Developers and DevOps engineers who work with GraphQL APIs and need a lightweight CLI for testing, debugging, or automation, as well as JavaScript developers looking for a minimal GraphQL client library.
Developers choose Graphqurl for its simplicity, versatility, and feature set—it combines a curl-like CLI with a full-featured JavaScript client, supports subscriptions and autocomplete, and requires minimal configuration compared to heavier GraphQL clients.
curl for GraphQL with autocomplete, subscriptions and GraphiQL. Also a dead-simple universal javascript GraphQL client.
Open-Awesome is built by the community, for the community. Submit a project, suggest an awesome list, or help improve the catalog on GitHub.
The CLI mimics curl syntax with flags like -H for headers and -q for queries, making it intuitive for command-line users to quickly execute GraphQL operations without heavy setup.
Schema introspection enables TAB-based autocomplete in the CLI, allowing developers to build queries interactively without external tools, as demonstrated in the demo gif.
Supports real-time data streaming over WebSockets in both CLI and Node.js library, a feature not common in lightweight GraphQL clients, with examples for handling events.
Can be used as a minimal JavaScript client in Node.js or browsers with promise and callback APIs, avoiding heavy dependencies for simple scripting or prototyping.
Version 2.0.0 removed GraphiQL support, forcing users to rely solely on the CLI or other tools for visual exploration, which limits usability for those preferring graphical interfaces.
Lacks built-in caching, error handling optimizations, and type safety that larger GraphQL clients like Apollo offer, making it less suitable for production-scale applications.
Setting up subscriptions requires explicit WebSocket endpoint and callback configurations, which can be error-prone and less streamlined compared to integrated solutions.