Introducing v0.8.0

On August 21, 2025, we released mcp-graphql-forge v0.8.0, a focused maintenance release that strengthens the project’s foundation while improving reliability for users who leverage concurrent tool calls.

This release brings important under-the-hood improvements: a major code refactoring that sets up better structure for future development, and a dependency update that fixes a critical race condition affecting concurrent operations.

What’s New

Enhanced Reliability for Concurrent Tool Calls

The most significant user-impacting change in v0.8.0 is a bug fix inherited from the upstream mcp-go library (updated to v0.38.0). A race condition in the stdio transport has been resolved, which means users who make multiple simultaneous tool calls will experience more predictable and reliable behavior. If your workflow involves concurrent operations, this upgrade addresses potential issues that could have caused failures under load.

Codebase Refactoring for Better Maintainability

We’ve reorganized the project’s internal structure to separate concerns and improve long-term maintainability. The previous monolithic main.go has been modularized into a clean internal/forge package with dedicated files for:

  • Type definitions and configuration loading
  • GraphQL execution logic
  • MCP server handling and tool registration
  • Server startup (HTTP and stdio modes)

This refactoring is entirely internal—your existing configurations, command-line flags, and YAML files continue to work without any changes. However, it establishes a stronger foundation for future feature development.

Community Recognition

We welcomed @Matvey-Kuk as our first-time contributor with PR #29, which added an MCP Trust Score badge to our README. This badge provides transparency about the project’s quality through evaluation by the MCP Catalog at archestra.ai.

Why It Matters

While v0.8.0 doesn’t introduce flashy new features, it delivers what solid engineering looks like: addressing reliability issues before they become problems, and investing in code quality to enable faster innovation down the road.

The concurrent tool call fix is particularly important for users who depend on mcp-graphql-forge in production workflows where multiple operations may execute simultaneously. This update ensures the server handles such scenarios gracefully.

The code restructuring reflects our commitment to maintaining a healthy, extensible codebase. As we continue developing mcp-graphql-forge, this modular architecture will enable us to add features more efficiently while keeping the core experience stable and predictable.

Getting Started with v0.8.0

Upgrading is straightforward—no configuration changes required. Choose your installation method:

GitHub Releases (recommended for most users)
Download the pre-compiled binary for your platform from the v0.8.0 release page. Binaries are available for macOS (Intel and Apple Silicon), Linux (x86_64 and ARM64), and Windows.

From Source
If you prefer building from source or want to install globally:

go install github.com/UnitVectorY-Labs/mcp-graphql-forge@v0.8.0

Existing users: Your forge.yaml configuration files, tool definitions, and usage patterns remain fully compatible. Simply swap in the new binary.

Transparency Note

This release announcement was AI-generated using the unsloth/Qwen3.5-122B-A10B-GGUF:Q4_K_M model on March 17, 2026. The content is based on the official v0.8.0 release of mcp-graphql-forge from UnitVectorY-Labs/mcp-graphql-forge. For questions or corrections, please refer to the repository or contact the author at release-storyteller.