Skip to content

MCP compatibility: don't error when prompts/list is unsupported (-32601) #26048

Closed

Description

@122yjs

Summary

When an MCP server does not implement prompts/list, OpenCode Desktop logs repeated errors like:

  • MCP error -32601: Method not found failed to get prompts

This appears to be a compatibility issue rather than a true server failure. Many MCP servers provide tools but no prompts.

Environment

  • OpenCode Desktop: 1.14.28
  • macOS: Apple Silicon
  • MCP servers observed: context7 (local), grep_app (remote)

Reproduction

  1. Configure an MCP server that supports tools but does not support prompts.
  2. Start OpenCode Desktop.
  3. Observe logs in ~/.local/share/opencode/log/*.log.

Actual behavior

OpenCode treats missing prompts support as an error and repeatedly logs -32601 Method not found.

Expected behavior

If prompts/list is unsupported (-32601), OpenCode should treat it as "no prompts" and continue without error-level logging.

Why this matters

  • Creates noisy logs and false alarms.
  • Makes healthy MCP setups look broken.
  • Impacts multiple MCP servers, not one specific provider.

Suggested fix

In MCP prompt discovery, catch -32601 / "Method not found" for listPrompts() and return [].

Pseudo behavior:

await client.listPrompts()
  .then(r => r.prompts)
  .catch(err => {
    if (err?.code === -32601 || /Method not found/i.test(err?.message ?? "")) {
      return []
    }
    throw err
  })

Temporary workaround I validated locally

I patched the Desktop app bundle to ignore -32601 for prompt listing, and the repeated MCP prompt errors disappeared while tool calls still worked.

Activity

  1. github-actions commented on May 6, 2026

    @github-actions
    Contributor

    This issue might be a duplicate of existing issues. Please check:

  2. 122yjs commented on May 7, 2026

    @122yjs
    Author

    I checked this again against v1.14.40.

    Results:

    So v1.14.40 fixes the separate macOS watcher packaging issue, but it does not appear to fix this MCP optional-method compatibility issue yet.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

Labels

No labels
No labels

Type

No type

Projects

No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions