A side-by-side look at the Directory and Aria Icons MCP servers: transport, auth, tools, quality signals, and the config to install either one in Claude, Cursor, Windsurf or VS Code.
Verdict: choose Directory for developer tools work over a hosted endpoint; choose Aria Icons for developer tools as a local process. You can also run both side by side in one mcpServers block.
Which MCP server should you choose?
Choose Directory when
You need dedicated capabilities in the Developer Tools domain.
No tool names declared yet. Check the project README from the listing page.
Aria Icons tools
No tool names declared yet. Check the project README from the listing page.
Ready-to-paste client configs
Paste either block (or both) into your client config, e.g. claude_desktop_config.json or ~/.cursor/mcp.json. We only show a config when the install command is confirmed.
Directory is categorized under Developer Tools and uses a remote HTTP/SSE transport. Aria Icons belongs to Developer Tools and uses a local stdio subprocess. Pick Directory for developer tools work and Aria Icons for developer tools.
Copy the mcpServers block from the config section on this page into your client's config (for example claude_desktop_config.json or ~/.cursor/mcp.json), then fully restart the client.
Directory has no declared pricing — check the project's own site. Aria Icons is listed as free. Auth: no auth required. If a server needs environment variables such as API keys, define them under the env key in your client's MCP config.
Yes. MCP clients support multiple servers: add directory-5 and aria-icons as separate keys in the same mcpServers object, and your assistant will call tools from either one.
On AllMCPs, Directory has a quality signal of 36/100 (Fair) with 0 views, 0 installs and 0 GitHub stars. Aria Icons has 49/100 (Fair) with 2 views, 0 installs and 87 GitHub stars.