I’ve been publishing Model Context Protocol (MCP) packages so AI coding assistants can talk to the tools teams already use — with OAuth where it matters, and launchers that stay out of your way.
Below are the canonical npm and GitHub URLs. Use these when you install, star, or cite the work.
Packages
Jira (OAuth-focused)
- npm: jira-mcp-oauth
- GitHub: Wasim-Shaikh25/jira-mcp-auth
Jira (scoped package)
- npm: @svasimahmed283/jira-mcp- GitHub: Wasim-Shaikh25/jira-mcp
Splunk
Confluence
- npm: @svasimahmed283/confluence-mcp- GitHub: Wasim-Shaikh25/confluence-mcp
GitHub Enterprise launcher
SonarQube launcher
Why MCP launchers matter
Enterprise tools rarely fit a one-line npx forever. These packages aim to make auth, config, and process launch predictable for Cursor and other MCP hosts — so you spend less time wiring JSON and more time asking useful questions of Jira, Confluence, Splunk, or SonarQube.
Also: CaseMap (legal research)
Separate from MCP: CaseMap produces source-grounded legal case reports with verbatim quotes and page citations.
→ Product: https://casemap.ecocodes.in
(No CaseMap source-repo link in this post — the product URL is the official share link.)
Feedback
Issues and PRs on the GitHub repos above (MCP only) are welcome. If a launcher fails on your MCP host, open an issue with host name + error snippet.
— Vasim Ahmed Shaikh
Top comments (0)