Semgrep vs UniFi Access MCP

A side-by-side look at the Semgrep and UniFi Access MCP MCP servers: transport, auth, tools, quality signals, and the config to install either one in Claude, Cursor, Windsurf or VS Code.

Semgrep logoSemgrepSecurity · Local subprocess (stdio)Scan code for security vulnerabilities using Semgrep.48FairAuth: no auth requiredUniFi Access MCP logoUniFi Access MCPSecurity · Local subprocess (stdio)Manage UniFi Access doors, credentials, policies, visitors, and events via MCP.63GoodAuth: not declared

Verdict: choose Semgrep for security work as a local process; choose UniFi Access MCP for security as a local process. You can also run both side by side in one mcpServers block.

Which MCP server should you choose?

Semgrep logoChoose Semgrep when

  • You need dedicated capabilities in the Security domain.
  • You prefer a local stdio subprocess transport.
  • Its auth model fits you: No auth required.
Explore Semgrep

UniFi Access MCP logoChoose UniFi Access MCP when

  • You need dedicated capabilities in the Security domain.
  • You prefer a local stdio subprocess transport.
  • You want tools like unifi_setup_status.
Explore UniFi Access MCP

Feature & specification comparison

Rows where the two servers differ are marked.

SpecSemgrep logoSemgrepUniFi Access MCP logoUniFi Access MCP
CategorySecuritySecurity
Quality signal48/100 · Fair63/100 · Good
Install commandConfirmedConfirmed
TransportLocal subprocess (stdio)Local subprocess (stdio)
AuthNo auth requiredNot declared
PricingFreeFree
Required env varsNone listedNone listed
Verified ownerCommunity listingCommunity listing
GitHub stars17,146942
Directory activity 1 views 0 installs 0 upvotes 2 views 0 installs 0 upvotes
ToolsNot listed1

Tools & capabilities

Semgrep tools

No tool names declared yet. Check the project README from the listing page.

UniFi Access MCP tools 1

  • unifi_setup_statusReport why the unifi-network server has no controller tools, how to configure it and how to load the new settings. Call this when the server's tools are missing.

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.

Semgrep

mcpServers (Claude Desktop / Cursor)
{
  "mcpServers": {
    "semgrep-semgrep": {
      "command": "uvx",
      "args": [
        "semgrep"
      ]
    }
  }
}

UniFi Access MCP

mcpServers (Claude Desktop / Cursor)
{
  "mcpServers": {
    "unifi-access-mcp": {
      "command": "uvx",
      "args": [
        "unifi-access-mcp@latest"
      ]
    }
  }
}

Frequently asked questions

Semgrep is categorized under Security and uses a local stdio subprocess. UniFi Access MCP belongs to Security and uses a local stdio subprocess. Pick Semgrep for security work and UniFi Access MCP 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.

Semgrep is listed as free. Auth: no auth required. UniFi Access MCP is listed as free. 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 semgrep-semgrep and unifi-access-mcp as separate keys in the same mcpServers object, and your assistant will call tools from either one.

On AllMCPs, Semgrep has a quality signal of 48/100 (Fair) with 1 views, 0 installs and 17,146 GitHub stars. UniFi Access MCP has 63/100 (Good) with 2 views, 0 installs and 942 GitHub stars.