Devin Search MCP
Related Servers
Alternatives to Devin Search MCP
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityAmaintenanceEnables AI coding assistants to perform multi-engine web searches, site-specific searches, and structured webpage content extraction via MCP stdio, without requiring any API keys.1MIT
- AlicenseNot gradedqualityCmaintenanceProvides AI coding agents with a live web search tool that returns extracted, answer-ready text from web pages. Enables real-time information retrieval without any local installation or maintenance.6 npmMIT
- FlicenseNot gradedqualityCmaintenanceProvides 42+ MCP tools for browser automation, web scraping, and search, enabling AI agents like Claude and Cursor to browse, extract data, and run research agents on the live web.9-
- AlicenseNot gradedqualityDmaintenanceProvides AI agents and coding assistants with advanced web crawling and RAG capabilities, allowing them to scrape websites and leverage that knowledge through various retrieval strategies.2MIT
- FlicenseNot gradedqualityCmaintenanceEnables AI agents to perform unified web research through a single MCP server, including search, page fetching, recursive crawling, document parsing, YouTube transcript extraction, and deep multi-query research.3-
- AlicenseAqualityDmaintenanceCLI-first web and code search for agents, with MCP support for integration with IDEs like Cursor, VS Code, and Claude Code.3MIT
TDQS
Scored across 3 tools
Each tool targets a distinct action: web search, web content fetching, and credential extraction. Boundaries are clear, and the credential tool does not overlap with the web retrieval tools.
Two tools use a devin_web_ prefix and noun-based structure, while extract_devin_key uses a different verb-first pattern without the web prefix. All names are snake_case and readable, but the convention is not uniform.
Three tools is a compact set appropriate for a focused search server, though the credential extraction tool is peripheral to the core search/fetch purpose. No bloat, and each tool has a clear role.
Search and fetch cover the primary web retrieval lifecycle, and key extraction supports authenticated access. Minor gaps like batch fetch, date filters, or search operators exist, but the core operations are present.