Issue Summary

The Atlassian remote Model Context Protocol (MCP) server advertises the resources capability during the initialize handshake, but subsequent calls to the resources/list method return a JSON-RPC -32601 "Method not found" error. This mismatch violates the MCP specification and specifically blocks integration with AWS Bedrock AgentCore Gateway. Because the gateway is a strict MCP client, it attempts to discover resources based on the advertised capability; when the server returns a "Method not found" error, the gateway aborts the entire target setup, preventing the use of otherwise functional tools.

Steps to Reproduce

1. Attempt to onboard the Atlassian MCP server as a target in AWS Bedrock AgentCore Gateway.

1. Observe the discovery phase where the client performs an initialize handshake.

1. Observe the subsequent failure when the client attempts to call resources/list.

Expected Results

The server should either implement the resources/list method or remove the resources capability from the initialize response so that AWS Bedrock does not attempt to call unimplemented methods, allowing tool discovery to complete successfully.

Actual Results

The server advertises the capability but fails the method call, causing AWS Bedrock to report:
"Failed to connect and fetch tools from the provided MCP target server. Error - Method not found"

The below exception is thrown in the log file:

 
 
 {{{ "jsonrpc": "2.0", "id": 2, "error": { "code": -32601, "message": "Method not found" }}}}

Workaround

Currently there is no known workaround for this behavior. A workaround will be added here when available.