MCP Servers, fluid compute and 800 second timout

We are running an MCP server on vercel, using the vercel mcp adapter.

We set the timeout out on the MCP endpoint to 800 seconds.
We are connecting via http from claude, using mcp-remote.

We are getting a lot of vercel runtime timeout errors in the logs. The functions are just waiting doing nothing as far as I can tell.

I don’t understand why this is happening. It almost feels like functions are just staying up running with nothing going. But I think we are still going to get billed for the full 13 minutes. Yikes.

Is the streaming http nature of the MCP adapter holding those functions open?

Am I missing something?

Todd

Look at this.

the request comes in, the response is complete as denoted by the mcp response ready line.

yet the connection is still open.

Why?

How do I close the connection?

Todd

upgrading to latest version of the adapter resolved this issue for me

YAY

Todd

Glad it works for you now, Todd!

This topic was automatically closed 7 days after the last reply. New replies are no longer allowed.