docs: add Bourdon as stdio MCP server example in mcp.example.json

[ryandavispro1-cmyk]

Summary

The current config/mcp.example.json only shows the sse transport. This PR adds a second entry showing the stdio transport shape alongside it. Concrete second example, no behavior change.

The new entry points at Bourdon, a cross-agent memory federation server that speaks MCP via fastmcp's stdio default. Once a user has pip install bourdon in their environment, the entry as written makes seven tools available to the OpenManus agent — query_agent_memory, list_recent_work, find_entity, get_cross_agent_summary, prepare_recognition_context, get_deeper_context, and (v0.6.0+) commit_to_federation — plus the agent-library:// MCP resources.

Diff

       },
+      "bourdon": {
+        "type": "stdio",
+        "command": "bourdon",
+        "args": ["serve", "--quiet"]
+      }

5 lines added to a JSON example file. No code changes elsewhere.

Why

Three reasons this fits as an example rather than just docs:

1. Documents both transports the MCPRunner supports. The existing example only covers sse; adding a stdio entry alongside makes the file a more complete reference for new users learning the schema.
2. Real, runnable second example. Anyone with Python on their machine can pip install bourdon && bourdon serve --quiet and see the entry work — no separate service needs to be running.
3. No coupling to Bourdon. The example doesn't make Bourdon a dependency or change OpenManus behavior in any way. It's a documentation/example-content change.

PATH gotcha

MCP hosts launch stdio servers as subprocesses with a minimal PATH — often just system defaults, not the user's shell. If bourdon lives in a venv, the bare "command": "bourdon" won't resolve and the server will silently fail to start. The fix is the same pattern other MCP integration docs use (e.g., Bourdon's docs/integrations/claude-desktop.md and docs/integrations/claude-code.md): replace "command": "bourdon" with the absolute path to the venv's bourdon binary, e.g.:

{
  "command": "/Users/you/.venv/bin/bourdon",
  "args": ["serve", "--quiet"]
}

Run which bourdon (macOS/Linux) or Get-Command bourdon (Windows PowerShell) in the venv to find the right path.

Integration guide

Full walkthrough on the Bourdon side: https://github.com/getbourdon/bourdon/blob/main/docs/integrations/openmanus.md. Includes the visibility model, the sse fallback (HTTP transport for users running L6 as a long-lived service), verification steps, and tradeoffs.

Test plan

• JSON validates (no syntax errors)
• Diff is purely additive (no removed entries, no semantic change)
• Command (bourdon serve --quiet) matches Bourdon's canonical integration docs for Claude Desktop, Claude Code, and Cursor
• CI green
• Cross-referenced from Bourdon's docs/integrations/openmanus.md and docs/agent-integration-status.md

Happy to drop the new entry from the example if you'd prefer the example file stay single-entry; in that case I'll move it to a new config/mcp.example-stdio.toml so the stdio shape still has a documented home.

🤖 Generated with Claude Code

[ryandavispro1-cmyk]

Check