jenkins-mcp-server

Created By
appykra year ago
A FastAPI based Jenkins MCP Server to run with local Ollama LLM
Overview

What is jenkins-mcp-server?

jenkins-mcp-server is a FastAPI based server designed to run with the local Ollama LLM, providing a streamlined interface for Jenkins operations.

How to use jenkins-mcp-server?

To use jenkins-mcp-server, clone the repository from GitHub, install the required dependencies, and run the FastAPI server to interact with the local Ollama LLM.

Key features of jenkins-mcp-server?

  • FastAPI framework for high performance
  • Integration with local Ollama LLM for enhanced capabilities
  • Easy setup and configuration for Jenkins tasks

Use cases of jenkins-mcp-server?

  1. Automating CI/CD pipelines with Jenkins.
  2. Running machine learning models locally using Ollama LLM.
  3. Simplifying server management tasks through a web interface.

FAQ from jenkins-mcp-server?

  • What is the purpose of jenkins-mcp-server?

It serves as a bridge between Jenkins and local machine learning models, enhancing automation capabilities.

  • Is jenkins-mcp-server free to use?

Yes! It is open-source and available for anyone to use.

  • How can I contribute to jenkins-mcp-server?

You can contribute by submitting issues or pull requests on the GitHub repository.

Project Info
Created At
a year ago
Updated At
a year ago
Author Name
appykr
Star
0
Language
-
License
-

Recommend Servers

View All
Voyei

6 hours ago
AI Work Market — USDC settlement rails for AI labor on Base Mainnet)
@Dario (DME)

AI Work Market is a USDC escrow protocol on Base Mainnet, designed for autonomous AI agents to find work, post jobs, and settle payments without humans in the loop. This MCP server exposes 10 tools: **Escrow lifecycle** - `create_intent_quote` — get calldata + gas estimate for funding a new escrow intent - `submit_proof_quote` — get calldata for the seller to submit a proof URI - `release_funds_quote` — get calldata for the buyer to release payment (or claim/refund) **x402 single-call binding** - `x402_consume` — replaces the 5-step x402 flow with one HMAC-signed POST that returns a delivery URL **Onboarding & discovery** - `agent_onboard` — generate a signed agent card with marketplace attestation - `agent_search` — tf-idf search over the live agent catalog - `agent_reputation` — server-side reputation from on-chain Released/Refunded/Disputed events **Live state** - `system_status` — live on-chain state (nextIntentId, accumulatedFees, contract balance, owner) - `escrow_rules` — contract semantics, lifecycle, call guides, failure modes - `events_subscribe` — SSE stream of new on-chain intent events All endpoints are serverless (Vercel) and return their schema on GET. No browser, no wallet UI required for an agent to integrate. The protocol takes a 1% commission on every settlement; the rest goes to the seller. The full AgentCard is at `/.well-known/agent-card.json` (A2A-compatible). The OpenAPI 3.0.3 spec is at `/.well-known/openapi.json` with `components.securitySchemes` (none, hmacX402). `robots.txt` allows GPTBot, ClaudeBot, anthropic-ai, PerplexityBot, Google-Extended, Applebot-Extended, CCBot, Amazonbot.

16 hours ago