Frequently Asked Questions (FAQ) about Brave Search MCP Server

Q: What is an MCP Server? A: MCP stands for Model Context Protocol. An MCP server acts as a bridge between AI models and external data sources or tools, providing a standardized way for AI models to access and interact with them.

Q: What is the Brave Search MCP Server? A: The Brave Search MCP Server is a pre-built server that allows AI agents to access Brave Search capabilities using the MCP protocol. It provides real-time search results via Server-Sent Events (SSE).

Q: What is SSE (Server-Sent Events)? A: SSE is a web technology that enables a server to push updates to a client in real-time over a single HTTP connection. This is used to deliver search results as they become available, without the need for constant polling.

Q: What is UBOS? A: UBOS is a full-stack AI Agent development platform focused on enabling businesses to orchestrate AI Agents, connect them with enterprise data, build custom AI Agents with LLMs, and create Multi-Agent Systems.

Q: Why use Brave Search instead of other search engines? A: Brave Search is known for its privacy-focused approach and independent search index, offering a viable alternative to mainstream search engines.

Q: What are the prerequisites for using the Brave Search MCP Server? A: You need a Brave Search API key, Node.js 18+, Docker (for containerized deployment), and a Coolify instance (for Coolify deployment).

Q: How do I get a Brave Search API key? A: You can obtain an API key by signing up for a Brave Search developer account on the Brave Search website.

Q: How do I deploy the Brave Search MCP Server? A: You can deploy it using Docker or Coolify. Instructions for both methods are provided in the server’s documentation.

Q: What is the SSE endpoint? A: The SSE endpoint is http://your-server:3001/sse. You can connect to it using the EventSource API in JavaScript to receive real-time search results.

Q: How do I send a search query to the server? A: Use the POST http://your-server:3001/messages endpoint with a JSON payload containing the query parameter. You can also specify the count parameter to control the number of results (default is 10, max is 20).

Q: What is the format of the search results? A: Search results are sent as JSON objects via SSE. You can parse the event.data property to access the results.

Q: How does the server handle errors? A: The server broadcasts errors to all connected SSE clients in a JSON format: {"type": "error", "error": "error message"}.

Q: Can I use this server in a production environment? A: Yes, but consider implementing authentication for the messages endpoint to prevent unauthorized access.

Q: How does the Brave Search MCP server integrate with the UBOS Platform? A: UBOS allows you to connect the Brave Search MCP Server to other UBOS components, such as LLMs, data connectors, and automation modules. This gives you access to internal knowledge. You can incorporate MCP server into custom AI Agents.

Q: Where can I find the Brave Search MCP server on UBOS? A: The Brave Search MCP Server is available on the UBOS Asset Marketplace.