obsidian-llm-wiki
★ 36
vs
chrome-devtools-mcp
★ 54.0k
obsidian-llm-wiki vs chrome-devtools-mcp
obsidian-llm-wiki: LLMwiki compiles raw research materials into a structured Obsidian wiki with summaries, concepts, and backlinks. It supports headless operation, MCP integration for AI agents, and a review pipeline to promote knowledge from drafts to team truth.; chrome-devtools-mcp: chrome-devtools-mcp enables AI coding assistants like Gemini, Claude, and Copilot to interact with a live Chrome browser via the Model-Context-Protocol (MCP). It grants AI full access to Chrome DevTools for reliable automation, deep debugging, and detailed performance insights.
01
TL;DR
obsidian-llm-wikiBrowser Automation · ★ 36
Team knowledge management
chrome-devtools-mcpBrowser Automation · ★ 54.0k
When to choose:
- You want an agent to record a Chrome performance trace and get insights from it; the README lists performance_start_trace, performance_stop_trace and performance_analyze_insight.
- You need to inspect network requests, console messages and screenshots of a page while debugging it.
- You want the agent to attach to a Chrome you already have running, using --browser-url, --ws-endpoint or --autoConnect (Chrome 144+).
When to skip:
- You need Firefox or Safari: the project is built on Chrome DevTools and targets Chrome.
- You want a general-purpose automation or test runner across browsers; Playwright MCP is the closer fit.
- You cannot run Node.js 20.19 or newer, which the README lists as a requirement.
02
Side-by-Side Comparison
Field
Category
Browser Automation
Browser Automation
Stars
★ 36
★ 54.0k
License
GPL-3.0
Apache-2.0
Install Command
git clone --depth 1 https://github.com/2233admin/obsidian-llm-wiki.git && cd obsidian-llm-wiki && ./setup
npx -y chrome-devtools-mcp@latest
Updated
1d ago
1d ago
Open Source
Yes
Yes
Tags
ai-agent, claude-code, codex
Chrome DevTools, AI Assistant, Browser Automation
03
Features
01Headless-first design
02MCP integration for AI agents
03Compile raw materials into wiki
04Knowledge work roles (librarian, architect, curator, etc.)
05Supports multiple MCP-compatible hosts (Claude Code, Codex CLI, etc.)
01Get performance insights using Chrome DevTools
02Advanced browser debugging (network, screenshots, console)
03Reliable automation using Puppeteer
04Input automation (click, drag, fill, etc.)
05Navigation automation (new page, navigate, wait for, etc.)
04
Use Cases
↳Team knowledge management
↳Research material compilation
↳AI-assisted query and answer from vault
↳Automating browser interactions for testing or data extraction
↳Debugging web applications by analyzing network requests and console messages
↳Analyzing website performance by recording traces and extracting insights
05
Best For
—
Most PopularEssentialTrending
FAQ
FAQ
What is the difference between obsidian-llm-wiki and chrome-devtools-mcp?
Both obsidian-llm-wiki and chrome-devtools-mcp are in the Browser Automation category. obsidian-llm-wiki has 36 stars, while chrome-devtools-mcp has 54.0k stars.
Which is better, obsidian-llm-wiki or chrome-devtools-mcp?
The best choice depends on your use case. Choose obsidian-llm-wiki if Team knowledge management, and chrome-devtools-mcp if Automating browser interactions for testing or data extraction.
Is obsidian-llm-wiki free or open source?
Yes, obsidian-llm-wiki is open source on GitHub (GPL-3.0).
Is chrome-devtools-mcp free or open source?
Yes, chrome-devtools-mcp is open source on GitHub (Apache-2.0).
Cloud Infrastructure
AdDeploy on DigitalOcean
Host your MCP servers, Docker containers, and AI agents with $200 free credit over 60 days.
→