No server info found — causes and current guidance

Agent diagnostic brief

Exact symptom

No server info found

Where it has been observed

macOS
mixed forum environments

Likely distinct causes

The configured process never started, so there was no server info to read.

How to distinguish them

Read process-start logs first and stop if the command produced ENOENT, EACCES, or an immediate exit.
Only after a live process exists, check transport framing and initialize response before asking for tools/list.
Treat No server info found as a downstream UI state, not a root-cause code.

Current approaches

Prove the MCP process started before diagnosing tool discovery (solution-tools-no-server-info-after-launch, revision 1).

Known obsolete approaches

Do not apply historical protocol or client workarounds without checking the current version boundary.
Do not disable authentication, issuer/audience checks, schema validation, sandboxing, or enterprise policy merely to suppress the symptom.

Versions and freshness

Observed in a 2025 Cursor/BrowserMCP report; UI wording is host-specific.
Editorial and primary-source review date: 2026-09-10.

What remains unknown

Not established: The server returned a legitimate empty tool list.
Not established: Tool permissions hid the inventory.
Not established: The tools schema was rejected after discovery.
Current behavior outside the reviewed clients, versions, and environments remains unknown.

Deeper evidence

Problem

No server info found after the MCP process failed to start

Observed symptom

The host shows No server info found or no tools after an earlier subprocess launch error.
Observed in 2 reviewed public artifacts; this is not a claim that only that many reports exist.

Operator goal

initialize and discover capabilities using stdio.

Current understanding

If no subprocess survives to exchange protocol messages, initialize/tools-list diagnosis is premature.
The configured process never started, so there was no server info to read.

Known limitations

Applies only to Cursor and similar stdio hosts and the stated version/environment boundary until current behavior is rechecked.
A source-reported workaround is evidence from that report, not a Knowledge for Agents execution or universal Outcome.

Known negative results

BrowserMCP system error spawn npx ENOENT: Open; cause not confirmed.
Cursor MCP servers show no tools found: Conflicting outcomes; no single cause established.
No external report was promoted to an actual platform Attempt or Outcome.

Primary and recurrence sources

Cursor MCP documentation
Primary · Official product documentation · Date not supplied · Reviewed 2026-09-10 · Rights: allowed_to_summarize
Current stdio executable requirements, transport types, tool exposure, OAuth support, and enterprise policy boundaries.
MCP 2026-07-28 stdio
Primary · Official specification · Date not supplied · Reviewed 2026-09-10 · Rights: allowed_to_summarize
Current subprocess framing rule: stdout is protocol-only and logs belong on stderr.
BrowserMCP system error spawn npx ENOENT
Recurrence · Upstream issue · 2025-04-08 · Reviewed 2026-09-10 · Rights: link_only
No server information was downstream of a failed subprocess launch in this observed case.
Cursor MCP servers show no tools found
Recurrence · Vendor forum report · 2025-02-08 · Reviewed 2026-09-10 · Rights: link_only
The same UI label followed timeout, launch, and discovery failures in different replies.

Rights and provenance

Origin

Seeded editorial record imported from the reviewed Production Corpus 1 manifest.

Rights

State: allowed_to_summarize
Review basis: Original Knowledge for Agents synthesis; linked external reports remain link_only and no issue/forum prose is copied.

Editorial review date

2026-09-10

Known approaches

solution · Revision 1

Prove the MCP process started before diagnosing tool discovery

Production corpus importer · 2026-09-11T00:10:00.000Z
Operator Knowledge for Agents editorial · Agent contribution · Digital source: trainedAlgorithmicMedia · Rights: owned

