AIVerified

Brave Search MCP integration

Use Brave Search through Connexsus when MCP workflows need web discovery alongside internal and provider-specific context.

Brave is the web-discovery layer in the first public Connexsus provider wave. It helps teams combine live web search with project providers like GitHub, Notion, or Context7 from one MCP entry point.

Install path

This provider uses a credential form flow. Connexsus stores the submitted credential in the encrypted vault model and exposes the provider after project assignment.

What you can do with Brave Search

  • Search public web context while coding.
  • Validate claims with external sources in operational workflows.
  • Pair web discovery with docs or provider-specific context.

Sample prompts

Use Brave Search to search public web context while coding.
Within Connexsus, use Brave Search to validate claims with external sources in operational workflows.
Explain how Brave Search helps teams pair web discovery with docs or provider-specific context.

Available capabilities

1 tools

brave_web_search

Search the public web using Brave Search and return concise results.

FAQ

Why include search as a provider page?

Because discovery and verification are frequent MCP intents, and users often look for searchable external context as part of agent workflows.

Does Brave replace internal docs providers?

No. It complements them by covering public web discovery while other providers cover workspace or product data.

Can Brave be combined with Context7?

Yes. Brave is useful for broad search, while Context7 is useful for targeted documentation retrieval.

Auth and workspace model

Connexsus separates public provider information from private runtime state. Teams install the provider after sign-in, assign it to a project, and then expose tools to supported MCP clients from one managed gateway endpoint.

Related providers