[Bug]: CLI MCP generation reports success after HTTP errors and overwrites an existing configuration

Open
#4,344 0 comments 0 reactions 0 assignees View on GitHub

Maintainers usually reply within 1 day

Nobody has claimed this yet.

Assessment

Difficulty
4/5
Estimated time
3-5 days
Newbie friendliness
58/100
Issue type
Bug
Clarity
Clearly specified
Activity status
Active
Tech stack
go

Research direction

Start with cli/src/internal/mcp/generator.go, especially postJSONRPCWithSession, initializeMCPServer, and the output-writing path identified in the issue. Trace how HTTP errors and JSON-RPC results flow through discovery, and check how bodyless 202 notification responses are handled. Done means failed initialization or discovery returns a nonzero exit and preserves the existing file, while successful discovery still generates the configuration.

Written by the indexing model from the issue text.

Description

Aspect/AI Aspect/API Aspect/Configuration. Severity/Major
Description

ap gateway mcp generate in WSO2 API Platform CLI ap v0.9.1 can exit successfully after HTTP authentication or service errors when the error body is a JSON object without a JSON-RPC error property. It treats the missing list result as an empty catalogue and overwrites an existing generated-mcp.yaml with empty lists.

This is incorrect error handling and configuration loss. It does not bypass authentication and does not grant access to protected server data.

Steps to Reproduce
  1. Download and extract the official CLI release ap/v0.9.1.

  2. Download reproduce_mcp.py (Python standard library only).

  3. Run:

    python reproduce_mcp.py --binary /absolute/path/to/ap --case json --case http_503_tools --case http_401_all
    

    On Windows use --binary "C:\tools\ap.exe" and python or py as appropriate.

Each error case writes a marker into a temporary generated-mcp.yaml before invoking the CLI, so preservation can be checked without touching a real configuration. Fixture responses:

  • http_503_tools: initialize succeeds and advertises all capabilities; tools/list responds with HTTP 503 and {"message":"Service temporarily unavailable"}. Other list methods succeed.
  • http_401_all: every POST including initialize responds with HTTP 401 and {"detail":"Unauthorized"}, representing an upstream authentication layer.
Actual result
Case CLI exit Echo tool in output Existing config preserved
json (control) 0 Yes n/a
http_503_tools 0 No No
http_401_all 0 No No

Both error cases print MCP generated successfully., report zero tools, and replace the previous configuration with tools: [], prompts: [], resources: []. In the 401 case the CLI proceeds through every discovery method even though initialization failed. No error is emitted on stderr.

Expected result

Return a nonzero exit status with the HTTP status and a useful error message. Do not write or overwrite the generated configuration after a failed initialization or any failed discovery request. A bodyless 202 notification response should remain a separate accepted case from JSON-RPC request responses.

Source evidence and suggested direction

Check HTTP status before decoding list results, validate the JSON-RPC envelope/result, and commit generated output only after the whole discovery sequence succeeds.

Environment Details
  • Product/component: WSO2 API Platform CLI, official Linux amd64 release ap/v0.9.1 (ap version v0.9.1 (built at 2026-08-07T09:04:19Z)).
  • Test runtime: Linux 6.18.57 x86_64 with glibc 2.41, Python 3.12.14.
  • Source reviewed: api-platform main at 398d50772b5605ffe0d6d8693aa7b9ce7c84032e; inspected, not compiled or executed.
  • All fixtures advertise tools, prompts, resources and logging capabilities, so the separately reported optional-capability issue does not apply here.
  • Evidence boundary: local mock server only; not tested against a WSO2-hosted product instance. No CVSS score is asserted.
Area / Aspect / Severity

Area: CLI. Aspect: Aspect/AI, Aspect/API and Aspect/Configuration. Severity: Severity/Major (provisional functional assessment for maintainer review).

Screenshot and attachments

Screenshot of captured CLI output showing success after HTTP 401/503 and empty generated configuration

Dominant language
Go
Stars
85
Forks
137
Avg merge
1d 12h
Merged PRs (30d)
247

Getting set up

  • No Dockerfile or Docker Compose file
  • Has a pull request template
  • No contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from wso2/api-platform

All issues in wso2/api-platform

Similar issues

More Go issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.