CONNECT APP
Build with Jira Data Center
Business Management
- API key
MCP
Give your agent Jira Data Center tools
Every Jira Data Center action is exposed as an MCP tool on Pipedream's remote server. Point a client at it with your end user's ID and Connect resolves that user's Jira Data Center account for each tool call — you store no tokens.
// accessToken: mint a short-lived token with the Connect SDK — see the MCP guide
const transport = new StreamableHTTPClientTransport(
new URL("https://remote.mcp.pipedream.net/v3"),
{
requestInit: {
headers: {
Authorization: `Bearer ${accessToken}`,
"x-pd-project-id": "{project_id}",
"x-pd-environment": "production",
"x-pd-external-user-id": "{external_user_id}", // any stable ID for this user in your system
"x-pd-app-slug": "jira_data_center",
},
},
},
)
const mcp = new Client({ name: "my-agent", version: "1.0.0" })
await mcp.connect(transport)
const { tools } = await mcp.listTools()
// e.g. run Create Board:
const result = await mcp.callTool({
name: "jira_data_center-create-board",
arguments: {
name: "Name",
type: "Type",
},
})# access_token: mint a short-lived token with the Connect SDK — see the MCP guide
headers = {
"Authorization": f"Bearer {access_token}",
"x-pd-project-id": "{project_id}",
"x-pd-environment": "production",
"x-pd-external-user-id": "{external_user_id}", # any stable ID for this user in your system
"x-pd-app-slug": "jira_data_center",
}
async with streamablehttp_client("https://remote.mcp.pipedream.net/v3", headers=headers) as (read, write, _):
async with ClientSession(read, write) as session:
await session.initialize()
tools = await session.list_tools()
# e.g. run Create Board:
result = await session.call_tool("jira_data_center-create-board", {
"name": "Name",
"type": "Type",
})API PROXY
Call the Jira Data Center API directly
For an endpoint with no pre-built tool, the Connect proxy forwards your request to the Jira Data Center API with the connected user's credentials attached. You store no tokens and write no refresh logic.
const resp = await pd.proxy.get({
externalUserId: "{external_user_id}", // any stable ID for this user in your system
accountId: "apn_xxxxxxx",
url: "https://api.example.com/v1/me",
})
// Any allowed Jira Data Center endpoint works here. Pipedream attaches the
// connected account's credentials to the outgoing request.# The path segment is the target URL, URL-safe base64 encoded:
# https://api.example.com/v1/me
curl "https://api.pipedream.com/v1/connect/{project_id}/proxy/aHR0cHM6Ly9hcGkuZXhhbXBsZS5jb20vdjEvbWU?external_user_id={external_user_id}&account_id=apn_xxxxxxx" \
-H "Authorization: Bearer {access_token}" \
-H "x-pd-environment: production"SDK
Run Jira Data Center actions from your backend
Connect a user's Jira Data Center account once, then run Create Board on their behalf from your own code — TypeScript, Python, or plain HTTP.
import { PipedreamClient } from "@pipedream/sdk"
const pd = new PipedreamClient({
projectId: process.env.PIPEDREAM_PROJECT_ID!,
clientId: process.env.PIPEDREAM_CLIENT_ID!,
clientSecret: process.env.PIPEDREAM_CLIENT_SECRET!,
projectEnvironment: "production",
})
const result = await pd.actions.run({
id: "jira_data_center-create-board",
externalUserId: "{external_user_id}", // any stable ID for this user in your system
configuredProps: {
jira_data_center: { authProvisionId: "apn_xxxxxxx" },
name: "Name",
type: "Type",
},
})from pipedream import Pipedream
pd = Pipedream(
client_id="{oauth_client_id}",
client_secret="{oauth_client_secret}",
project_id="{project_id}",
project_environment="production",
)
result = pd.actions.run(
id="jira_data_center-create-board",
external_user_id="{external_user_id}", # any stable ID for this user in your system
configured_props={
"jira_data_center": {"authProvisionId": "apn_xxxxxxx"},
"name": "Name",
"type": "Type",
},
)curl -X POST https://api.pipedream.com/v1/connect/{project_id}/actions/run \
-H "Content-Type: application/json" \
-H "X-PD-Environment: production" \
-H "Authorization: Bearer {access_token}" \
-d '{
"external_user_id": "{external_user_id}",
"id": "jira_data_center-create-board",
"configured_props": {
"jira_data_center": { "authProvisionId": "apn_xxxxxxx" },
"name": "Name",
"type": "Type"
}
}'TOOLS
Jira Data Center actions
On-demand operations your product or agent can configure and run on behalf of a connected user.
-
Create Board
actionCreates a new board. See the documentationWritev0.0.2 -
Create Filter
actionCreates a filter. See the documentationWritev0.0.2 -
Create Future Sprint
actionCreates a future sprint. See the documentationWritev0.0.2 -
Delete Sprint
actionDeletes a sprint. See the documentationWritev0.0.2 -
Get Board
actionRetrieves a board. See the documentationRead-onlyv0.0.2 -
Get Issues From Backlog
actionGets the issues from the backlog. See the documentationRead-onlyv0.0.2 -
Get Resolution
actionGets a resolution by ID. See the documentationRead-onlyv0.0.2 -
Get Server Info
actionReturns general information about the Jira Data Center instance, including version, base URL, and deployment type. See the documentationRead-onlyv0.0.1 -
Get Sprint
actionGets a sprint by ID. See the documentationRead-onlyv0.0.2 -
Get Updated Work Logs
actionGets the updated work logs for a given time period. See the documentationRead-onlyv0.0.2 -
Get Worklogs by ID
actionGets the worklogs by IDs. See the documentationRead-onlyv0.0.2 -
List Board Issues
actionLists the issues for a given board. See the documentationRead-onlyv0.0.2 -
List Boards
actionRetrieves a list of boards. See the documentationRead-onlyv0.0.2 -
List Epic Issues
actionLists the issues for a given epic. See the documentationRead-onlyv0.0.2 -
List Epics
actionLists the epics for a given board. See the documentationRead-onlyv0.0.2 -
List Filter ID Options
actionRetrieves available options for the Filter ID field.Read-onlyv0.0.1 -
List Issues Without Epic
actionLists the issues without an epic. See the documentationRead-onlyv0.0.2 -
List Project ID Options
actionRetrieves available options for the Project ID field.Read-onlyv0.0.1 -
List Resolutions
actionLists all resolutions. See the documentationRead-onlyv0.0.2 -
List Sprint Issues
actionLists the issues for a given sprint. See the documentationRead-onlyv0.0.2 -
List Sprints
actionLists the sprints for a given board. See the documentationRead-onlyv0.0.2 -
List Worklog IDs Actions
actionRetrieves available options for the Worklog IDs field.Read-onlyv0.0.1 -
Move Issues To Backlog
actionMoves issues to the backlog. See the documentationWritev0.0.2 -
Move Issues To Sprint
actionMoves issues to a sprint. See the documentationWritev0.0.2 -
Update Sprint Fully
actionPerforms a full update of a sprint. A full update means that the result will be exactly the same as the request body. Any fields not present in the request JSON will be set to null. See the documentationWritev0.0.3 -
Update Sprint Partially
actionPerforms a partial update of a sprint. A partial update means that fields not present in the request JSON will not be updated. See the documentationWritev0.0.3
EVENTS
Jira Data Center triggers
Event sources your backend can deploy for users and receive through a webhook.
No Jira Data Center triggers are available yet.
MULTI-APP
Use Jira Data Center with other popular apps
Most products don't stop at one integration. Pair Jira Data Center with the other apps your users rely on, and ship use cases that span both.
REFERENCE
App details
Reference metadata for the Jira Data Center connector in the Pipedream registry.
- App slug
- jira_data_center
- Authentication
- API key
- Categories
- Business Management
- Actions
- 26
- Triggers
- 0
- API proxy
- Available