A side-by-side look at the Agentward and Aegis MCP servers: transport, auth, tools, quality signals, and the config to install either one in Claude, Cursor, Windsurf or VS Code.
No tool names declared yet. Check the project README from the listing page.
Aegis 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.
Agentward
No confirmed install command for Agentward yet — follow the setup steps linked from its listing page rather than a guessed package name.
Agentward is categorized under Security and uses an install path we have not confirmed yet. Aegis belongs to Security and uses a local stdio subprocess. Pick Agentward for security work and Aegis for security.
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. Agentward has no confirmed install command yet — follow its own setup instructions.
Agentward is listed as free. Auth: no auth required. Aegis has no declared pricing — check the project's own site. 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 agentward-ai-agentward and getaegis-aegis as separate keys in the same mcpServers object, and your assistant will call tools from either one.
On AllMCPs, Agentward has a quality signal of 41/100 (Fair) with 6 views, 0 installs and 19 GitHub stars. Aegis has 53/100 (Good) with 2 views, 0 installs and 14 GitHub stars.