About worktrack-port
worktrack-port is an MCP server that accesses Jira issues and Confluence pages through Atlassian REST APIs. Its 12-tool core covers search, retrieval, creation, and updates, but does not reproduce the hosted server's OAuth surface.
Key features
- 01Search and manage Jira issues
- 02Add comments to Jira issues
- 03List and retrieve Jira projects
- 04Search and manage Confluence pages
- 05List Confluence spaces
- 06Convert plain text to ADF
Use cases
- 01Search Jira issues with a JQL query
- 02Create or update an issue and add a comment
- 03Find or edit a Confluence page
- 04List projects or spaces
MCP support
Exposes 12 tools for Jira and Confluence operations to MCP clients. It connects to Atlassian REST APIs using account email, API token, and site URL credentials.
Configuration
Local server config is the same for every client. Copy it into your client’s MCP config file.
npx -y @reneturcios/worktrack-portLocal servers need a runtime on your machine (e.g. Node.js 18+). Config file locations differ by client; see your client’s docs.
Tools
12Saved tool list · updated 1w ago
| Parameter | Type | Required | Description |
|---|---|---|---|
| jql | string | Yes | The JQL (Jira Query Language) query used to search for issues. |
| max_results | number | No | Maximum number of issues to return. |
Details
From the project READMEworktrack-port
Jira issues and Confluence pages as MCP tools, talking to the Atlassian REST APIs. worktrack-port is a clean-room rebuild of the core surface of the Atlassian remote MCP server, under a new name: the same tool names and wire behaviour, fresh code, no copied branding. The original is a hosted remote MCP server; this rebuild is a REST-compatible client for the same upstream APIs — the hosted OAuth surface is not reproduced.
Tools (core subset, 12)
Jira: search_issues, get_issue, create_issue, update_issue,
add_comment, list_projects, get_project.
Confluence: search_content, get_page, create_page,
update_page, list_spaces.
Not in this subset: Jira boards/sprints/agile, workflows and transitions admin, users/groups admin, attachments, dashboards and filters, service desk; Confluence attachments, labels, permissions, children/ancestors operations, blogposts, and space create/delete.
Plain-text issue descriptions and comments are converted to Atlassian Document Format (ADF) before they are sent.
Setup
Create an Atlassian API token for your account, then set:
export [email protected]
export ATLASSIAN_API_TOKEN=...
export ATLASSIAN_SITE_URL=https://your-site.atlassian.net
Without any one of them, every tool call fails with an error naming the missing variable (checked in the order EMAIL, API_TOKEN, SITE_URL).
CLI
npx @reneturcios/worktrack-port search_issues '{"jql":"project = ABC"}'
npx @reneturcios/worktrack-port mcp # stdio MCP server
Each tool name is a subcommand taking one JSON object argument.
MCP client config
{
"mcpServers": {
"worktrack-port": {
"command": "npx",
"args": ["-y", "@reneturcios/worktrack-port", "mcp"],
"env": {
"ATLASSIAN_EMAIL": "[email protected]",
"ATLASSIAN_API_TOKEN": "...",
"ATLASSIAN_SITE_URL": "https://your-site.atlassian.net"
}
}
}
}
Docker
docker run -i -e ATLASSIAN_EMAIL -e ATLASSIAN_API_TOKEN -e ATLASSIAN_SITE_URL ghcr.io/cloudcorprecords/worktrack-port
Development
npm install
npm run build
npm test
License
MIT
Comments
New to MCP?
From what the protocol is to installing your first server, these answers cover most first questions.
An open protocol that defines how AI applications connect to external tools and data in a uniform way. Clients talk to the model; MCP servers provide tools, resources and prompt templates. They exchange standard messages, so one server can be reused by many clients.