Ironclad / Ironclad/rivet

[Bug]: Playright MCP - McpError: MCP error -32601: Method not found

Open
#523 0 comments 0 reactions 0 assignees View on GitHub
bug
Dominant language
TypeScript
Stars
4.7k
Forks
388
PR merge metrics
No merged PRs in 30d

Description

### What happened?

I am running Playright mcp server locally
``` bash
npx @playwright/mcp@latest --port 8931
Listening on http://localhost:8931
Put this in your client config:
{
"mcpServers": {
"playwright": {
"url": "http://localhost:8931/mcp"
}
}
}
```

when i use MCP Discovery Node with Output Prompts disabled -

Image

I get McpError: MCP error -32601: Method not found

while inspecting with wiremock it seems the prompts call is still made

```
{"method":"prompts/list","jsonrpc":"2.0","id":1}
HTTP/1.1 200 OK
Content-Type: text/event-stream
Cache-Control: no-cache
Connection: keep-alive
mcp-session-id: f51af558-0902-48c7-b2cb-341667a79854
Date: Fri, 12 Sep 2025 20:30:09 GMT
Transfer-Encoding: chunked

event: message
data: {"jsonrpc":"2.0","id":1,"error":{"code":-32601,"message":"Method not found"}}
```

This also happens in STDIO mode

### What was the expected functionality?

MCP Discovery Node's underlying call should respect the toggles on th ui and not call the prompts/list call

### Describe your environment

MacOS
npm --version 11.6.0
node --version v24.2.0
npx --version 11.6.0
Rivet 1.11.3

### Relevant log output

```shell

```

### Relevant screenshots

_No response_

### Code of Conduct

- [x] I agree to follow this project's Code of Conduct

Contributor guide

Open the contributing guide

Research direction

Start at the MCP Discovery Node's handling of the prompts/list request and reproduce the issue with the documented npx Playwright MCP command and client configuration. Inspect the HTTP and STDIO behavior with Output Prompts disabled; done means the underlying call respects the toggle and does not send prompts/list.

Written by the indexing model from the issue text.

Assessment

Tech stack
typescript
Domain
tooling
Issue type
Bug
Difficulty
3/5
Estimated time
1-2 days
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
38/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.