Linear MCP Server Calls Timing Out | Warp | Page 1

deep snow Dec 6, 2025, 2:32 AM

#

I've been having issues with MCP calls to Linear timing out today. It might be related to the marginal WiFi where I have been working. Is there a way to configure MCP server call timeouts? Through the MCP server configuration JSON?

proud nebulaBOT Dec 6, 2025, 2:32 AM

#

Hi @deep snow. I'm kapa.ai, your friendly support bot. I will try to answer your question by searching through the knowledge base. :wave:

#

Warp’s MCP docs and linked issues don’t mention any way to configure per‑server call timeouts (either in the MCP server JSON or elsewhere in Warp). The JSON schema shown for both CLI and SSE servers only covers:

command, args, env, working_directory for CLI servers [MCP basics]
url for SSE servers [MCP basics]

No timeout or similar field is documented, and the timeout / “hang” behavior is only described qualitatively in feedback about the MCP Dev Agent, not as a tunable setting. [MCP Dev Agent issue]

So, based on the available docs:

There is no documented way to configure MCP call timeouts from Warp’s MCP configuration JSON.
Timeouts appear to be controlled internally by Warp, not exposed as user‑configurable options.

If the behavior is blocking you, Warp suggests using different models or debugging via server logs, but nothing about changing timeout values. [Debugging MCP]

If you need finer control right now, the only potential (but indirect) lever would be to run Linear via a CLI relay (like `mcp-remote`) where that tool might expose its own retry/timeout behavior—but Warp’s docs don’t describe or guarantee this. [Linear MCP example]

Note: you can ask me a follow up question by @ mentioning me again :speech_balloon:

#

@deep snow Kapa.ai is still learning and improving, please let me know how I did by reacting below.

deep snow Dec 6, 2025, 3:15 AM

#

Using mcp-remote won't overwrite Warp's timeout, so if that's the issue that's giving me heartburn, this tool is not part of the solution.

deep snow Dec 8, 2025, 8:40 PM

#

I am still having issues with Warp using the Linear MCP Server. It worked a couple times, and now it hangs every call. Should I be turning on some kind of logging and registering a bug report?

#Linear MCP Server Calls Timing Out

If you need finer control right now, the only potential (but indirect) lever would be to run Linear via a CLI relay (like mcp-remote) where that tool might expose its own retry/timeout behavior—but Warp’s docs don’t describe or guarantee this. [Linear MCP example]

Note: you can ask me a follow up question by @ mentioning me again :speech_balloon:

If you need finer control right now, the only potential (but indirect) lever would be to run Linear via a CLI relay (like `mcp-remote`) where that tool might expose its own retry/timeout behavior—but Warp’s docs don’t describe or guarantee this. [Linear MCP example]