PetKit vs Jenkins MCP Server
A side-by-side look at the PetKit and Jenkins MCP Server MCP servers: transport, auth, tools, quality signals, and the config to install either one in Claude, Cursor, Windsurf or VS Code.
Verdict: choose PetKit for developer tools work as a local process; choose Jenkins MCP Server for developer tools. You can also run both side by side in one mcpServers block.
Which MCP server should you choose?
Choose PetKit when
- You need dedicated capabilities in the Developer Tools domain.
- You prefer a local stdio subprocess transport.
- You have the keys it needs:
PETKIT_EMAIL, PETKIT_PASSWORD, PETKIT_REGION, PETKIT_TIMEZONE, MCP_PUBLIC_URL, MCP_OWNER_PASSWORD, MCP_HOST, MCP_PORT.
Choose Jenkins MCP Server when
- You need dedicated capabilities in the Developer Tools domain.
- Its auth model fits you: API key required.
- You have the keys it needs:
JENKINS_URL, JENKINS_USER, JENKINS_API_TOKEN, JENKINS_MAX_RETRIES, JENKINS_RETRY_BASE_DELAY, JENKINS_RETRY_MAX_DELAY, MCP_PORT, MCP_HOST. - You want tools like
trigger_job, get_job_info, list_jobs.
Feature & specification comparison
Rows where the two servers differ are marked.
| Spec | ||
|---|---|---|
| Category | Developer Tools | Developer Tools |
| Quality signal | 36/100 · Fair | 48/100 · Fair |
| Install command | Confirmed | Not confirmed yet |
| Transport | Local subprocess (stdio) | — |
| Auth | Not declared | API key required |
| Pricing | Not declared | Free |
| Required env vars | PETKIT_EMAILPETKIT_PASSWORDPETKIT_REGIONPETKIT_TIMEZONEMCP_PUBLIC_URLMCP_OWNER_PASSWORDMCP_HOSTMCP_PORT | JENKINS_URLJENKINS_USERJENKINS_API_TOKENJENKINS_MAX_RETRIESJENKINS_RETRY_BASE_DELAYJENKINS_RETRY_MAX_DELAYMCP_PORTMCP_HOST |
| Verified owner | Community listing | Community listing |
| GitHub stars | 0 | 4 |
| Directory activity | 0 views 0 installs 0 upvotes | 5 views 0 installs 0 upvotes |
| Tools | Not listed | 21 |
| Full listing | View PetKit | View Jenkins MCP Server |
Tools & capabilities
PetKit tools
No tool names declared yet. Check the project README from the listing page.
Jenkins MCP Server tools 21
trigger_jobTrigger a Jenkins job with optional parameters.get_job_infoGet detailed information about a Jenkins job.list_jobsList Jenkins jobs with advanced filtering.search_jobsSearch for Jenkins jobs by pattern.search_and_triggerSearch for jobs and trigger all matches.get_folder_infoGet information about a Jenkins folder.get_build_statusGet status of a specific build.get_console_logGet console output from a build.summarize_build_logGet a summarized version of build console log.get_pipeline_statusGet detailed pipeline execution status with stage information.list_build_artifactsList all artifacts from a build.download_build_artifactDownload a specific build artifact.- +9 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.
PetKit
{
"mcpServers": {
"petkit": {
"command": "npx",
"args": [
"-y",
"mcp-server-petkit"
],
"env": {
"PETKIT_EMAIL": "YOUR_PETKIT_EMAIL_HERE",
"PETKIT_PASSWORD": "YOUR_PETKIT_PASSWORD_HERE",
"PETKIT_REGION": "YOUR_PETKIT_REGION_HERE",
"PETKIT_TIMEZONE": "YOUR_PETKIT_TIMEZONE_HERE",
"MCP_PUBLIC_URL": "YOUR_MCP_PUBLIC_URL_HERE",
"MCP_OWNER_PASSWORD": "YOUR_MCP_OWNER_PASSWORD_HERE",
"MCP_HOST": "YOUR_MCP_HOST_HERE",
"MCP_PORT": "YOUR_MCP_PORT_HERE"
}
}
}
}
Jenkins MCP Server
No confirmed install command for Jenkins MCP Server yet — follow the setup steps linked from its listing page rather than a guessed package name.
Frequently asked questions
PetKit is categorized under Developer Tools and uses a local stdio subprocess. Jenkins MCP Server belongs to Developer Tools and uses an install path we have not confirmed yet. Pick PetKit for developer tools work and Jenkins MCP Server for developer tools.
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. Jenkins MCP Server has no confirmed install command yet — follow its own setup instructions.
PetKit has no declared pricing — check the project's own site. Jenkins MCP Server is listed as free. Auth: api key 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 petkit and avisangle-jenkins-mcp-server as separate keys in the same mcpServers object, and your assistant will call tools from either one.
On AllMCPs, PetKit has a quality signal of 36/100 (Fair) with 0 views, 0 installs and 0 GitHub stars. Jenkins MCP Server has 48/100 (Fair) with 5 views, 0 installs and 4 GitHub stars.