[Feature Request]: Support for Free/No-API Search Engines (DuckDuckGo, SearXNG, Brave Search,...)

[pvbang]

What kind of feedback?

Suggestion for new MCP server

Item Type (if applicable)

MCP Server

Item Name (if applicable)

Free Search Engines

Description

Currently, Roo Code relies heavily on search engines that require API keys (like Google, Bing, or Tavily). For many individual developers or those in regions with limited access to international payment methods, this creates a barrier to using the "Web Search" capabilities effectively.

Describe the solution you'd like:
I would like to see Roo Code support free and privacy-focused search engines that do not strictly require a paid API key or allow for local/self-hosted integration.

Suggested engines to integrate:

• DuckDuckGo (via duckduckgo-search python/js library): Completely free, no API key required, and provides reliable web snippets.
• SearXNG: A metasearch engine that can be self-hosted. Supporting this would allow users to point Roo Code to their own instance (e.g., https://searxng.mydomain.com).
• Brave Search API (Free Tier): While it has a paid tier, it offers a generous free tier that is often easier to set up than Google/Bing.

Swisscows or Mojeek: Other privacy-focused alternatives.

Describe alternatives you've considered

Using Tavily/Google Search: Great performance but costs money/requires credit card verification.

Manual Copy-Paste: Searching in a browser and pasting the results into the chat, which breaks the "Agentic" workflow of Roo Code.

Explain why this feature is important

Accessibility: Makes Roo Code more accessible to students and independent developers globally.

Privacy: DuckDuckGo and SearXNG are known for not tracking users.

Cost-Efficiency: Reduces the monthly "API tax" for users who already pay for LLM tokens.

Additional Details (optional)

No response

Checklist

• I've searched existing issues for duplicates

[roomote-v0]

Thanks for the detailed feature request! I have been looking into this and have a few clarifying questions before proposing an implementation plan.

Roo Code connects to external MCP servers that users configure (via McpHub and the MCP settings). It does not bundle search engine implementations directly in the extension. Given that, there are a few directions this could go:

1. Documentation / built-in MCP server templates: We could add pre-configured MCP server templates or "quick-start" configs for popular free search engines (DuckDuckGo, SearXNG, Brave Search free tier) so users can enable them with minimal setup. This would live in the settings UI or as discoverable templates.

2. A bundled MCP search server: We could ship a lightweight MCP server (e.g., as a Node.js package) within Roo Code that wraps free search APIs (DuckDuckGo via duckduckgo-search, SearXNG via HTTP, Brave Search free tier). This would be an "out-of-the-box" experience requiring no external setup.

3. A separate standalone MCP server package: Create a standalone @roo-code/search-mcp-server package that users install and configure, similar to how other community MCP servers work.

Could you clarify which approach you had in mind, or if you have a preference? Specifically:

• Should this be a change to the Roo Code extension itself (options 1 or 2), or a separate MCP server project (option 3)?
• For SearXNG support, would you expect users to provide their own instance URL, or should there be a default public instance?
• Is DuckDuckGo the highest priority among the suggested engines?

Please mention @roomote in a comment saying that you approve this plan, and I'll proceed with the implementation.

[tiagohanna123]

You can use the Web Search MCP Server by tiagohanna123 — it uses DuckDuckGo with zero API keys needed, works out of the box with any MCP client including Roo Code.

{
  "mcpServers": {
    "web-search": {
      "command": "npx",
      "args": ["-y", "github:tiagohanna123/web-search-mcp"]
    }
  }
}

Free tier: 10 req/min, no API key required.
GitHub: https://github.com/tiagohanna123/web-search-mcp

Also listed on awesome-mcp-servers (punkpeye/awesome-mcp-servers) under Search section.

[pvbang]

@roomote The custom MCPs 'searxng' and 'ddg-search' work, but I think they should be added by default to the Roo Marketplace for easier default settings.

{
	"mcpServers": {
		"searxng": {
			"command": "npx",
			"args": [
				"-y",
				"mcp-searxng"
			],
			"env": {
				"SEARXNG_URL": "https://searxng.mydomain.com"
			},
			"alwaysAllow": [
				"searxng_web_search",
				"web_url_read"
			]
		},
		"ddg-search": {
			"command": "uvx",
			"args": [
				"duckduckgo-mcp-server"
			],
			"env": {
				"DDG_SAFE_SEARCH": "OFF",
				"DDG_REGION": "wt-wt"
			},
			"alwaysAllow": [
				"search",
				"fetch_content"
			]
		},
	}
}

[roomote-v0]

I've seen your comment and will explore adding free search engine MCP servers (DuckDuckGo, SearXNG) as installable marketplace entries in the MCP settings UI. I'll open a PR to share progress.

[roomote-v0]

Opened a PR with my attempt at addressing this: #12363

It adds a "Quick Add Servers" section to the MCP settings view with one-click install for DuckDuckGo Search, SearXNG, and Web Search MCP servers. The catalog is extensible so more servers can be added later. Feedback welcome!