GalaxyMCP Server
A Model Context Protocol server for AI persona management with JIRA integration, enabling personality switching and ticket operations.
README
GalaxyMCP Server
🌌 A Model Context Protocol (MCP) server for AI persona management with Galaxy theme. Built with TypeScript and designed for seamless integration with AI assistants like Claude and Augment AI.
Features
- 🎭 Persona Management: Activate different AI personalities for specialized tasks
- 🛠️ 6 MCP Tools: Complete persona lifecycle management
- 🎫 JIRA Integration: Full JIRA API support with 8 additional tools for ticket management
- 📝 Markdown-Based Personas: Easy-to-edit persona definitions with YAML frontmatter
- 🔧 TypeScript: Type-safe development with modern ES modules
- 🌟 Galaxy Theme: Space-themed indicators and branding
- 🚀 Simplified Architecture: Streamlined codebase for easy understanding and extension
- 📦 Self-Contained: All persona logic in a single main file for clarity
Available Tools
Persona Management Tools
| Tool | Description |
|---|---|
list_personas |
List all available personas with details |
activate_persona |
Activate a specific persona by name or filename |
get_active_persona |
Get currently active persona information |
deactivate_persona |
Return to default mode |
get_persona_details |
View detailed persona information and content |
reload_personas |
Refresh personas from filesystem |
JIRA Integration Tools (Optional)
Available when JIRA is configured with required environment variables
| Tool | Description |
|---|---|
get_jira_ticket |
Retrieve JIRA ticket information by ticket key |
create_jira_ticket |
Create a new JIRA ticket (story) with workspace intelligence |
create_jira_epic |
Create a new JIRA epic for organizing multiple related stories |
update_jira_ticket |
Update an existing JIRA ticket with new information |
add_jira_comment |
Add a comment to an existing JIRA ticket |
link_jira_story_to_parent |
Link a JIRA story to its parent ticket |
link_jira_epic_to_parent |
Link a JIRA epic to its parent ticket |
attach_file_to_jira |
Attach a file to an existing JIRA ticket |
Built-in Personas
- Technical Analyst - Systematic problem-solver for deep technical analysis and architectural decisions
Prerequisites
- Node.js: v20.0.0 or higher
- npm: v10.0.0 or higher
- TypeScript: v5.0.0 or higher
Quick Start
1. Installation
# Navigate to the project directory
cd /Users/vkakkar/Documents/self/Projects/AI_MCP/galaxymcp-server
# Install dependencies
npm install
# Build the TypeScript code
npm run build
2. Environment Setup (Optional)
# Set user identity for persona attribution
export GALAXY_USER="your-username"
# Custom personas directory (optional)
export GALAXY_PERSONAS_DIR="/path/to/custom/personas"
# JIRA Integration (optional)
export JIRA_BASE_URL="https://your-company.atlassian.net"
export JIRA_EMAIL="your-email@company.com"
export JIRA_TOKEN="your-jira-api-token"
export JIRA_SUB_COMPONENT="Galaxy-Core"
JIRA Configuration
To enable JIRA integration, you need to set up the following environment variables:
- JIRA_BASE_URL: Your JIRA instance URL (e.g.,
https://company.atlassian.net) - JIRA_EMAIL: Your JIRA account email
- JIRA_TOKEN: Your JIRA API token (How to create)
- JIRA_SUB_COMPONENT (optional): Default component for created tickets
Creating a JIRA API Token:
- Go to Atlassian Account Settings
- Click "Create API token"
- Give it a label (e.g., "GalaxyMCP")
- Copy the generated token
3. Test the Server
# Start the server
npm start
# Or with environment variables
GALAXY_USER="vaibhavkkk" npm start
Expected Output:
GalaxyMCP server running on stdio
Loaded persona: Technical Analyst (technical-analyst_20250714-130000_galaxymcp)
Integration with Augment AI
Step 1: Get Absolute Path
# Get the absolute path to your GalaxyMCP installation
cd /Users/vkakkar/Documents/self/Projects/AI_MCP/galaxymcp-server
pwd
# Copy this path: /Users/vkakkar/Documents/self/Projects/AI_MCP/galaxymcp-server
Step 2: Configure MCP Server in Augment AI
- Open IntelliJ IDEA
- Go to Preferences (⌘ + ,)
- Navigate to Tools → Augment AI → MCP Servers (or similar)
- Add new MCP server with these settings:
Configuration:
{
"mcpServers": {
"galaxymcp": {
"command": "node",
"args": ["/Users/vkakkar/Documents/self/Projects/AI_MCP/galaxymcp-server/dist/index.js"],
"env": {
"GALAXY_USER": "vaibhavkkk",
"JIRA_BASE_URL": "https://your-company.atlassian.net",
"JIRA_EMAIL": "your-email@company.com",
"JIRA_TOKEN": "your-jira-api-token",
"JIRA_SUB_COMPONENT": "Galaxy-Core"
}
}
}
}
Note: JIRA environment variables are optional. If not provided, only persona management tools will be available.
Step 3: Restart and Test
- Restart IntelliJ IDEA completely
- Open Augment AI panel
- Look for GalaxyMCP tools in available tools
- Test with:
list_personas
Usage Examples
Basic Persona Management
# List all available personas
list_personas
# Activate the Technical Analyst persona
activate_persona "Technical Analyst"
# Get details about current persona
get_active_persona
# View full persona details
get_persona_details "Technical Analyst"
# Deactivate persona
deactivate_persona
Working with Technical Analyst
Once activated, the Technical Analyst persona will:
- Provide systematic technical analysis
- Focus on architectural decisions
- Consider scalability and performance
- Offer detailed debugging approaches
- Suggest concrete implementation steps
JIRA Integration Examples
Available when JIRA is configured
# Get ticket information
get_jira_ticket "ENG-12345"
# Create a new story
create_jira_ticket {
"summary": "Implement user authentication",
"description": "Add JWT-based authentication to the API",
"issue_type": "Story",
"labels": ["backend", "security"]
}
# Create an epic
create_jira_epic {
"summary": "User Management System",
"description": "Complete user management functionality",
"labels": ["epic", "user-management"]
}
# Add a comment
add_jira_comment {
"ticket_key": "ENG-12345",
"comment_text": "Implementation completed and ready for review"
}
# Link a story to an epic
link_jira_story_to_parent {
"story_key": "ENG-12346",
"parent_key": "ENG-12345",
"link_type": "Blocks"
}
Project Structure
galaxymcp-server/
├── src/
│ ├── index.ts # Main MCP server with all logic
│ ├── types/
│ │ ├── persona.ts # Persona type definitions
│ │ ├── mcp.ts # MCP-related types
│ │ └── index.ts # Type exports
│ ├── persona/
│ │ └── PersonaManager.ts # Persona loading and management (unused in current impl)
│ └── utils/
│ └── filesystem.ts # Utility functions (unused in current impl)
├── personas/
│ └── technical-analyst.md # Technical Analyst persona
├── dist/ # Compiled JavaScript (auto-generated)
├── package.json # Project configuration
├── tsconfig.json # TypeScript configuration
├── README.md # This file
├── LICENSE # MIT License
└── .gitignore # Git ignore rules
Note: The current implementation uses a simplified architecture where all logic is contained in src/index.ts for clarity and ease of understanding.
Development
Available Scripts
npm run build # Compile TypeScript
npm run start # Run the server
npm run dev # Watch mode for development
npm run clean # Remove compiled files
npm run rebuild # Clean and rebuild
npm run setup # Install deps and build
Adding New Personas
- Create a new
.mdfile in thepersonas/directory - Follow the YAML frontmatter format:
---
name: "Your Persona Name"
description: "Brief description"
triggers: ["keyword1", "keyword2"]
version: "1.0"
author: "your-username"
category: "professional"
unique_id: "your-persona_20250714-130000_your-username"
---
# Your Persona Name
Your persona instructions go here...
- Reload personas:
reload_personas
Troubleshooting
Common Issues
"Cannot find module" errors:
npm install
npm run build
Personas not loading:
# Check personas directory exists
ls -la personas/
# Reload personas
reload_personas
Augment AI doesn't see tools:
- Restart IntelliJ completely
- Verify absolute paths in MCP configuration
- Check Augment AI plugin version supports MCP
Debug Mode
# Run with debug output
DEBUG=galaxymcp:* npm start
# Check server compilation
node --version # Should be v20+
npm run build # Should complete without errors
Environment Variables
| Variable | Description | Default |
|---|---|---|
GALAXY_USER |
User identity for persona attribution | null |
GALAXY_PERSONAS_DIR |
Custom personas directory | ./personas |
Architecture Notes
This implementation uses a simplified architecture compared to DollhouseMCP:
- Single File Logic: All MCP server logic is in
src/index.ts - Inline Persona Management: Persona loading and management is built into the main server class
- Direct Tool Handling: Tools are handled directly in the main server without separate tool registry
- Simplified Types: Minimal type definitions for clarity
This approach makes the codebase easier to understand and modify while maintaining full MCP compatibility.
License
MIT License - see LICENSE file for details.
Contributing
- Fork the repository
- Create a feature branch
- Make your changes
- Test thoroughly
- Submit a pull request
🌌 Transform your AI interactions with the power of Galaxy personas!
推荐服务器
Baidu Map
百度地图核心API现已全面兼容MCP协议,是国内首家兼容MCP协议的地图服务商。
Playwright MCP Server
一个模型上下文协议服务器,它使大型语言模型能够通过结构化的可访问性快照与网页进行交互,而无需视觉模型或屏幕截图。
Magic Component Platform (MCP)
一个由人工智能驱动的工具,可以从自然语言描述生成现代化的用户界面组件,并与流行的集成开发环境(IDE)集成,从而简化用户界面开发流程。
Audiense Insights MCP Server
通过模型上下文协议启用与 Audiense Insights 账户的交互,从而促进营销洞察和受众数据的提取和分析,包括人口统计信息、行为和影响者互动。
VeyraX
一个单一的 MCP 工具,连接你所有喜爱的工具:Gmail、日历以及其他 40 多个工具。
graphlit-mcp-server
模型上下文协议 (MCP) 服务器实现了 MCP 客户端与 Graphlit 服务之间的集成。 除了网络爬取之外,还可以将任何内容(从 Slack 到 Gmail 再到播客订阅源)导入到 Graphlit 项目中,然后从 MCP 客户端检索相关内容。
Kagi MCP Server
一个 MCP 服务器,集成了 Kagi 搜索功能和 Claude AI,使 Claude 能够在回答需要最新信息的问题时执行实时网络搜索。
e2b-mcp-server
使用 MCP 通过 e2b 运行代码。
Neon MCP Server
用于与 Neon 管理 API 和数据库交互的 MCP 服务器
Exa MCP Server
模型上下文协议(MCP)服务器允许像 Claude 这样的 AI 助手使用 Exa AI 搜索 API 进行网络搜索。这种设置允许 AI 模型以安全和受控的方式获取实时的网络信息。