Back to home

Directory-first guide

Find the right MCP server, then install what you verified.

MCPizy does not require an account for discovery. Start with the decision, inspect the profile’s evidence gaps and follow the setup path that matches your client.

01

Find

Search all servers or browse by category and client.

02

Verify

Read the available audit, repository, setup and authentication evidence.

03

Install

Copy the upstream command, client configuration or optional CLI command.

The recommended path

  1. 1. Open the directory or a comparison

    Use the complete directory when you know the integration, or comparisons when you are choosing between alternatives.

  2. 2. Treat missing coverage as unknown

    A profile can document an install path without proving maintenance or security. Check the evidence date, upstream repository, licence and authentication notes that are available.

  3. 3. Use the client-specific setup

    Copy the configuration shown for VS Code, Cursor, Claude Code or Copilot when present. Then verify credentials and permissions against the upstream project before first use.

Optional

CLI reference

View the npm package

The CLI is an optional local convenience. Search and install are directory utilities; proxy and observer features are secondary tools and should not be treated as the core public-product promise.

npx mcpizy search database

Search the public catalogue from a terminal.

npx mcpizy install postgres

Add a listed server to the Claude Code configuration.

npx mcpizy status

Inspect the optional local MCPizy setup state.

npx mcpizy help

List the commands available in the installed CLI version.

Compare servers Read the FAQ