Agent Connectors MCP server
# Agent Connectors MCP server
Read-only MCP server that searches the public [Agent Connectors](https://agentconnectors.dev) directory of MCP servers and AI agent connectors.
[](https://glama.ai/mcp/servers/JaniJegoroff/agent-connectors-mcp)
[Browse the full directory](https://agentconnectors.dev)
## What it does
The tools read `https://agentconnectors.dev/api/tools.json?limit=all` and follow `next` if the response is paged. They return directory records. They do not run, install, or test the servers in those records.
- `search_tools` — match a query, with an optional category slug, against listing name, slug, and description.
- `get_tool` — one listing by slug.
- `list_categories` — category name, slug, and listing count, counted from the catalogue response.
Example query for `search_tools`:
```json
{ "query": "web search", "category": "search" }
```
## Install
This repository is not published to npm. Clone it, install dependencies, and point your client at the clone. Requires Node.js 22 or newer.
```bash
git clone https://github.com/JaniJegoroff/agent-connectors-mcp.git
cd agent-connectors-mcp
npm install
```
The server speaks MCP over stdin and stdout:
```bash
node --experimental-strip-types src/index.ts
```
Replace `/absolute/path/to/agent-connectors-mcp` with the absolute path of your clone. Run `npm install` in that directory first.
### Claude Desktop
Add this to `claude_desktop_config.json`:
```json
{
"mcpServers": {
"agent-connectors": {
"command": "node",
"args": ["--experimental-strip-types", "src/index.ts"],
"cwd": "/absolute/path/to/agent-connectors-mcp"
}
}
}
```
### Cursor
Project file `.cursor/mcp.json`, or the global Cursor MCP settings:
```json
{
"mcpServers": {
"agent-connectors": {
"command": "node",
"args": ["--experimental-strip-types", "src/index.ts"],
"cwd": "/absolute/path/to/agent-connectors-mcp"
}
}
}
```
### VS Code
Project file `.vscode/mcp.json`. `cwd` is the clone root:
```json
{
"servers": {
"agent-connectors": {
"type": "stdio",
"command": "node",
"args": ["--experimental-strip-types", "src/index.ts"],
"cwd": "${workspaceFolder}"
}
}
}
```
Optional streamable HTTP, bound to `127.0.0.1:8791`:
```bash
node --experimental-strip-types src/index.ts --http
```
The HTTP endpoint is `http://127.0.0.1:8791/mcp`. Set `PORT` to use another port. Set `AGENT_CONNECTORS_API` to point the catalogue fetch at another `tools.json` URL.
## Docker
Glama builds this image and introspects the server over stdio.
```bash
docker build -t agent-connectors-mcp .
docker run -i --rm agent-connectors-mcp
```
The image is `node:22-slim`. It installs production dependencies with `npm ci --omit=dev`, copies `src`, and starts stdio mode with `node --experimental-strip-types src/index.ts`.
TDQS
Scored across 3 tools
Each tool has a clearly distinct purpose: search_tools returns multiple catalogue matches, get_tool fetches a single listing by slug, and list_categories enumerates categories. The descriptions even explicitly clarify that search/get do not run servers, further separating read-only lookup semantics.
All three names follow a clean verb_noun snake_case pattern (search_tools, get_tool, list_categories). No mixed conventions or vague verbs.
Three tools is a reasonable, well-scoped surface for a read-only directory/lookup server, with no redundancy. It is on the thin side and could justify one more browsing tool, but nothing is gratuitous.
Search, single-slug lookup, and category enumeration cover the basic browse flow, but list_categories only returns counts with no obvious tool to fetch listings within a category (unless search supports that filter). This leaves a potential browse-by-category dead end, though agents can likely work around it via search.