Search for:
Why this server?
Enables AI agents to control web browsers via a standardized interface for operations like launching, interacting with, and closing browsers.
Why this server?
A browser automation server providing Playwright capabilities for controlling web browsers, capturing screenshots, extracting content, and performing complex interactions through an MCP interface.
Why this server?
A server based on the MCP protocol that uses the Brave API for web search functionality.
Why this server?
A Model Context Protocol server that enables LLMs to interact with web pages through structured accessibility snapshots, providing browser automation capabilities without requiring screenshots or visually-tuned models.
Why this server?
Provides functionality to fetch and transform web content in various formats (HTML, JSON, plain text, and Markdown) through simple API calls.
Why this server?
An MCP server paired with a Firefox extension that enables LLM clients to control the user's browser, supporting tab management, history search, and content reading.
Why this server?
A bridge between AI assistants and ArXiv's research repository that enables searching, downloading, and reading academic papers through the Message Control Protocol.
Why this server?
Provides a standardized protocol for tool invocation, enabling an AI system to search the web, retrieve information, and provide relevant answers through integration with LangChain, RAG, and Ollama.
Why this server?
A bridge between AI assistants and search services that implements A2A protocol and Model Context Protocol, enabling search functionality for web, videos, maps, flights, and hotels.
Why this server?
An MCP (Model Context Protocol) server for performing accessibility audits on webpages using axe-core. Use the results in an agentic loop with your favorite AI assistants (Cline/Cursor/GH Copilot) and let them fix a11y issues for you!