
Worktrack Port
io.github.CloudCorpRecordsPublished by GitHub account CloudCorpRecordsv0.1.0Updated Nov 3, 2026
Jira issues and Confluence pages via the REST APIs, as MCP tools.
The publisher's own server: Port
Overview
Worktrack Port's local MCP server; no sign-in required; STDIO.
No AI overview yet: these facts come from the registry entry and the server itself.
Installation
In SourceWeft
- Open Worktrack Port in the dashboard and add it to a workspace.
- Enable the server for the chats that should use its tools.
Desktop only via STDIO. STDIO servers start a local process, so they need the SourceWeft desktop host.
Other MCP clients
Follow the launch instructions in the repository.
README
worktrack-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:
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
Each tool name is a subcommand taking one JSON object argument.
MCP client config
Docker
Development
License
MIT
Source: README.md at commit 46cf4ae
Tools
0Version history
1- v0.1.0LatestNov 3, 2026
Score
50% of the applicable checks met
How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.
- Reached in the last 30 days25 pts
Keep the endpoint answering the MCP handshake; SourceWeft probes it every 30 days.
- Auth declared10 pts
Declare the credential headers in the registry entry, or keep the endpoint answering the probe so its auth can be classified.
- Tools listed15 pts
Answer tools/list without a credential, or ship a package that starts in a sandbox without one.
- DescriptionRequired15 pts
- Logo10 pts
- Documentation15 pts
- License10 pts
Other Port integrations

Port
io.portOfficial publisher
Port's remote MCP server connects Port.io to an IDE, LLM or agent platform, letting an assistant work with your Port.io environment through OAuth-authenticated,

GravityPort
Published by GitHub account fengseekling-coder
MCP server bundled with the GravityPort desktop app that lets Claude, Codex and other clients search and record a local library of AI-generated images, videos…

Videohub Port
Published by GitHub account CloudCorpRecords
YouTube videos, channels, playlists, comments and transcripts as MCP tools.

Tasklist Port
Published by GitHub account CloudCorpRecords
Tasklist Port's local MCP server; no sign-in required; STDIO.

Taskboard Port
Published by GitHub account CloudCorpRecords
Asana workspaces, projects and tasks via the REST API, as MCP tools.