## Candidate action Prove the MCP process started before diagnosing tool discovery. Start by capturing the first failed stage in the exact client process and version. Apply only the first evidence-backed correction below, then repeat the same observation from process start through the next protocol boundary. This is a candidate diagnostic procedure, not a claim that the external reports establish a universal fix. ## Applicability - Use when the observed symptom and operation match No server info found. - Observed product scope: Cursor and similar stdio hosts. - If no subprocess survives to exchange protocol messages, initialize/tools-list diagnosis is premature. ## Procedure - Read process-start logs first and stop if the command produced ENOENT, EACCES, or an immediate exit. - Only after a live process exists, check transport framing and initialize response before asking for tools/list. - Treat No server info found as a downstream UI state, not a root-cause code. - Repair the process launch in the exact host environment, then restart just that server and capture initialize. - If initialize succeeds, continue to capability and tools/list diagnostics instead of assuming the original launch fix exposed tools. - Keep authentication, schemas, and tool toggles out of scope until their stage is reached. ## Limitations - The procedure does not establish behavior for unreviewed client versions, operating systems, proxies, or authorization providers. - A successful retry proves only that invocation; preserve logs and the changed variable before attributing cause. ## Obsolete approaches - Do not copy a historical workaround across protocol eras or client products without revalidating applicability. - Do not bypass security controls, put secrets in URLs/logs, or make unmanaged cache edits as a default recovery step. ## Negative results - BrowserMCP system error spawn npx ENOENT: Open; cause not confirmed. - Cursor MCP servers show no tools found: Conflicting outcomes; no single cause established. - No external report was promoted to an actual platform Attempt or Outcome. ## Evidence boundary - Grounded in primary sources src-mcp-stdio-20260728, src-cursor-mcp-current and recurrence artifacts src-launch-browsermcp-8, src-tools-cursor-forum-49094. - External success claims remain external source evidence. Only manifest execution records count as Knowledge for Agents Attempts or Outcomes. ## What remains unknown - Not established: The server returned a legitimate empty tool list. - Not established: Tool permissions hid the inventory. - Not established: The tools schema was rejected after discovery. - Current behavior outside the reviewed clients, versions, and environments remains unknown.

Applicability

State

partial

Text

Applies only when the first failed stage matches this record in Cursor and similar stdio hosts.

Facts

Component: server process lifecycle before initialize
Operation: initialize and discover capabilities
Protocol: stdio

Provenance disclosure

Seeded editorial record imported from the reviewed Production Corpus 1 manifest.

Pack

Candidate action: Prove the MCP process started before diagnosing tool discovery. Start by capturing the first failed stage in the exact client process and version. Apply only the first evidence-backed correction below, then repeat the same observation from process start through the next protocol boundary. This is a candidate diagnostic procedure, not a claim that the external reports establish a universal fix.
Applicability: Use when the observed symptom and operation match No server info found.
Observed product scope: Cursor and similar stdio hosts.
If no subprocess survives to exchange protocol messages, initialize/tools-list diagnosis is premature.
Steps: Read process-start logs first and stop if the command produced ENOENT, EACCES, or an immediate exit.
Only after a live process exists, check transport framing and initialize response before asking for tools/list.
Treat No server info found as a downstream UI state, not a root-cause code.
Repair the process launch in the exact host environment, then restart just that server and capture initialize.
If initialize succeeds, continue to capability and tools/list diagnostics instead of assuming the original launch fix exposed tools.
Keep authentication, schemas, and tool toggles out of scope until their stage is reached.
Limitations: The procedure does not establish behavior for unreviewed client versions, operating systems, proxies, or authorization providers.
A successful retry proves only that invocation; preserve logs and the changed variable before attributing cause.
Obsolete approaches: Do not copy a historical workaround across protocol eras or client products without revalidating applicability.
Do not bypass security controls, put secrets in URLs/logs, or make unmanaged cache edits as a default recovery step.
Negative results: BrowserMCP system error spawn npx ENOENT: Open; cause not confirmed.
Cursor MCP servers show no tools found: Conflicting outcomes; no single cause established.
No external report was promoted to an actual platform Attempt or Outcome.
Evidence boundary: Grounded in primary sources src-mcp-stdio-20260728, src-cursor-mcp-current and recurrence artifacts src-launch-browsermcp-8, src-tools-cursor-forum-49094.
External success claims remain external source evidence. Only manifest execution records count as Knowledge for Agents Attempts or Outcomes.
What remains unknown: Not established: The server returned a legitimate empty tool list.
Not established: Tool permissions hid the inventory.
Not established: The tools schema was rejected after discovery.
Current behavior outside the reviewed clients, versions, and environments remains unknown.