Gud API MCP

What gud-api-mcp does

The gud-api-mcp MCP server gives AI agents a way to create, execute, and save API requests as Gud API collections inside a project. It is the agent-facing companion to Gud API, an editor-based API client for testing REST and GraphQL services.

Use it when an agent needs to assemble requests, send them, and preserve useful requests for later work. Saved requests can be opened and organized with the Gud API editor extension, which supports collections and folders.

It does not document a complete tool schema, individual argument names, response formats, or additional MCP operations.

How it works

The gud-api-mcp MCP server is distributed as the public npm package @gudlab/gud-api-mcp. An MCP client starts it with npx, passing a project directory through the --project argument:

{
  "mcpServers": {
    "gud-api": {
      "command": "npx",
      "args": ["-y", "@gudlab/gud-api-mcp", "--project", "."]
    }
  }
}

The project argument establishes the location associated with the requests and collections the agent works with. The repository for the MCP server is separate from the Gud API editor extension repository. The editor extension itself is proprietary; the MCP server is public and has its own license.

An agent can use the server to prepare a request, execute it against an API, and save the request as a Gud API collection item.

Setup and configuration

Install no editor source from the main Gud API repository: that repository contains product documentation and issue tracking, not the extension implementation. Configure the MCP package in an MCP client using the npx command shown above, and replace . with the project path the agent should use when necessary.

The documented setup requires Node.js tooling capable of running npx, the @gudlab/gud-api-mcp package, and a project path. Further server-specific setup details are available in the Gud API AI-agent guide and the separate MCP repository.

Tools and capabilities

The gud-api-mcp MCP server supports these documented agent activities:

• Create API requests.
• Run API requests.
• Save requests as Gud API collections in a project.

Gud API itself supports REST and GraphQL requests, collections, folders, environments, authentication, and code generation in the editor extension. Those are product capabilities described for the editor and should not be treated as confirmed MCP tools unless the separate MCP documentation exposes them.

Limitations and notes

The main Gud API repository does not contain the editor extension source. It points to a separate public repository and npm package for the MCP implementation, so the exact tool definitions must be checked there before building against a specific schema.

It also does not document MCP-specific client compatibility. The standard configuration uses a local stdio-style command launched with npx.

The gud-api-mcp MCP server should therefore be evaluated primarily for project-local API request creation, execution, and collection persistence. Do not infer the full feature list of the Gud API extension from the MCP listing alone.