Agent Audit vs MCP Server Commands
A side-by-side look at the Agent Audit and MCP Server Commands MCP servers: transport, auth, tools, quality signals, and the config to install either one in Claude, Cursor, Windsurf or VS Code.
Verdict: choose Agent Audit for coding agents work as a local process; choose MCP Server Commands for coding agents as a local process. You can also run both side by side in one mcpServers block.
Which MCP server should you choose?
Choose Agent Audit when
- You need dedicated capabilities in the Coding Agents domain.
- You prefer a local stdio subprocess transport.
- You have the keys it needs:
LIGHTHOUSE_MCP_ALLOW_LOCALHOST. - You want tools like
analyze_website_performance.
Choose MCP Server Commands when
- You need dedicated capabilities in the Coding Agents domain.
- You prefer a local stdio subprocess transport.
- Its auth model fits you: No auth required.
- You want tools like
run_process.
Feature & specification comparison
Rows where the two servers differ are marked.
| Spec | ||
|---|---|---|
| Category | Coding Agents | Coding Agents |
| Quality signal | 53/100 · Good | 65/100 · Great |
| Install command | Confirmed | Confirmed |
| Transport | Local subprocess (stdio) | Local subprocess (stdio) |
| Auth | Not declared | No auth required |
| Pricing | Not declared | Free |
| Required env vars | LIGHTHOUSE_MCP_ALLOW_LOCALHOST | None listed |
| Verified owner | Community listing | Community listing |
| GitHub stars | 4 | 237 |
| Directory activity | 1 views 0 installs 0 upvotes | 3 views 0 installs 0 upvotes |
| Tools | 1 | 1 |
| Full listing | View Agent Audit | View MCP Server Commands |
Tools & capabilities
Agent Audit tools 1
analyze_website_performanceRuns Lighthouse and site intelligence against a target URL:
MCP Server Commands tools 1
run_processRun a process on this linux machine
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.
Agent Audit
{
"mcpServers": {
"agent-audit": {
"command": "npx",
"args": [
"-y",
"@fullstackdegen/agent-audit"
],
"env": {
"LIGHTHOUSE_MCP_ALLOW_LOCALHOST": "YOUR_LIGHTHOUSE_MCP_ALLOW_LOCALHOST_HERE"
}
}
}
}
MCP Server Commands
{
"mcpServers": {
"g0t4-mcp-server-commands": {
"command": "npx",
"args": [
"mcp-server-commands"
]
}
}
}
Frequently asked questions
Agent Audit is categorized under Coding Agents and uses a local stdio subprocess. MCP Server Commands belongs to Coding Agents and uses a local stdio subprocess. Pick Agent Audit for coding agents work and MCP Server Commands for coding agents.
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.
Agent Audit has no declared pricing — check the project's own site. MCP Server Commands 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 agent-audit and g0t4-mcp-server-commands as separate keys in the same mcpServers object, and your assistant will call tools from either one.
On AllMCPs, Agent Audit has a quality signal of 53/100 (Good) with 1 views, 0 installs and 4 GitHub stars. MCP Server Commands has 65/100 (Great) with 3 views, 0 installs and 237 GitHub stars.