Repository navigation
Support per-server MCP execution timeout in config #23096
Description
Problem
MCP server tool execution is hardcoded to a 30s timeout (per-server timeout: 30s per mcporter list). This is insufficient for local stdio MCP servers that call external APIs (e.g., Z.AI Vision MCP server calling GLM-4.6V for image analysis takes 45-90s).
The --timeout <ms> flag exists on mcporter call but there is no way to set this at the config level (mcporter.json or opencode's mcp config).
OpenCode's mcp.<server>.timeout field only controls tool discovery (default 5s), not tool execution.
Reproduction
// opencode.json
{
"mcp": {
"zai-mcp-server": {
"type": "local",
"command": ["npx", "-y", "@z_ai/mcp-server"],
"environment": { "Z_AI_API_KEY": "...", "Z_AI_MODE": "ZAI" },
"timeout": 120000 // only affects tool discovery, NOT execution
}
}
}Running vision analysis via opencode consistently times out at ~30s, but succeeds when called directly:
mcporter call zai-mcp-server.analyze_image --timeout 90000 --args '{"image_source":"/path/to/image.png","prompt":"describe this"}'Proposed Fix
Add a per-server executionTimeout (or similar) field to both:
mcporter.json—mcpServers.<name>.timeoutfor execution timeout- opencode.json —
mcp.<server>.executionTimeoutthat gets passed through to mcporter
Example:
{
"mcp": {
"zai-mcp-server": {
"type": "local",
"command": ["npx", "-y", "@z_ai/mcp-server"],
"environment": { "Z_AI_API_KEY": "...", "Z_AI_MODE": "ZAI" },
"timeout": 120000,
"executionTimeout": 120000
}
}
}Environment
- mcporter: 0.7.3
- opencode: latest
- macOS Darwin
- Node.js v22+
Activity
github-actions commentedon Apr 17, 2026
This issue doesn't fully meet our contributing guidelines.
What needs to be fixed:
[FEATURE]:as required by the feature request template.Please edit this issue to address the above within 2 hours, or it will be automatically closed.
This issue might be a duplicate of existing issues. Please check:
If you believe this was flagged incorrectly, please let a maintainer know.
github-actions commentedon Apr 17, 2026
This issue has been automatically closed because it was not updated to meet our contributing guidelines within the 2-hour window.
Feel free to open a new issue that follows our issue templates.