GitHub Repository Intelligence vs P4mcp Server
A side-by-side look at the GitHub Repository Intelligence and P4mcp Server MCP servers: transport, auth, tools, quality signals, and the config to install either one in Claude, Cursor, Windsurf or VS Code.
Verdict: choose GitHub Repository Intelligence for version control work over a hosted endpoint; choose P4mcp Server 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?
Choose GitHub Repository Intelligence when
- You need dedicated capabilities in the Version Control domain.
- You prefer a remote HTTP/SSE transport.
- You have the keys it needs:
APIFY_TOKEN. - You want tools like
get_repo_overview, list_recent_prs, get_contributors.
Choose 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.
Feature & specification comparison
Rows where the two servers differ are marked.
| Spec | ||
|---|---|---|
| Category | Version Control | Version Control |
| Quality signal | 48/100 · Fair | 61/100 · Good |
| Install command | Confirmed | Confirmed |
| Transport | Remote HTTP/SSE | Local subprocess (stdio) |
| Auth | Not declared | Not declared |
| Pricing | Not declared | Not declared |
| Required env vars | APIFY_TOKEN | P4PORTP4USERP4CLIENT |
| Verified owner | Community listing | Community listing |
| GitHub stars | 0 | 123 |
| Directory activity | 2 views 0 installs 0 upvotes | 0 views 0 installs 0 upvotes |
| Tools | 6 | 15 |
| Full listing | View GitHub Repository Intelligence | View P4mcp Server |
Tools & capabilities
GitHub Repository Intelligence tools 6
get_repo_overview"Is this repo still maintained?"list_recent_prs"Show me the last 20 merged PRs by user X"get_contributors"Who maintains this project?"get_hot_files"Where's the churn?"get_ci_status"Is the default branch green?"get_dependencies"What does this project depend on?"
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
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.
GitHub Repository Intelligence
{
"mcpServers": {
"github-repository-intelligence": {
"url": "https://cg-nguyen--github-repo-intel-mcp.apify.actor/mcp"
}
}
}
P4mcp Server
{
"mcpServers": {
"p4mcp-server": {
"command": "uvx",
"args": [
"p4mcp-server"
],
"env": {
"P4PORT": "YOUR_P4PORT_HERE",
"P4USER": "YOUR_P4USER_HERE",
"P4CLIENT": "YOUR_P4CLIENT_HERE"
}
}
}
}
Frequently asked questions
GitHub Repository Intelligence is categorized under Version Control and uses a remote HTTP/SSE transport. P4mcp Server belongs to Version Control and uses a local stdio subprocess. Pick GitHub Repository Intelligence for version control work and P4mcp Server 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.
GitHub Repository Intelligence has no declared pricing — check the project's own site. P4mcp Server 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 github-repository-intelligence and p4mcp-server as separate keys in the same mcpServers object, and your assistant will call tools from either one.
On AllMCPs, GitHub Repository Intelligence has a quality signal of 48/100 (Fair) with 2 views, 0 installs and 0 GitHub stars. P4mcp Server has 61/100 (Good) with 0 views, 0 installs and 123 GitHub stars.