agentalmanac-mcp
# agentalmanac-mcp
An MCP server for searching the [Agent Almanac](https://agentalmanac.org) — the public catalog of 9,000+ Model Context Protocol servers.
> The MCP server for finding MCP servers. Discover, inspect, and install MCP tools from inside any MCP-aware agent.
## Install
```json
{
"mcpServers": {
"agentalmanac": {
"command": "npx",
"args": ["-y", "agentalmanac-mcp"]
}
}
}
```
Add this to your Claude Desktop / Cursor / Continue / Zed MCP config. No auth, no setup.
## Tools
| Tool | What it does |
|---|---|
| `search_mcp_servers(query, transport?, limit?)` | Search the catalog by capability, name, or description (FTS5-backed) |
| `get_server_details(slug)` | Full per-server info: install command, tool list, repo, version |
| `list_recent_servers(limit?, transport?)` | Most recently updated MCP servers in the catalog |
## Example usage
After installing, ask your agent:
> Find me an MCP server for working with Postgres.
> Get details on `io-github-proompteng-bilig-workpaper`.
> What's been updated in the MCP ecosystem this week?
The server returns formatted text. Your agent does the rest.
## What's the Agent Almanac
[agentalmanac.org](https://agentalmanac.org) is a neutral, open catalog of MCP servers. It ingests from the official Model Context Protocol Registry and surfaces searchable, installable entries. No login. Free. JSON API: `https://agentalmanac.org/api/v1/mcp/servers`.
## Configuration
| Env var | Default | Use |
|---|---|---|
| `AGENTALMANAC_API_BASE` | `https://agentalmanac.org/api/v1` | Override for testing against a different base URL |
## License
MIT. Issues + PRs: https://github.com/survivorforge/agentalmanac-mcp
TDQS
Scored across 3 tools
Each tool has a distinct purpose: get_server_details retrieves details for a specific server, list_recent_servers lists recently updated servers, and search_mcp_servers searches the catalog. No functional overlap.
All tool names follow a consistent verb_noun pattern using snake_case (e.g., get_server_details, list_recent_servers, search_mcp_servers), making them predictable and easy to understand.
With only 3 tools, the server is well-scoped for its purpose of discovering and getting details about MCP servers. Each tool is essential, and the count is not excessive or insufficient.
The tool set covers the core workflows: searching, browsing recent additions, and retrieving full details. Minor gaps exist (e.g., no pagination or filtering beyond search), but the surface is adequate for typical use.