What is the key difference between BrowserAI Dev and Research Hub?

BrowserAI Dev belongs to the Research category with local stdio execution, while Research Hub belongs to the Research category with local stdio execution.

How do I install BrowserAI Dev or Research Hub in Claude Desktop or Cursor?

Copy the mcpServers JSON configuration snippet provided on this page into your claude_desktop_config.json or ~/.cursor/mcp.json file and restart your AI client.

Are BrowserAI Dev and Research Hub free or paid?

BrowserAI Dev operates under a Freemium model (API Key required). Research Hub operates under a Free / Open Source model (API Key required).

Which MCP server has more tools and community activity?

BrowserAI Dev lists 13 tools with 3 views and 20 GitHub stars. Research Hub lists 6 tools with 2 views and 54 GitHub stars.

Can I use both BrowserAI Dev and Research Hub together in the same MCP host?

Yes! MCP hosts like Claude Desktop, Cursor, Windsurf, Cline, and VS Code support configuring multiple servers under the mcpServers object simultaneously.

Side-by-Side Model Context Protocol Comparison

BrowserAI Dev vs Research Hub

In-depth architectural comparison of the BrowserAI Dev and Research Hub MCP servers. Compare execution transports, security boundaries, tool capabilities, quality scores, and ready-to-paste client installation snippets for Claude, Cursor, Windsurf, and VS Code.

At a Glance & Executive Verdict

BrowserAI Dev

Research · Local stdio

Quality: 64/100 (Good) | Auth: API Key required

Research Hub

Research · Local stdio

Quality: 56/100 (Good) | Auth: API Key required

Verdict Summary: Choose BrowserAI Dev if you need specialized Research tools running via a local process. Choose Research Hub if your workspace requires Research integration with local subprocess execution. Both servers can be configured concurrently in your client's mcpServers manifest.

Which MCP Server Should You Choose?

Choose BrowserAI Dev when:

You need dedicated capabilities in the Research domain.
You prefer local stdio subprocess transport architecture.
Your security boundary fits: API Key required (Freemium).
You have access to required keys: LASTSEARCH_API_KEY.
Primary tools included: search, open, extract.

Explore BrowserAI Dev Details

Choose Research Hub when:

You need dedicated capabilities in the Research domain.
You prefer local stdio subprocess transport architecture.
Your security boundary fits: API Key required (Free / Open Source).
You have access to required keys: ZOTERO_API_KEY, ZOTERO_USER_ID, NOTEBOOKLM_API_KEY, GOOGLE_API_KEY, GOOGLE_OAUTH_CLIENT_ID, GOOGLE_OAUTH_CLIENT_SECRET.
Primary tools included: Unified search across arXiv, Semantic Scholar, PubMed, and CrossRef, Integration with Zotero for reference management, Obsidian note syncing and dashboard visualization.

Feature & Specification Comparison

Specification	BrowserAI Dev BrowseAI-HQ Research	Research Hub WenyuChiou Research
Summary	Evidence-backed web research for AI agents. Real-time search with cited claims, confidence scores, and compare mode (raw LLM vs evidence-backed). MCP server, REST API, and Python SDK.	Research workspace MCP integrating Zotero, Obsidian, and NotebookLM. Search papers (arXiv/Semantic Scholar/PubMed/CrossRef), ingest into Zotero, sync notes to Obsidian, verify NotebookLM briefs. All three external tools optional. pip install research-hub-pipeline then research-hub serve.
Category & Scope

Tools & Capabilities Breakdown

BrowserAI Dev Tools (13)

Search the web for information on any topic

open

Fetch and parse a web page into clean text

extract

Extract structured claims from a page

answer

Full pipeline: search + extract + cite. `depth`: `"fast"`, `"thorough"`, or `"deep"

compare

Compare raw LLM vs evidence-backed answer

clarity

Anti-hallucination answer engine — three modes: prompt (prompts only), answer (LLM), verified (LLM + web fusion)

Ready-to-Paste Client Configurations

Paste either (or both) of these JSON server blocks into your client config file (e.g. claude_desktop_config.json or ~/.cursor/mcp.json).

BrowserAI Dev Configuration

mcpServers (Claude Desktop / Cursor)

{
  "mcpServers": {
    "browseai-hq-browserai-dev": {
      "command": "npx",
      "args": [
        "-y",
        "lastsearch"
      ],
      "env": {
        "LASTSEARCH_API_KEY": "YOUR_LASTSEARCH_API_KEY_HERE"
      }
    }
  }
}

Research Hub Configuration

mcpServers (Claude Desktop / Cursor)

{
  "mcpServers": {
    "wenyuchiou-research-hub": {
      "command": "uvx",
      "args": [
        "research-hub-pipeline"
      ],
      "env": {
        "ZOTERO_API_KEY": "YOUR_ZOTERO_API_KEY_HERE",
        "ZOTERO_USER_ID": "YOUR_ZOTERO_USER_ID_HERE",
        "NOTEBOOKLM_API_KEY": "YOUR_NOTEBOOKLM_API_KEY_HERE",
        "GOOGLE_API_KEY": "YOUR_GOOGLE_API_KEY_HERE",
        "GOOGLE_OAUTH_CLIENT_ID": "YOUR_GOOGLE_OAUTH_CLIENT_ID_HERE",
        "GOOGLE_OAUTH_CLIENT_SECRET": "YOUR_GOOGLE_OAUTH_CLIENT_SECRET_HERE"
      }
    }
  }
}

Frequently Asked Questions

BrowserAI Dev is categorized under Research and uses a local stdio subprocess. In contrast, Research Hub belongs to Research using local stdio subprocess. Select BrowserAI Dev when you need capabilities focused on research and Research Hub when you require tools for research.

More alternatives to BrowserAI Dev More alternatives to Research Hub Research category hub