mcp: an unknown path answers a plain "not found" without the REST and OpenAPI addresses

Open Beginner friendly
#630 0 comments 0 reactions 0 assignees View on GitHub

Maintainers usually reply within 1 day

Nobody has claimed this yet.

Assessment

Difficulty
2/5
Estimated time
1-3 hours
Newbie friendliness
78/100
Issue type
Bug
Clarity
Clearly specified
Activity status
Active
Tech stack
javascript, node.js
Domain
api, backend

Research direction

Start with pivotkit-mcp/src/http.js and trace how the MCP handler responds to unknown paths. Compare that behavior with the 404 detail in packages/pivotkit-server/src/config.js and the change described in #609. Done means unknown paths include the REST and OpenAPI addresses, either by passing through to the server handler or reusing noRouteDetail.

Written by the indexing model from the issue text.

Description

area:mcp

With pivotkit-mcp installed, pivotkit-mcp/src/http.js answers unknown paths itself with a plain "not found". That answer does not name the REST and OpenAPI addresses that pivotkit-server's own 404 names since #609.

Fix: let the MCP handler pass unknown paths on, or reuse noRouteDetail from packages/pivotkit-server/src/config.js.

Dominant language
JavaScript
Stars
1
Forks
1
Avg merge
3h 10m
Merged PRs (30d)
267

Getting set up

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 eizedev/pivotkit

All issues in eizedev/pivotkit

Similar issues

More JavaScript issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.