About AI Tool Directory
AI Tool Directory is an MCP server that lets clients query a human-maintained catalog of AI tools. It provides profiles, comparisons, alternatives, and lifecycle checks, including whether a product is defunct or acquired.
Key features
- 01Hybrid semantic catalog search
- 02Tool profiles with pricing and features
- 03Active, defunct, or acquired status
- 04Curated alternatives
- 05Side-by-side tool comparisons
- 06Category and role listings
Use cases
- 01Checking whether a recommended tool is still active
- 02Finding alternatives to a discontinued product
- 03Comparing tools for a particular task
- 04Browsing tools by category or role
MCP support
Provides read-only search, lookup, status, alternatives, comparison, and listing tools to MCP clients. The hosted Streamable HTTP endpoint is available, and the stdio package proxies calls to it.
Configuration
Remote servers need no local install. Pick your client, then copy the config or install in one click.
https://tooldirectory.ai/api/mcpclaude mcp add --transport http ai-tooldirectory-catalog https://tooldirectory.ai/api/mcp{"mcpServers":{"ai-tooldirectory-catalog":{"type":"http","url":"https://tooldirectory.ai/api/mcp"}}}Open in Cursor{"servers":{"ai-tooldirectory-catalog":{"type":"http","url":"https://tooldirectory.ai/api/mcp"}}}Open in VS Code{"mcpServers":{"ai-tooldirectory-catalog":{"type":"http","url":"https://tooldirectory.ai/api/mcp"}}}{"mcpServers":{"ai-tooldirectory-catalog":{"serverUrl":"https://tooldirectory.ai/api/mcp"}}}Run commands in a terminal; paste JSON into the client’s MCP config and restart. Servers that need sign-in will prompt on first connect.
Tools
6| Parameter | Type | Required | Description |
|---|---|---|---|
| limit | integer | No | Max results (1-20, default 8). |
| query | string | Yes | What the user is looking for, e.g. "AI video editing" or "alternatives to Jasper". |
Details
From the project READMETool Directory MCP Server
MCP server for the AI Tool Directory — a live, human-edited catalog of 2,000+ AI tools. Lets any MCP client (Claude Desktop, Claude Code, Cursor, Windsurf, agent frameworks) query the catalog mid-task instead of guessing from a frozen training cut.
The headline tool is check_tool_status: whether an AI tool is still alive. It's the one fact LLMs reliably get wrong — models keep recommending products that shut down months ago. This server answers it from the directory's AI Graveyard, a maintained dataset of 150+ defunct and acquired AI tools, and suggests live alternatives when a tool is dead.
Tools
| Tool | What it does |
|---|---|
search_tools | Hybrid semantic search across the catalog — by keyword, use case, or category. |
get_tool | Full profile of one tool: pricing, features, editorial verdict, last human-verified date. |
check_tool_status | Is this tool active, deceased, or acquired? Date + cause if it shut down, plus live alternatives. |
find_alternatives | Curated alternatives to a tool; live replacements if it's defunct. |
compare_tools | Side-by-side comparison of two tools, with the editor's head-to-head verdict when one exists. |
list_tools | Top-rated active tools for a category or job role, optionally filtered by pricing. |
Read-only, no API key, no signup.
Install
Hosted endpoint (no install)
The server is also available as a remote MCP (Streamable HTTP) — point your client at:
https://tooldirectory.ai/api/mcp
Claude Desktop / Claude Code
{
"mcpServers": {
"tooldirectory": {
"command": "npx",
"args": ["-y", "tooldirectory-mcp"]
}
}
}
Or with Claude Code:
claude mcp add tooldirectory -- npx -y tooldirectory-mcp
Cursor / Windsurf / other MCP clients
Use the same stdio command: npx -y tooldirectory-mcp.
Docker
docker build -t tooldirectory-mcp .
docker run -i tooldirectory-mcp
Example prompts
- "Is Jasper still operating? What happened to Inflection Pi?"
- "Find me alternatives to Midjourney with a free tier."
- "Compare Gamma and Beautiful.ai for making decks."
- "What are the best AI tools for sales teams?"
How it works
This package is a thin stdio front-end over the canonical hosted endpoint at tooldirectory.ai/api/mcp, where the search (Meilisearch hybrid semantic) and catalog logic live. Tool schemas are declared locally, so initialize and tools/list respond instantly with no network call; tools/call proxies to the hosted endpoint. Zero runtime dependencies.
Set TOOLDIRECTORY_MCP_ENDPOINT to override the upstream endpoint (e.g. for testing).
About the data
The catalog is maintained by Tool Directory — an AI tool company run by humans that use AI. Every listed tool has a lifecycle status; editorial reviews carry a named editor and a last-verified date. Related machine-readable surfaces:
- Research hub — AI tool mortality statistics
- Catalog feed / Graveyard feed
- /mcp — server documentation page
License
MIT
Comments
New to MCP?
From what the protocol is to installing your first server, these answers cover most first questions.
An open protocol that defines how AI applications connect to external tools and data in a uniform way. Clients talk to the model; MCP servers provide tools, resources and prompt templates. They exchange standard messages, so one server can be reused by many clients.