[FEATURE]: Load MCP servers asynchronously to not block startup

Problem

MCP clients (especially remote ones like exa, grep_app, context7) are loaded synchronously during OpenCode startup, blocking the UI from appearing. Users wait 2-3+ seconds before seeing anything.

Solution

Load MCP clients asynchronously after the main UI is ready, rather than blocking startup. If an MCP client is not yet connected when a tool is used, it should either:

Connect lazily when first needed, OR
Show a "connecting..." status and not block the UI

Startup delay data (from logs)

exa (remote): ~2s (OAuth discovery + connection)
grep_app (remote): ~624ms
context7 (remote): ~471ms

Workaround

Users can disable remote MCP clients in config, but this defeats the purpose of having them installed.

Related issues

[FEATURE]: MCP server startup timeout should fallback to lazy-load, not fail #13672: MCP server startup timeout should fallback to lazy-load
[FEATURE]: Lazy/dynamic loading for mcp tools #8277: Lazy/dynamic loading for mcp tools

This issue doesn't fully meet our contributing guidelines.

What needs to be fixed:

No issue template was used. Please resubmit using one of the three required templates: Bug Report, Feature Request (title must start with [FEATURE]:), or Question. This issue appears to be either a bug report or a feature request — please pick the appropriate template and fill in the required fields.

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:

[FEATURE]: MCP server startup timeout should fallback to lazy-load, not fail #13672: MCP server startup timeout should fallback to lazy-load — directly addresses async/background MCP loading
[FEATURE]: Lazy/dynamic loading for mcp tools #8277: Lazy/dynamic loading for MCP tools — same core request of not blocking startup with MCP tool loading
Slow startup (~7 minutes) on OpenCode Desktop v1.2.27 for Linux #18117: Slow startup on OpenCode Desktop — related startup performance issue

If you believe this was flagged incorrectly, please let a maintainer know.

opencode created this issue on its own initiative ^^' but i guess it's fine..

Thanks for updating the issue! It now meets our contributing guidelines — great write-up with the specific timing data. The feature request is clear and well-structured.

One concern is that async / lazy load might affect stability and cache rates as MCP servers injects instructions and tool definitions to the agent. It is the best to start a session with all MCPs loaded. I think lately they made a partial fix by showing a spinner at start up. At least the UX is better.

Fix #110: probe-gate OPENCODE_ENABLE_EXA on --net + drop training-pat…

To stay organized issues are automatically closed after 60 days of no activity. If the issue is still relevant please open a new one.

Hi is there a workaround for this? It takes 18s of coldstart sometimes

Navigation Menu

Repository navigation

[FEATURE]: Load MCP servers asynchronously to not block startup #20755

Problem

Solution

Startup delay data (from logs)

Workaround

Related issues

Metadata

Assignees

Labels

Type

Projects

Milestone

Relationships

Development

[FEATURE]: Load MCP servers asynchronously to not block startup #20755

Description

Problem

Solution

Startup delay data (from logs)

Workaround

Related issues

Activity

github-actions commented on Apr 2, 2026

ccfontes commented on Apr 2, 2026

github-actions commented on Apr 2, 2026

Arcadi4 commented on May 27, 2026

github-actions commented on Jul 27, 2026

devinder-augur commented on Sep 27, 2026

Metadata

Metadata

Assignees

Labels

Type

Projects

Milestone

Relationships

Development

Issue actions