Claude Code Plugins

A collection of zero-dependency plugins for Claude Code that provide direct integrations with popular Atlassian tools using OpenAPI specifications.

Why These Plugins?

• Zero Dependencies: Only Node.js built-in modules (no npm packages!)
• No MCP Overhead: Direct REST API calls without Model Context Protocol
• OpenAPI Based: Standards-compliant implementations following official specs
• Production Ready: Comprehensive error handling and documentation
• Easy to Use: Simple slash commands in Claude Code
• Easy to Extend: Clean architecture makes adding features straightforward
• Seamless Workflow: Agents and hooks integrate into your development process

Workflow Integration

These plugins work in three modes to fit your workflow:

1. Manual Commands - Use slash commands when you need them (works immediately, no setup)
2. Agent-Assisted - AI proactively suggests Jira/Confluence actions based on context (recommended)
3. Automated Hooks - Triggers remind you to update Jira/Confluence based on your actions (advanced)

See WORKFLOW.md for complete integration guide with examples!

Quick Example: Agent Mode

You: [Write new authentication code]

Claude (Jira Assistant): "I see you've implemented authentication.
Would you like me to create a Jira issue to track this?"

You: "Yes"

Claude: [Creates PROJ-456 automatically]

The plugins include intelligent agents:

• Jira Assistant - Tracks work and suggests issue updates
• Documentation Assistant - Reminds you to update Confluence when code changes

Available Plugins

🎯 Jira Plugin

Complete Jira integration for issue tracking and project management.

Features:

• Create, view, update, and transition issues
• Search issues with JQL (Jira Query Language)
• Add comments to issues
• View your assigned issues
• Full issue lifecycle management

Commands:

• /jira-create - Create new issue
• /jira-get - View issue details
• /jira-search - Search with JQL
• /jira-my-issues - Your assigned issues
• /jira-update - Update issue fields
• /jira-comment - Add comments
• /jira-transition - Change issue status

→ Full Jira Plugin Documentation

📚 Confluence Plugin

Complete Confluence integration for wiki and documentation management.

Features:

• Create, view, update, and delete pages
• Search pages by space or title
• List all spaces
• Full page lifecycle management
• ADF (Atlassian Document Format) support

Commands:

• /confluence-create-page - Create new page
• /confluence-get-page - View page details
• /confluence-search-pages - Search pages
• /confluence-list-spaces - List all spaces
• /confluence-update-page - Update existing page
• /confluence-delete-page - Delete page

→ Full Confluence Plugin Documentation

Quick Start

Installation

1. Install a plugin from within Claude Code:

   /plugin install https://github.com/sethdford/claude-plugins/jira-plugin
   /plugin install https://github.com/sethdford/claude-plugins/confluence-plugin
   

2. Get your Atlassian API token:

   • Visit https://id.atlassian.com/manage-profile/security/api-tokens
   • Click "Create API token"
   • Copy the generated token

3. Configure credentials in .claude/settings.json:

   {
     "env": {
       "JIRA_HOST": "your-domain.atlassian.net",
       "JIRA_EMAIL": "your-email@example.com",
       "JIRA_API_TOKEN": "your-api-token",
   
       "CONFLUENCE_HOST": "your-domain.atlassian.net",
       "CONFLUENCE_EMAIL": "your-email@example.com",
       "CONFLUENCE_API_TOKEN": "your-api-token"
     }
   }
   

4. Start using the plugins:

   /jira-my-issues
   /confluence-list-spaces
   

Architecture

Both plugins share the same minimalist architecture:

plugin/
├── .claude-plugin/
│   ├── commands/           # Slash command definitions
│   ├── scripts/            # Direct API integration scripts
│   │   └── *-client.js    # Zero-dependency HTTP client
│   └── plugin.json         # Plugin manifest
├── package.json            # No dependencies!
├── *-openapi-*.json       # OpenAPI spec (reference)
└── README.md

Key Design Principles

1. Zero Dependencies: Only Node.js built-in https module
2. Direct API Calls: No abstraction layers or third-party libraries
3. OpenAPI Compliance: Follow official API specifications
4. Simple Commands: Intuitive slash commands for all operations
5. Clear Error Messages: Helpful feedback when things go wrong

Why No MCP?

Model Context Protocol (MCP) adds unnecessary complexity for simple API integrations:

• Extra Protocol Layer: MCP requires additional translation
• More Points of Failure: More components means more can break
• Performance Overhead: Protocol transla

...