Skip to content

mcpdo resources/directory/read accepts no URI, so it can never succeed #2767

Closed

Description

@cliffhall

Found during the v2.12.0 release smoke (#2764), while verifying #2740 through both CLIs.

Problem

mcpdo resources/directory/read can never succeed. The command requires a URI but offers no way to pass one:

  • Run without a URI: URI is required … Use --uri
  • Run with --uri skill://data-analysis: rejected as an unknown option
  • Run with skill://data-analysis as a positional argument: rejected with "too many arguments"

The method's command registration in clients/mcpdo/src/connection/mcp.ts (around line 1370) gives resources/read, resources/subscribe and resources/unsubscribe an [uri] argument and a --uri <uri> option, and skills/get gets the same. resources/directory/read is left out of that case, so it falls through to a registration that only takes --metadata. The one-shot CLI is not affected: mcp-inspector --cli <server> --method resources/directory/read --uri skill://data-analysis works.

This predates v2.12.0, since the 2.11.0 mcpdo has the same gap. It is not a regression, but it means #2740's ttlMs/cacheScope result can only be read through the one-shot CLI and web.

Reproduce

mcpdo connect <skills server URL>
mcpdo resources/directory/read --uri skill://data-analysis   # error: unknown option '--uri'
mcpdo resources/directory/read skill://data-analysis         # error: too many arguments
mcpdo disconnect

Expected

The command accepts [uri] / --uri <uri> like resources/read, forwards it, and prints the result (including ttlMs and cacheScope on a modern connection). The fix should add a test in clients/mcpdo/__tests__/ that would have caught the missing option.

Activity

  1. added this to the v2.13.0 milestone on Oct 21, 2026
  2. added
    bugSomething isn't working
    v2Issues and PRs for v2
    on Oct 21, 2026
  3. self-assigned this
    on Oct 21, 2026
  4. modified the milestones: v2.13.0, v2.12.0 on Oct 21, 2026
  5. added a commit that references this issue on Oct 26, 2026
    3a174cb
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

Labels

bugSomething isn't workingv2Issues and PRs for v2

Type

No type

Projects

No projects

    Milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions