@crypto512/jicon-mcp 0.1.0 → 0.2.0

package/CLAUDE.md

@@ -1,8 +1,8 @@
-# Jira and Confluence MCP Server
+# Jira, Confluence, and Tempo MCP Server
 
 ## Overview
 
-A Model Context Protocol (MCP) server that provides seamless integration with Atlassian Jira and Confluence Server/Data Center instances. This server enables AI assistants to interact with Jira issues, projects, boards, and Confluence pages, spaces, and content through a comprehensive set of tools.
+A Model Context Protocol (MCP) server that provides seamless integration with Atlassian Jira, Confluence, and Tempo Server/Data Center instances. This server enables AI assistants to interact with Jira issues, projects, boards, Confluence pages, spaces, content, and Tempo time tracking through a comprehensive set of tools.
 
 ## Features
 
@@ -22,6 +22,13 @@ A Model Context Protocol (MCP) server that provides seamless integration with At
 - **Attachments**: Upload and retrieve file attachments
 - **Comments**: Add and view page comments
 
+### Tempo Integration
+- **Time Tracking**: Log, view, and manage work time
+- **Worklog Management**: Create, update, and delete worklogs
+- **Team Tracking**: Access team worklogs and time tracking data
+- **Account Management**: View and manage Tempo accounts
+- **User Info**: Retrieve user time tracking information
+
 ## Installation
 
 ```bash

package/README.md

@@ -17,10 +17,11 @@ npm install -g @crypto512/jicon-mcp
 
 ## What is Jicon?
 
-Jicon is an MCP server that enables AI assistants like Claude to interact with your Jira and Confluence instances. It provides 28 powerful tools for:
+Jicon is an MCP server that enables AI assistants like Claude to interact with your Jira, Confluence, and Tempo instances. It provides 39 powerful tools for:
 
 - 🎫 **Jira**: Issue management, searching, project operations, Agile boards, sprints
 - 📄 **Confluence**: Page management, content search, spaces, attachments, comments
+- ⏱️ **Tempo**: Time tracking, worklog management, accounts, and teams
 
 ## Features at a Glance
 
@@ -38,6 +39,13 @@ Jicon is an MCP server that enables AI assistants like Claude to interact with y
 - Manage attachments
 - Add and view comments
 
+### Tempo (11 Tools)
+- Log and manage work time
+- View and update worklogs
+- Access accounts and teams
+- Retrieve team worklogs
+- Get user time tracking info
+
 ## Configuration
 
 ### Configuration with `.jicon.json` (Recommended)
@@ -79,13 +87,13 @@ Control which tools are allowed to execute:
 ```json
 { "permissions": { "mode": "full" } }
 ```
-All 28 tools are available.
+All 39 tools are available.
 
 #### 2. **Read-Only Mode**
 ```json
 { "permissions": { "mode": "readonly" } }
 ```
-Only read operations (18 tools: 10 Jira + 8 Confluence).
+Only read operations (26 tools: 10 Jira + 8 Confluence + 8 Tempo).
 
 #### 3. **Custom Mode** with Virtual Actions
 
@@ -98,23 +106,26 @@ Simplify configuration with **virtual actions** that group related tools:
 - `confluence_read` - All 8 Confluence read tools
 - `confluence_write` - All 5 Confluence write tools
 - `confluence_all` - All 13 Confluence tools
+- `tempo_read` - All 8 Tempo read tools
+- `tempo_write` - All 3 Tempo write tools
+- `tempo_all` - All 11 Tempo tools
 
-**Example: Read-only access to both services**
+**Example: Read-only access to all services**
 ```json
 {
   "permissions": {
     "mode": "custom",
-    "whitelist": ["jira_read", "confluence_read"]
+    "whitelist": ["jira_read", "confluence_read", "tempo_read"]
   }
 }
 ```
 
-**Example: Full Jira + Confluence read-only**
+**Example: Full Jira + Confluence read-only + Tempo time tracking**
 ```json
 {
   "permissions": {
     "mode": "custom",
-    "whitelist": ["jira_all", "confluence_read"]
+    "whitelist": ["jira_all", "confluence_read", "tempo_all"]
   }
 }
 ```
@@ -128,7 +139,9 @@ Simplify configuration with **virtual actions** that group related tools:
       "jira_search_issues",
       "jira_get_issue",
       "jira_create_issue",
-      "confluence_get_page"
+      "confluence_get_page",
+      "tempo_log_work",
+      "tempo_get_worklogs"
     ]
   }
 }
@@ -180,6 +193,9 @@ Once configured, you can ask Claude to:
 - *"Show me the current sprint's progress"*
 - *"Update the API documentation page in Confluence"*
 - *"Search for pages about authentication in the DOCS space"*
+- *"Log 4 hours of work on PROJ-123 for today"*
+- *"Show me my worklogs for this week"*
+- *"Get team worklogs for the development team"*
 
 ## Documentation
 
@@ -209,11 +225,20 @@ Once configured, you can ask Claude to:
 | **Collaboration** | `confluence_add_comment`, `confluence_get_comments` |
 | **Attachments** | `confluence_upload_attachment`, `confluence_list_attachments` |
 
+### Tempo Tools
+| Category | Tools |
+|----------|-------|
+| **Worklog Management** | `tempo_get_worklogs`, `tempo_get_worklog`, `tempo_log_work`, `tempo_update_worklog`, `tempo_delete_worklog` |
+| **Team Tracking** | `tempo_get_team_worklogs`, `tempo_get_teams`, `tempo_get_team` |
+| **Accounts** | `tempo_get_accounts`, `tempo_get_account` |
+| **User Info** | `tempo_get_user_info` |
+
 ## Requirements
 
 - Node.js 18 or higher
 - Jira Server/Data Center or Jira Cloud instance
-- Confluence Server/Data Center or Confluence Cloud instance
+- Confluence Server/Data Center or Confluence Cloud instance (optional)
+- Tempo Timesheets instance (optional)
 - Valid API tokens or Personal Access Tokens
 
 ## Authentication
@@ -241,7 +266,7 @@ Generate a Personal Access Token (PAT):
 ## Development Status
 
 - ✅ **Specification Complete** - Functional spec and tool list defined
-- ✅ **Implementation Complete** - All 28 tools implemented
+- ✅ **Implementation Complete** - All 39 tools implemented
 - ✅ **Testing** - 86 tests passing
 - ✅ **Configuration System** - Flexible .jicon.json with permissions
 - 📦 **Publishing** - Ready for npm publish
@@ -250,13 +275,14 @@ Generate a Personal Access Token (PAT):
 
 ### Phase 1: Core Implementation ✅ **COMPLETED**
 - ✅ Project setup and structure
-- ✅ Jira API client implementation (310 lines, 15 tools)
-- ✅ Confluence API client implementation (281 lines, 13 tools)
-- ✅ MCP server implementation (179 lines)
+- ✅ Jira API client implementation (15 tools)
+- ✅ Confluence API client implementation (13 tools)
+- ✅ Tempo API client implementation (11 tools)
+- ✅ MCP server implementation
 - ✅ Basic testing (86 tests, 100% pass rate)
 - ✅ Configuration system (.jicon.json with hierarchy)
 - ✅ Permission system (full, readonly, custom modes)
-- ✅ Virtual actions (jira_read, jira_all, confluence_read, etc.)
+- ✅ Virtual actions (jira_read, jira_all, confluence_read, tempo_all, etc.)
 - ✅ Development and contributing guides
 
 ### Phase 2: Enhancement (In Progress)
@@ -297,4 +323,4 @@ MIT License - see [LICENSE](LICENSE) file for details.
 
 ---
 
-**Made with ❤️ for developers who work with Jira and Confluence**
+**Made with ❤️ for developers who work with Jira, Confluence, and Tempo**

package/TOOL_LIST.md

@@ -1,13 +1,16 @@
-# Jira & Confluence MCP Server - Tool List
+# Jira, Confluence & Tempo MCP Server - Tool List
 
 ## Overview
-This document provides a comprehensive reference of all available tools in the Jira and Confluence MCP server.
+This document provides a comprehensive reference of all available tools in the Jira, Confluence, and Tempo MCP server.
 
 ## Summary
 
-**Total Tools**: 28
+**Total Tools**: 39
 - **Jira Tools**: 15
 - **Confluence Tools**: 13
+- **Tempo Tools**: 11
+
+**Note**: Detailed documentation for Tempo tools is available in the source code at `src/tempo/tools.ts`. Tempo provides time tracking, worklog management, team tracking, and account management capabilities.
 
 ---
 

package/dist/index.d.ts

@@ -1,6 +1,6 @@
 #!/usr/bin/env node
 /**
- * Jira and Confluence MCP Server
+ * Jira, Confluence, and Tempo MCP Server
  */
 export {};
 //# sourceMappingURL=index.d.ts.map

package/dist/index.js

@@ -1,6 +1,6 @@
 #!/usr/bin/env node
 /**
- * Jira and Confluence MCP Server
+ * Jira, Confluence, and Tempo MCP Server
  */
 import { Server } from "@modelcontextprotocol/sdk/server/index.js";
 import { StdioServerTransport } from "@modelcontextprotocol/sdk/server/stdio.js";

package/dist/types.d.ts

@@ -1,5 +1,5 @@
 /**
- * Shared types for Jira and Confluence MCP Server
+ * Shared types for Jira, Confluence, and Tempo MCP Server
  */
 export interface ApiConfig {
     url: string;

package/dist/types.js

@@ -1,5 +1,5 @@
 /**
- * Shared types for Jira and Confluence MCP Server
+ * Shared types for Jira, Confluence, and Tempo MCP Server
  */
 export {};
 // Note: This type is compatible with CallToolResult from @modelcontextprotocol/sdk

package/package.json

@@ -1,7 +1,7 @@
 {
   "name": "@crypto512/jicon-mcp",
-  "version": "0.1.0",
-  "description": "Model Context Protocol server for Jira and Confluence integration",
+  "version": "0.2.0",
+  "description": "Model Context Protocol server for Jira, Confluence, and Tempo integration",
   "main": "dist/index.js",
   "type": "module",
   "bin": {