Error calling tool xxx: context deadline exceeded

[jfdenise]

I have implemented a very simple tools that returns a string containing some raw Prometheus metrics.
When testing the server with npx @modelcontextprotocol/inspector the server runs perfectly and is very fast.

I am calling: ./mcphost_Linux_x86_64/mcphost --config mcp.json --model ollama:qwen2.5:3b

The output is:

2025/01/16 18:42:26 INFO Model loaded provider=ollama model=qwen2.5:3b
2025/01/16 18:42:26 INFO Initializing server... name=fetch
2025/01/16 18:42:26 INFO Initializing server... name=wildfly
2025/01/16 18:42:27 INFO Server connected name=wildfly
2025/01/16 18:42:27 INFO Server connected name=fetch
2025/01/16 18:42:27 INFO Tools loaded server=fetch count=1
2025/01/16 18:42:27 INFO Tools loaded server=wildfly count=1
┃ Enter your prompt (Type /help for commands, Ctrl+C to quit)                   

When I am asking a question releated to the metrics, I am getting the following error and and reply....

2025/01/16 18:43:33 INFO 🔧 Using tool name=wildfly__getMetrics

Error calling tool getMetrics: context deadline exceeded

Even when enabling --debug, I have no clue of what is going on.

Thank-you for your assistance.

[moresearch]

mcphost -m ollama:granite3.2:8b-instruct-q8_0 2025/03/17 11:56:33 INFO Model loaded provider=ollama model=granite3.2:8b-instruct-q8_0 2025/03/17 11:56:33 INFO Initializing server... name=github 2025/03/17 11:56:35 INFO Initializing server... name=filesystem Error: error creating MCP clients: failed to initialize MCP client for filesystem: context deadline exceeded

Same issue here! What is that all about?

[gmlewis]

I'm also getting this when I use this configuration:

{
  "mcpServers": {
    "filesystem": {
      "command": "npx",
      "args": [
        "-y",
        "@modelcontextprotocol/server-filesystem",
        "/tmp/demo"
      ]
    }
  }
}

[moresearch]

The main issue here is that sometime it takes too long for the LLM to respond, so either you dont use a deadline or extend it to a proper duration.

[lordzorn]

I had same issue in macOS. Issue resolved after updating to the latest version of node and npm.