list_jira_projectsLABSCO SUMMARY
Four servers and, more usefully, the thing that installs them.
The manager is the reason to look at this: isolated environments per server plus one command that writes config for six different clients is the part everybody rebuilds badly. Of the bundled servers, jira-helper is the substantial one, and loadbearing-youtube is the unusual one — it looks for the load-bearing claims in a video rather than summarising it.
What it is
A monorepo of Python MCP servers with an installer, mcp-manager, that gives each server its own isolated uv-managed environment and writes the client configuration for you. mcp-manager sync covers Cline, Claude Desktop, Claude Code, VS Code native MCP, Codex and Antigravity, and leaves hand-written entries in those config files alone.
What you get
- Jira-helper — the largest of the bundled servers, covering issues (
get_issue_details,create_jira_ticket,update_jira_issue,transition_jira_issue,change_issue_assignee), search (search_jira_issues,validate_jql_query), links (create_issue_link,create_epic_story_link), worklogs and estimates (log_work,get_work_logs,get_time_tracking_info), attachments (upload_file_to_jira,list_issue_attachments) and Confluence pages (list_confluence_spaces,get_confluence_page,search_confluence_pages,create_confluence_page,update_confluence_page), across multiple Jira instances - Worldcontext — the facts a model does not have:
get_current_datetime,get_stock_quote,get_stock_market_overview,get_news_headlines,get_latest_tool_versions,get_python_package_versionand a combinedget_context_summary - Loadbearing-youtube —
analyze_videoextracts a transcript and surfaces the claims, decisions, tradeoffs and recommendations a video's conclusion actually rests on, with timestamps; long videos run as a background job you collect withget_analysis_result, andget_video_transcriptreturns the raw text - Mcpservercreator —
create_mcp_serverscaffolds a new server from a code snippet, withlist_installed_serversto see what is already there - A
templateserver to fork when you are writing your own, and amcp-manager sync --platformflag when you only want to update one client
Requirements
Per-server credentials, kept in ~/.config/mcp-manager/servers/<YOUR_SERVER_NAME>/config.yaml — jira-helper needs an Atlassian API token. Install uv, then uv tool install "git+https://github.com/dawsonlp/BaseMcpServer.git#subdirectory=utils/mcp_manager", then mcp-manager install <YOUR_SERVER_NAME> --source ./servers/<YOUR_SERVER_NAME> for each server you want. macOS and Linux are supported and tested; Windows is explicitly out of scope. Every server registers plain tool functions through the MCP Python SDK, so the template is a small file rather than a framework.
Setup effort
Follow the published steps — uv tool install "git+https://github.com/dawsonlp/BaseMcpServer.git#subdirectory=utils/mcp_manager"
USE CASES
Working a Jira ticket without leaving the editor
Read the issue in full, log work against it, and move it through its workflow once the change is done.
Getting a model to stop guessing today's date
Fetch the current date and time before anything that timestamps a file or reasons about deadlines.
Deciding whether a long video is worth watching
Extract the transcript and read back the claims and tradeoffs the conclusion depends on, with timestamps to jump to.
Installing several servers into several clients at once
Install each server into its own environment, then write the entries into every detected client with a single sync.
47 tools
Listed in project docs. Your client may show a different list.
get_issue_detailsget_full_issue_detailscreate_jira_ticketadd_comment_to_jira_tickettransition_jira_issueget_issue_transitionschange_issue_assigneelist_project_ticketsget_custom_field_mappingsgenerate_project_workflow_graphlist_jira_instancesupdate_jira_issuesearch_jira_issuesvalidate_jql_querycreate_issue_linkcreate_epic_story_linkget_issue_linkscreate_issue_with_linkslog_workget_work_logsget_time_tracking_infoupdate_time_estimatesupload_file_to_jiralist_issue_attachmentsdelete_issue_attachmentlist_confluence_spaceslist_confluence_pagesget_confluence_pagesearch_confluence_pagescreate_confluence_pageupdate_confluence_pageget_current_datetimeget_stock_market_overviewget_stock_quoteget_news_headlinesget_context_summaryget_latest_tool_versionsget_python_package_versionanalyze_videoget_analysis_resultlist_analysis_jobsget_video_transcriptlist_analysis_providershelpcreate_mcp_serverlist_installed_serversBEFORE YOU INSTALL
What to know first
Tools you get
47 tools named in the project's documentation.
Requires
- macOS or Linux (Windows is out of scope)
- uv
INSTALLATION
Connect your client
Server setup
# 1. One-time: install uv and mcp-manager
curl -LsSf https://astral.sh/uv/install.sh | sh
uv tool install "git+https://github.com/dawsonlp/BaseMcpServer.git#subdirectory=utils/mcp_manager"
uv tool update-shell
# 2. Get the repository: --source points at its servers/ folder
git clone https://github.com/dawsonlp/BaseMcpServer.git
cd BaseMcpServer
# 3. Install whichever servers you want
mcp-manager install jira-helper --source ./servers/jira-helper
mcp-manager install worldcontext --source ./servers/worldcontext
mcp-manager install mcpservercreator --source ./servers/mcpservercreator
mcp-manager install loadbearing-youtube --source ./servers/loadbearing-youtube
# 4. Put credentials in each server's config file (jira-helper needs an Atlassian API token)
$EDITOR ~/.config/mcp-manager/servers/jira-helper/config.yaml
# 5. Write the entries into every detected client (Cline, Claude Desktop, Claude Code, VS Code, Codex, Antigravity)
# or one client only: mcp-manager sync --platform cline
mcp-manager sync