GalaxyMCP Server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| JIRA_EMAIL | No | JIRA account email | |
| JIRA_TOKEN | No | JIRA API token | |
| GALAXY_USER | No | User identity for persona attribution | |
| JIRA_BASE_URL | No | JIRA instance URL (e.g., https://your-company.atlassian.net) | |
| JIRA_SUB_COMPONENT | No | Default component for created tickets (optional) | |
| GALAXY_PERSONAS_DIR | No | Custom personas directory (default: ./personas) |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| list_personasB | List all available personas in GalaxyMCP |
| activate_personaA | Activate a specific persona by name or filename |
| get_active_personaB | Get information about the currently active persona |
| deactivate_personaA | Deactivate the current persona |
| get_persona_detailsB | Get detailed information about a specific persona |
| reload_personasB | Reload all personas from the personas directory |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 6 tools
Each tool has a distinct purpose: activate, deactivate, get active, get details, list, and reload personas. No overlap or ambiguity.
All tool names follow a consistent verb_noun pattern in snake_case (e.g., activate_persona, list_personas), ensuring predictability.
With 6 tools focused on persona management, the set is well-scoped and neither too sparse nor excessive for the domain.
The tools cover core persona lifecycle operations (activate, deactivate, list, details) and include reload, but lack explicit create or delete functions, which may be handled externally.