Add an opt-in Parallel Search MCP configuration example

[georgeatparallel]

Adds a runnable configuration example for free, keyless Parallel Search MCP through BotSharp's existing HTTP MCP integration. The guide covers server setup, selecting web_search and web_fetch for an agent, and disabling the integration. WebStarter configuration and existing provider selections stay unchanged.

The example validation loads the JSON with AddBotSharpMCP, discovers tools with IMcpService, loads selected agent functions, and executes search and fetch through FunctionExecutorFactory and McpToolExecutor. It checks useful source content, BotSharp User-Agent headers, absence of authentication headers, and disabled controls. The default test uses a local HTTP fixture; an explicit switch runs it against the public service.

Validation: full solution Release build; 459 core tests, 4 UnitTest tests, and 3 SemanticKernel tests passed. The live keyless example passed search and fetch against the public service. The documentation HTML build passed.

I work at Parallel.

[qodo-code-review]

Code Review by Qodo

Sorry, something went wrong

We weren't able to complete the code review on our side. Please try again manually by commenting /agentic_review on this PR.

[qodo-code-review]

PR Summary by Qodo

Add an opt-in Parallel Search MCP configuration example

📝 Documentation 🧪 Tests ✨ Enhancement 🕐 20-40 Minutes

AI Description

• Document keyless Parallel Search setup through BotSharp’s existing HTTP MCP integration.
• Provide an opt-in configuration without changing WebStarter defaults or provider selections.
• Validate tool discovery, search, fetch, request headers, and disable controls with a local
 fixture.

Diagram

graph TD
  Config["Example JSON"] --> Registration["MCP registration"] --> Discovery["Tool discovery"] --> Agent["Agent tools"] --> Factory["Executor factory"] --> Executor["MCP executor"] --> Service["Parallel Search"]
  Discovery --> Service

Loading

High-Level Assessment

The opt-in example is the appropriate approach: BotSharp already supports HTTP MCP discovery and execution, so a dedicated plugin or a change to WebStarter defaults would add complexity or enable an external service unexpectedly.

Files changed (5) +277 / -0

Tests (2) +190 / -0

BotSharp.Core.UnitTests.csprojCopy the example JSON into the test output +4/-0

Copy the example JSON into the test output

• Makes the documented configuration available to the test at runtime so validation uses the example itself.

tests/BotSharp.Core.UnitTests/BotSharp.Core.UnitTests.csproj

ParallelSearchExampleTests.csExercise the documented MCP discovery and execution path +186/-0

Exercise the documented MCP discovery and execution path

• Tests configuration loading, tool discovery, agent function loading, search and fetch execution, request headers, and disable controls. Uses a local HTTP fixture by default and contacts the public service only when explicitly enabled.

tests/BotSharp.Core.UnitTests/MCP/ParallelSearchExampleTests.cs

Documentation (2) +63 / -0

index.rstLink the Parallel Search guide from the documentation index +6/-0

Link the Parallel Search guide from the documentation index

• Adds an MCP table-of-contents section pointing to the new guide.

docs/index.rst

parallel-search.mdExplain setup, agent tool selection, and validation +57/-0

Explain setup, agent tool selection, and validation

• Documents how to add the server, select web_search and web_fetch, disable the integration, and run local or explicitly opted-in live validation.

docs/mcp/parallel-search.md

Other (1) +24 / -0

parallel-search.jsonProvide an opt-in HTTP MCP server configuration +24/-0

Provide an opt-in HTTP MCP server configuration

• Defines an enabled Parallel Search server using the public MCP endpoint and a BotSharp User-Agent, without authentication headers.

docs/mcp/parallel-search.json