.DkNUKaKx_ZLAT4m.webp?dpl=dpl_ARtVL4739pNJnxC8yxqCNToe4mN7){kind=small}
Connectors / Developer tools · HTTP Connector
Automate Jenkins with Tray.ai
Create a job in Jenkins. Connect Jenkins to the rest of your developer tools stack with Tray.ai.
What can you do with Jenkins on Tray.ai?
Jenkins is an open-source automation server that builds, tests, and deploys software through jobs and pipelines you run on your own infrastructure. Tray.ai connects to Jenkins through the HTTP Connector, so your workflows can call the Jenkins API alongside the rest of your stack.
- Trigger a build when a pull request is approved in your code repository.
- Get build details for failed runs and post them to your team chat for the on-call engineer.
- Build with parameters to deploy a release when a change ticket is approved in your help desk.
- Connects through
- HTTP Connector
- Authentication
- Basic authentication
Set it up
Connect Jenkins to Tray.ai
Each step uses Jenkins's own API details, from its documentation.
Step 1
Save Jenkins's username and password
Save the credentials Jenkins gives you as a Tray.ai authentication. The HTTP Client sends them as basic auth. They stay out of the workflow and out of the logs.
Step 2
Import a request from Jenkins's docs
Add an HTTP Client step and paste a cURL example from Jenkins's API docs. Tray.ai fills in the method, URL, headers, and query.
Step 3
Start with “List jobs”
It's one of 7 documented actions, under Jobs. The response comes back as data the next step can map into your other apps.
Step 4
Hand it to an AI agent
Wrap “Trigger a build” and “Build with parameters” in workflows, and Tray.ai's Agent Gateway for MCP publishes them as governed tools Claude and other AI agents can call.
Give your AI agents Jenkins tools
Build an MCP server on Jenkins in Agent Gateway and choose which actions your agents can call. Every call runs with access control and an audit trail. How Agent Gateway works
- List jobs
- Get build details
- Trigger a build
- Build with parameters
- Create a job
- Copy a job
- Get the last successful build
What the Jenkins API covers
2 resources and 7 documented actions, each one a call the HTTP Connector can make from a Tray.ai workflow. Connecting it takes a few clicks: here's how.
Jobs
- List jobs
- Trigger a build
- Build with parameters
- Create a job
- Copy a job
Builds
- Get build details
- Get the last successful build
Checked against Jenkins's own documentation on 2026-10-22
How Tray.ai makes this work
Jenkins plugs into the whole Tray.ai platform
Intelligent Integration
Integrate and automate across 10,100+ apps, databases, APIs, and services with visual workflows, error handling, and observability.
Learn more →Agent Builder
Build AI agents that read, write, and take action in Jenkins — with guardrails, audit, and human-in-the-loop.
Learn more →Agent Gateway for MCP
Expose Jenkins actions as governed MCP tools — observable, rate-limited, authenticated.
Learn more →Tray Helix
Build apps on Jenkins data with your AI assistant, then deploy, run, and govern them on Tray.ai.
Learn more →More developer tools apps on Tray.ai
Dedicated connectors and other apps Tray.ai reaches in the same category. See every developer tools connector →
Frequently asked questions
What can a Tray.ai workflow do in Jenkins?
+
The Jenkins API documents 7 actions across 2 resources (Jobs, Builds). For example: List jobs; Get build details. A workflow can make any documented call through the HTTP Connector.
How does Tray.ai authenticate with Jenkins?
+
The Jenkins API uses basic authentication. You save it once as a Tray.ai authentication, and the HTTP Connector adds it to every request.
See Jenkins working against your stack.
We'll walk through a tailored demo with your systems plugged in.
Thanks — someone from our team will be in touch soon.