# Agent Stack Directory MCP server

> Search and compare infrastructure tools for AI agents, such as cloud browsers, sandboxes, memory, search APIs, email and payments.

- Listing: https://mcp.tc/i/agent-stack-directory
- Connect: use the server's own URL `https://agentstackdirectory.com/mcp` (no sign-in); clients connect to it directly. The listing link is a page, not an MCP endpoint.
- Type: remote (Streamable HTTP)
- Auth: none
- Category: [Docs & Knowledge](https://mcp.tc/c/docs-knowledge)
- Vendor: Agent Stack Directory
- Homepage: <https://agentstackdirectory.com/>

## About

Gives an assistant access to Agent Stack Directory, a checked list of 79 tools that AI agents run on, grouped into 13 categories. You can browse categories, search by keyword with category and open-source filters, read a tool's listing with its alternatives, and compare two to four tools side by side.

Runs as a hosted streamable HTTP endpoint at agentstackdirectory.com/mcp. No sign-in or API key is needed. All tools are read-only.

## What it can do

- List the categories (layers) of the agent stack with tool counts
- Search tools by keyword, category and open-source flag
- Get a tool's summary, official site and alternatives
- Compare 2 to 4 tools side by side

## Tools (4)

- `search_tools`: Search agent infrastructure tools by keyword, with optional category and open-source filters. (read-only)
- `get_tool`: Get one tool's listing: summary, official site, open-source flag, last link check and alternatives. (read-only)
- `compare`: Compare 2 to 4 tools in a table with notable differences. (read-only)
- `list_categories`: List every category with its key, description and tool counts. (read-only)

## Example prompts

- "Which open-source code sandboxes are listed for AI agents?"
- "Compare Browserbase and Stagehand side by side."
- "List the categories in the agent stack directory."
- "Find email APIs built for AI agents."

## Install

### Claude Code

1. Run this in a terminal, in your project folder:

```bash
claude mcp add --transport http agent-stack-directory https://agentstackdirectory.com/mcp
```

2. Start Claude Code and type `/mcp`. **agent-stack-directory** should show as connected.

Add `--scope user` to make it available in every project, not just this one.

### Claude Desktop

1. Open **Customize → Connectors**, click **+ Add**, then **Add custom connector**.

2. Name it **Agent Stack Directory** and paste this URL:

```url
https://agentstackdirectory.com/mcp
```

3. Click **Add**. Its tools appear in the chat’s tools menu.

Claude Desktop’s JSON config file only starts local servers. Remote servers go through Connectors, and connectors you add on claude.ai show up here too.

### claude.ai

1. Open the connector form on claude.ai. This button fills in the name and URL for you:

[Add to claude.ai](<https://claude.ai/customize/connectors?modal=add-custom-connector&connectorName=Agent%20Stack%20Directory&connectorUrl=https%3A%2F%2Fagentstackdirectory.com%2Fmcp>) (opens connector settings)

2. Check that the URL reads `https://agentstackdirectory.com/mcp` and click **Add**.

3. Turn it on in a chat from the tools menu.

Free plans allow one custom connector. On Team and Enterprise plans an owner adds it under **Organization settings → Connectors**.

### ChatGPT

1. On chatgpt.com, go to **Plugins**, select **+**, then **Add custom MCP server**.

2. Enter a name for the server.

3. Under **Connection**, paste `https://agentstackdirectory.com/mcp` as the server URL, then for authentication choose **No authentication**.

4. Check **I understand and want to continue**, then select **Create as a plugin**.

Whether you can add a custom MCP server depends on your ChatGPT plan and your workspace permissions (in Business workspaces, admins and owners can).

### Cursor

[Add to Cursor](<https://cursor.com/install-mcp?name=agent-stack-directory&config=eyJ1cmwiOiJodHRwczovL2FnZW50c3RhY2tkaXJlY3RvcnkuY29tL21jcCJ9>) (opens Cursor)

Or add it by hand to `~/.cursor/mcp.json` (all projects) or `.cursor/mcp.json` (this project):

`mcp.json`:

```json
{
  "mcpServers": {
    "agent-stack-directory": {
      "url": "https://agentstackdirectory.com/mcp"
    }
  }
}
```

### VS Code

[Install in VS Code](<https://vscode.dev/redirect/mcp/install?name=agent-stack-directory&config=%7B%22type%22%3A%22http%22%2C%22url%22%3A%22https%3A%2F%2Fagentstackdirectory.com%2Fmcp%22%7D>) (opens VS Code)

Or from a terminal:

```bash
code --add-mcp '{"name":"agent-stack-directory","type":"http","url":"https://agentstackdirectory.com/mcp"}'
```

Or commit it to the repo in `.vscode/mcp.json`:

`.vscode/mcp.json`:

```json
{
  "servers": {
    "agent-stack-directory": {
      "type": "http",
      "url": "https://agentstackdirectory.com/mcp"
    }
  }
}
```

### Devin Desktop

1. Add it to `~/.config/devin/mcp_config.json` (macOS and Linux) or `%APPDATA%\devin\mcp_config.json` (Windows):

`mcp_config.json`:

```json
{
  "mcpServers": {
    "agent-stack-directory": {
      "serverUrl": "https://agentstackdirectory.com/mcp"
    }
  }
}
```

2. Refresh the MCP server list in Cascade.

Devin Desktop is the new name for Windsurf. It reads `serverUrl` (or `url`) for remote servers.

### Codex

```bash
codex mcp add agent-stack-directory --url https://agentstackdirectory.com/mcp
```

Or edit `~/.codex/config.toml` directly:

`config.toml`:

```toml
[mcp_servers.agent-stack-directory]
url = "https://agentstackdirectory.com/mcp"
```

### Gemini CLI

```bash
gemini mcp add --transport http agent-stack-directory https://agentstackdirectory.com/mcp
```

This adds it to the current project. Add `-s user` to use it everywhere.

### Any client

Most clients accept this shape. Some name the URL field differently: `serverUrl` in Devin Desktop, `httpUrl` in Gemini CLI’s settings file.

```json
{
  "mcpServers": {
    "agent-stack-directory": {
      "type": "http",
      "url": "https://agentstackdirectory.com/mcp"
    }
  }
}
```

Zed puts servers under `context_servers` in its settings. Cline needs `"type": "streamableHttp"`, or it assumes SSE.

Client only starts local servers? Bridge it with `npx -y mcp-remote https://agentstackdirectory.com/mcp`.

## Recent changes

- 2026-10-28 17:27 UTC: Tracking started: 4 tools read. Source: automatic check.

More on the History tab, with descriptions before and after for the newest entries: https://mcp.tc/i/agent-stack-directory#history (Atom feed: https://mcp.tc/i/agent-stack-directory/history.xml). It records what mcp.tc's anonymous checks saw, every 3 hours where the tool list can be read without sign-in; it is not a security review.

## Details

- Server version: 0.1.0
- MCP protocol version: 2025-11-25
- Last checked: 2026-11-15 (reachable)
- Listed: 2026-10-28
- Updated: 2026-10-28

---
Source: https://mcp.tc/i/agent-stack-directory (mcp.tc is an independent directory, not affiliated with this server's publisher). Corrections: https://mcp.tc/report