P4mcp Server vs Repowise

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

P4mcp Server logoP4mcp ServerVersion Control · Local subprocess (stdio)Perforce P4 MCP Server is a MCP server that integrates with the Perforce P4 version control system.64GoodAuth: not declaredRepowise logoRepowiseVersion Control · Local subprocess (stdio)Codebase intelligence for AI coding agents. Indexes a repo into a dependency graph, git history, defect-risk code health, auto-generated docs, and architectural decisions, served as 9 task-shaped MCP tools across 15 languages. Runs 100% local; hosted option available.61GoodAuth: no auth required

Verdict: choose P4mcp Server for version control work as a local process; choose Repowise for version control as a local process. You can also run both side by side in one mcpServers block.

Which MCP server should you choose?

P4mcp Server logoChoose P4mcp Server when

  • You need dedicated capabilities in the Version Control domain.
  • You prefer a local stdio subprocess transport.
  • You have the keys it needs: P4PORT, P4USER, P4CLIENT.
  • You want tools like query_server, query_workspaces, modify_workspaces.
Explore P4mcp Server

Repowise logoChoose Repowise when

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

Feature & specification comparison

Rows where the two servers differ are marked.

SpecP4mcp Server logoP4mcp ServerRepowise logoRepowise
CategoryVersion ControlVersion Control
Quality signal64/100 · Good61/100 · Good
Install commandConfirmedConfirmed
TransportLocal subprocess (stdio)Local subprocess (stdio)
AuthNot declaredNo auth required
PricingNot declaredFree
Required env varsP4PORTP4USERP4CLIENTNone listed
Verified ownerCommunity listingCommunity listing
GitHub stars1237,891
Directory activity 0 views 0 installs 0 upvotes 5 views 0 installs 0 upvotes
Tools15Not listed

Tools & capabilities

P4mcp Server tools 15

  • query_serverGet server info and current user information (READ permission)
  • query_workspacesGet workspace details, list workspaces, check type and status (READ permission)
  • modify_workspacesCreate/delete workspace, Update workspace specs, and switch active workspace (WRITE permission)
  • query_filesGet file content, history, info, diff, annotations, search by name, grep by content (READ permission)
  • modify_filesAdd, edit, move, delete, revert, reconcile, resolve, and sync files (WRITE permission)
  • query_changelistsGet changelist details and list changelists (READ permission)
  • modify_changelistsCreate/delete changelists, update changelists and organize files/jobs (WRITE permission)
  • query_shelvesList shelves, get shelve diff and files (READ permission)
  • modify_shelvesCreate/delete, update shelves and unshelve files (WRITE permission)
  • query_jobsGet jobs from changelist and get job details (READ permission)
  • modify_jobsLink or unlink jobs (WRITE permission)
  • query_reviewsGet review details and list reviews (READ permission). Open review - state is 'approved but pending=true' or 'needsReview' or 'needsRevision'. Closed review - state is 'approved but pending=false' or 'rejected' or 'archived'.
  • +3 more on the listing page

Repowise 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.

P4mcp Server

mcpServers (Claude Desktop / Cursor)
{
  "mcpServers": {
    "p4mcp-server": {
      "command": "uvx",
      "args": [
        "p4mcp-server"
      ],
      "env": {
        "P4PORT": "YOUR_P4PORT_HERE",
        "P4USER": "YOUR_P4USER_HERE",
        "P4CLIENT": "YOUR_P4CLIENT_HERE"
      }
    }
  }
}

Repowise

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

Frequently asked questions

P4mcp Server is categorized under Version Control and uses a local stdio subprocess. Repowise belongs to Version Control and uses a local stdio subprocess. Pick P4mcp Server for version control work and Repowise for version control.

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.

P4mcp Server has no declared pricing — check the project's own site. Repowise 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 p4mcp-server and repowise-dev-repowise as separate keys in the same mcpServers object, and your assistant will call tools from either one.

On AllMCPs, P4mcp Server has a quality signal of 64/100 (Good) with 0 views, 0 installs and 123 GitHub stars. Repowise has 61/100 (Good) with 5 views, 0 installs and 7,891 GitHub stars.