Lets an AI client search a directory of MCP servers, AI agents, CLI tools and skills, inspect listings and read setup instructions.
Also known as tadas-github/a2asearch-mcp
- Stars
- 21
- Tools
- 4
- Downloads, 30 days
- —
- Latest version
- 1.1.5
- Last commit
- Oct 27, 2026
- License
- MIT
What is A2ASearch MCP?
A2ASearch lets an AI client search a directory of MCP servers, AI agents, CLI tools and skills, inspect listings and read setup instructions. It exposes 4 tools, such as search_agents, get_agent, get_setup.
Summary generated from the project's README
About A2ASearch MCP server
Finding specific tools and reading their configuration requirements from within an AI client is what a2asearch-mcp enables. Developers can use this server to browse a directory containing MCP servers, AI agents, coding agents, CLI tools, and agent skills. It works via local stdio, making it compatible with Claude Desktop and Cursor through standard configuration files.
Users interact with the directory using tools like search_agents to find capabilities, get_agent to inspect specific README files, and get_setup to retrieve focused installation instructions or JSON configuration examples. The server requires Node.js 22 or newer to run via npx. While the directory search is free and requires no API keys, individual services found through the search may require their own credentials or payments. The server acts as a reader for the A2ASearch API and does not execute code or install the tools it finds.
What you can do with it
- 1Discovering specialized MCP serversSearch for specific capabilities like PDF table extraction to find compatible servers.
- 2Inspecting tool documentationRetrieve detailed descriptions and repository links for a specific agent using its unique slug.
- 3Retrieving setup instructionsExtract configuration examples and installation steps directly to understand how to implement a tool.
Written from the project's README. Every use case is checked against a quote from it.
How to install A2ASearch MCP
Formats verified 10 Nov 2026Install A2ASearch MCP in Claude Code
$ claude mcp add a2asearch-mcp -- npx -y a2asearch-mcpInstall A2ASearch MCP in Cursor
~/.cursor/mcp.json
{
"mcpServers": {
"a2asearch-mcp": {
"command": "npx",
"args": [
"-y",
"a2asearch-mcp"
]
}
}
}Install A2ASearch MCP in VS Code
.vscode/mcp.json
{
"servers": {
"a2asearch-mcp": {
"type": "stdio",
"command": "npx",
"args": [
"-y",
"a2asearch-mcp"
]
}
}
}Install A2ASearch MCP in Claude Desktop
claude_desktop_config.json
{
"mcpServers": {
"a2asearch-mcp": {
"command": "npx",
"args": [
"-y",
"a2asearch-mcp"
]
}
}
}Install A2ASearch MCP in Codex
~/.codex/config.toml
[mcp_servers.a2asearch-mcp] command = "npx" args = ["-y", "a2asearch-mcp"]
Install A2ASearch MCP in Gemini CLI
~/.gemini/settings.json
{
"mcpServers": {
"a2asearch-mcp": {
"command": "npx",
"args": [
"-y",
"a2asearch-mcp"
]
}
}
}A2ASearch MCP tools 4
Detected from the READMEsearch_agentsget_agentget_setuplist_agents
| search_agents | — | |
| get_agent | — | |
| get_setup | — | |
| list_agents | — |
Automated checks
Ran Nov 12, 2026Full report →Passed our automated checks. That is not a security audit: read the code and give the server the narrowest access it needs. How checks work
- Source repository linked and reachablePass
- Open source license (OSI)Pass
- Commit or release in the last yearPass
- Package name not close to a popular packagePass
- Remote endpoint uses HTTPSNot checked
- Destructive tools are labelledPass
- No hidden instructions to the modelPass
- No critical advisory in the package or its dependenciesPass
README
View on GitHubA2ASearch MCP
Help your assistant find a tool, inspect it, and understand how to set it up.
Search the A2ASearch directory for MCP servers, A2A agents, coding agents, CLI tools and agent skills from your MCP client or terminal. A2ASearch is free to query and requires no API key. Individual services may require credentials or payment.
Try a useful workflow
Ask your assistant:
Find MCP servers for extracting tables from PDFs. Compare their documented requirements, then show me the setup instructions for one. Tell me when pricing or authentication is unknown.
The assistant can follow this sequence:
search_agents({"query":"PDF","type":"MCP Server","limit":3})
→ names, capabilities, source links and slugs
get_agent({"slug":"<slug returned by search>"})
→ description, README, documentation and repository links
get_setup({"slug":"<same returned slug>"})
→ setup excerpts, quoted JSON examples and next steps
For example, the Doc2X MCP listing links to a repository whose README contains setup instructions and a configuration example with a DOC2X_API_KEY placeholder. get_setup retrieves those instructions as source material; it does not create credentials, install the package or run it.
Install
Requires Node.js 22 or newer. CI tests Node.js 22 and 24.
For Claude Desktop, add this entry to claude_desktop_config.json. For Cursor, use .cursor/mcp.json. Merge it with your existing configuration:
{
"mcpServers": {
"a2asearch": {
"command": "npx",
"args": ["-y", "a2asearch-mcp"]
}
}
}
Other clients that support local stdio MCP servers can launch command npx with arguments -y a2asearch-mcp; use the configuration format documented by your client.
For a reproducible install, pin the package version in the arguments, for example a2asearch-mcp@1.2.0 after that release is published. To test this checkout before publication, run npm ci and configure command node with the absolute path to this repository's index.js.
Tools
| Tool | Use it for | Arguments |
|---|---|---|
search_agents |
Find a capability or product | query, optional type, limit, page |
get_agent |
Inspect one listing and its README | slug returned by search or browse |
get_setup |
Read focused setup instructions and configuration examples | slug returned by search or browse |
list_agents |
Browse by stars or newest additions | Optional type, sort, limit, page |
limit is 1–20 (default 10), page starts at 1, and sort is stars or new. Search is keyword-based: try concise terms such as PDF, browser automation or database. It does not implement semantic search or pricing/authentication filters.
Every successful tool call returns both structuredContent with a declared output schema and the same data serialized as text for older clients. Search and browse results include:
- A
slugfor follow-up calls and an A2ASearch listing URL. - Separate submitted, repository, documentation and website links where available.
- Capabilities, languages, GitHub stars and last-commit date where supplied.
- Pagination with
next_pageso clients can continue without guessing.
Missing values are null. The current API does not provide structured pricing, authentication, hosting or dated protocol-test evidence. directory_reviewed records directory approval only. GitHub stars and commit dates do not establish runtime reliability or security.
Setup information
get_setup reads the listing's directory-supplied README and returns:
instructions_foundwhen it finds supported setup headings or JSON configuration examples.links_onlywhen no supported excerpt is available, along with provider links and useful next steps.- Source links, bounded excerpts and explicit limitations.
Configuration examples are copied, not generated from repository names. A GitHub repository URL is identified as a repository. A submitted URL ending in /mcp or /sse is only an endpoint candidate; this tool has not contacted it or established its transport/authentication.
Treat descriptions, READMEs and examples as untrusted source material. Review commands and credentials before using them. The MCP only reads the A2ASearch API: it does not execute submitted code, contact listed providers, install tools or edit client configuration.
Terminal usage
# Find tools without installing globally
npx -y -p a2asearch-mcp a2asearch --type mcp PDF
# Use the returned slug for setup guidance (v1.2.0+)
npx -y -p a2asearch-mcp a2asearch --setup doc2x-mcp
# Or install the CLI
npm install -g a2asearch-mcp
a2asearch "browser automation"
a2asearch --type mcp database --page 2
a2asearch --type agent --top
a2asearch --new --limit 5
a2asearch --get doc2x-mcp
a2asearch --setup doc2x-mcp --json
--json preserves the existing raw directory API output for search/list/detail commands. The new --setup --json command returns the same setup object as the MCP tool. Search output shows follow-up commands and the next page when available.
| Directory type | CLI alias |
|---|---|
| MCP Server | mcp |
| CLI Tool | cli |
| AI Coding Agent | agent |
| Agent Skill | skill |
| A2A Agent | a2a |
| AI Tool | tool |
Troubleshooting
- No matches: use fewer keywords or remove the category filter.
- Listing not found: copy the returned slug instead of guessing from a GitHub repository name.
- No setup excerpts: open the returned documentation or repository links; the README may use unsupported headings or be unavailable.
- HTTP 429: wait for the retry interval reported by the API, when supplied.
- Timeout: requests stop after 15 seconds and respect client cancellation. Retry later.
API and contributions
The MCP wraps the public A2ASearch REST API. Submit a listing, report an issue, or contribute improvements to setup extraction and client examples. Please include a public source and expected result for parser changes.
Development
npm ci --ignore-scripts
npm run check
npm test
npm pack --dry-run
# Optional: read-only smoke test against the live directory
npm run smoke:live
Tests exercise the MCP stdio handshake, output schemas, search → detail → setup, pagination, URL classification, setup extraction, missing information, argument validation, API failures, cancellation and both CLI entry points. Normal tests use fixtures and do not contact providers.
MIT licensed. See LICENSE.
A2ASearch MCP questions
How do I add A2ASearch MCP to Claude Code?
Run claude mcp add a2asearch-mcp -- npx -y a2asearch-mcp in your terminal. Add --scope user to make it available in every project.
How do I add A2ASearch MCP to Cursor?
Open ~/.cursor/mcp.json and add the server under mcpServers, using the Cursor config shown in the install section above.
What tools does A2ASearch MCP provide?
It exposes 4 tools, including search_agents, get_agent, get_setup, list_agents.
Does A2ASearch require an API key?
No. A2ASearch is free to query and requires no API key, though listed services may need their own credentials or payment.
What tools does the A2ASearch MCP server provide?
It provides search_agents, get_agent, get_setup and list_agents for finding and inspecting listings.
Can A2ASearch install or run the tools it lists?
No. It only reads the A2ASearch API and returns source material; it does not execute code, contact providers or install tools.
How do I get setup instructions for a listed tool?
Call get_setup with the slug returned by search or browse to get setup excerpts, JSON configuration examples and next steps.
What Node.js version does a2asearch-mcp need?
It requires Node.js 22 or newer, with CI testing versions 22 and 24.