MCP empty response

[Warren Clark]

We are currently building an MCP-based workflow using Atlassian Rovo MCP + Jira Tools via MCP Gateway. The implementation works correctly in a local environment, but when attempting to move toward a more production-grade setup, the MCP server returns an empty list response.

We are looking for guidance on how to properly productionize this architecture and troubleshoot the empty response issue.

We are trying to move from a successful local POC to a reliable production deployment. Any documentation, architectural guidance, or troubleshooting steps would be greatly appreciated.

[Dr Valeri Colon _Connect Centric_]

@Warren Clark I second that welcome. An empty MCP response in production usually points to a difference between the local and deployed environment: auth method, enabled MCP permission groups, token/user permissions, gateway filtering, or network/proxy handling. I’d compare local vs. prod headers, token type, org MCP settings, and tool-list response. Also check Admin audit logs for MCP calls. If tools list locally but not through the gateway, the gateway layer is likely the first place to inspect.

[Rebekka Heilmann _viadee_]

Hi @Warren Clark - welcome to the Community,

can you give us a little more insights in how the connection is setup?

How are you authenticating? What are your MCP settings in admin.atlassian.com? Anything else you're seeing in the response? What's on the other side.. Some 3rd party tool or a custom solution?

...