Speakeasy Logo
Skip to Content
Gram DocumentationClientsTroubleshooting

Troubleshooting

Due to the emerging nature of the MCP specification and differences in how various LLM providers and client applications implement it, you may encounter issues when hosting and using MCP servers with Gram. This troubleshooting guide addresses common problems and provides solutions to help you resolve them quickly.

Helpful Resources

The following external resources provide additional context and information about MCP, and may be helpful when troubleshooting issues:

Issues with MCP Remote & Node Environments

Some LLM clients, such as Claude, are not yet able to connect to remote MCP servers natively. To overcome this, the mcp-remote CLI tool is used to proxy requests from the LLM client to hosted MCP servers:

Since version 0.1.26 of the mcp-remote package, some users have reported  servers failing to start, with Client transport closed appearing in client logs.

This is typically due to the LLM client attempting to use an older version of Node to execute mcp-remote than what is required.

Solutions

Ensure that you are using Node.js version 20 or higher. If you run into issues, check in claude desktop logs for what node version it is selecting. Claude desktop has at times shown a tendency to select the lowest version of Node is can find on your machine, regardless of what the default node version is. Instructions for installing and managing Node.js versions can be found on the official Node.js website .

Pin mcp-remote to Version 0.1.25

If you’re not able to install or change to a compatible version of Node, you can pin the mcp-remote package to version 0.1.25 in your MCP configuration.

Getting Support

If you’re encountering a persistent issue that is not covered in this troubleshooting guide, please reach out to Gram support via the in-app chat, or join our Slack community  to get help!

Last updated on