Skip to main content
Glama
Helios-9 MCP Server

Helios-9 MCP Server

by jakedx6

Helios-9 MCP Server

An AI-native Model Context Protocol (MCP) server that provides comprehensive project management context to AI agents. Built for seamless integration with Claude, OpenAI, and other AI systems via the Helios-9 API.

πŸ“Œ Current Status

Stability: Ready for Core Features
Active Tools: 21 (Projects, Initiatives, Tasks, Documents - full hierarchy support)
API Integration: βœ… Fully integrated with Helios-9 SaaS API

Related MCP server: Planning System MCP Server

🌟 Features

Core Capabilities

  • Project Management: Create, read, update projects with full context

  • Task Operations: Kanban boards, task creation, status tracking

  • Document Management: Markdown documents with frontmatter metadata

  • AI Integration: Structured metadata for optimal AI collaboration

  • Real-time Context: Live project statistics and activity feeds

MCP Protocol Support

  • Tools: 21 tools for projects, initiatives, tasks, and documents

  • Resources: Dynamic project and document resources

  • Prompts: 9 AI-optimized prompt templates for project workflows

AI-First Design

  • Frontmatter Support: YAML metadata for AI instructions

  • Link Analysis: Internal document linking with [[document-name]] syntax

  • Basic Search: Keyword search across projects, tasks, and documents

  • Semantic Search: Coming soon with Supabase pgvector integration

πŸš€ Quick Start

Prerequisites

  • Node.js 16+

  • Access to Helios-9 main application with API key generation

  • MCP-compatible AI client (Claude Desktop, OpenAI, etc.)

Installation Options

npx -y helios9-mcp-server@latest --api-key YOUR_HELIOS9_API_KEY

Option 2: Clone and build locally

  1. Install dependencies:

    npm install
  2. Configure environment:

    cp .env.example .env
    # Edit .env with your Helios-9 API configuration
  3. Build the server:

    npm run build
  4. Start the server:

    npm start

Environment Variables

# Required - Helios-9 API Configuration
HELIOS_API_URL=https://www.helios9.app
HELIOS_API_KEY=your_generated_api_key

# Optional
LOG_LEVEL=info
NODE_ENV=development

πŸ”‘ API Key Generation

From Helios-9 Main Application

  1. Login to your Helios-9 application

  2. Navigate to Settings > API Keys

  3. Click "Generate New API Key"

  4. Copy the generated key (it will only be shown once)

  5. Set permissions for the key (read/write access to projects, tasks, documents)

  6. Add the key to your MCP server environment

API Key Permissions

Your API key controls access to:

  • Projects: Create, read, update, delete projects

  • Tasks: Manage tasks within your projects

  • Documents: Create and manage project documentation

  • Analytics: Access project insights and metrics

πŸ“‹ Available Tools

βœ… Project Tools

  • list_projects - List all projects with filtering

  • get_project - Get detailed project information

  • create_project - Create new project

  • update_project - Update existing project

βœ… Task Tools

  • list_tasks - List tasks with filtering

  • get_task - Get specific task details

  • create_task - Create new task

  • update_task - Update task status/details

βœ… Document Tools

  • list_documents - List documents with filtering

  • get_document - Get specific document

  • create_document - Create markdown document (requires project_id)

  • update_document - Update document content

Note: All tools require proper API key authentication and respect user-level data isolation.

🚧 Coming Soon

  • Semantic search across all content

  • Task dependencies and workflows

  • AI conversation tracking

  • Advanced analytics and insights

  • Document collaboration features

πŸ”— Resources & Prompts

Available Resources (24 total)

Projects: /projects, /project/{id}/context, /project/{id}/health, /project/{id}/timeline
Initiatives: /initiatives, /initiatives?project_id={id}, /initiative/{id}, /initiative/{id}/context
Tasks: /tasks, /tasks?project_id={id}, /tasks?initiative_id={id}, /task/{id}
Documents: /documents, /documents?project_id={id}, /document/{id}
Workspace: /workspace/overview, /workspace/analytics
Search: /search?q={query}, /search/semantic?q={query}
Conversations: /conversations?project_id={id}, /conversation/{id}
Workflows: /workflows, /workflow/{id}

Available Prompts

Planning & Strategy:

  • project_planning - Generate full project plans with initiatives

  • initiative_strategy - Strategic planning for initiatives

  • task_breakdown - Break features into actionable tasks

  • sprint_planning - Plan sprints with current context

Analysis & Review:

  • project_health_check - Analyze project health

  • document_review - Review and improve documentation

  • daily_standup - Generate standup reports

  • project_kickoff - Initial project structuring

Special Features:

  • helios9_personality - HELIOS-9's sardonic AI insights

πŸ”§ Integration Examples

Claude Desktop Configuration

Add to your claude_desktop_config.json:

{
  "mcpServers": {
    "helios9": {
      "command": "npx",
      "args": ["-y", "helios9-mcp-server@latest"],
      "env": {
        "HELIOS_API_URL": "https://helios9.app",
        "HELIOS_API_KEY": "your_generated_api_key"
      }
    }
  }
}

Option 2: Using local installation

{
  "mcpServers": {
    "helios9": {
      "command": "node",
      "args": ["/path/to/helios9-MCP-Server/dist/index.js"],
      "env": {
        "HELIOS_API_URL": "https://helios9.app",
        "HELIOS_API_KEY": "your_generated_api_key"
      }
    }
  }
}

Cline/Continue Integration

{
  "mcpServers": {
    "helios9": {
      "command": "node",
      "args": ["/path/to/helios9-MCP-Server/dist/index.js"],
      "env": {
        "HELIOS_API_URL": "https://www.helios9.app", 
        "HELIOS_API_KEY": "your_generated_api_key"
      }
    }
  }
}

OpenAI Integration

from mcp import MCPClient
import os

# Set environment variables
os.environ["HELIOS_API_URL"] = "https://www.helios9.app"
os.environ["HELIOS_API_KEY"] = "your_generated_api_key"

client = MCPClient()
client.connect_stdio("node", ["/path/to/dist/index.js"])

# List projects
projects = client.call_tool("list_projects", {})

# Create task
task = client.call_tool("create_task", {
    "project_id": "uuid",
    "title": "Implement user authentication",
    "priority": "high"
})

πŸ“Š Data Models

Project

interface Project {
  id: string
  user_id: string
  name: string
  description?: string
  status: 'active' | 'completed' | 'archived'
  created_at: string
  updated_at: string
}

Task

interface Task {
  id: string
  title: string
  description?: string
  status: 'todo' | 'in_progress' | 'done'
  priority: 'low' | 'medium' | 'high'
  project_id: string
  assignee_id?: string
  due_date?: string
  created_at: string
  updated_at: string
  created_by: string
}

Document

interface Document {
  id: string
  title: string
  content: string  // Markdown with frontmatter
  document_type: 'requirement' | 'design' | 'technical' | 'meeting_notes' | 'note' | 'other'
  project_id: string  // Required
  created_at: string
  updated_at: string
  created_by: string
}

πŸ”’ Security

Authentication

  • API Key Authentication: Generated from your Helios-9 application

  • Secure Storage: API keys are securely stored and managed in Helios-9

  • User Context: All operations are performed in the context of the API key owner

Data Access

  • User Isolation: API enforces user-level data access controls

  • Permission-based: API keys can have granular permissions

  • Audit Logging: All API calls are logged for security and debugging

Rate Limiting

  • API-level: Rate limiting is enforced by the Helios-9 API

  • Per-key Limits: Different limits can be set per API key

  • Configurable: Limits can be adjusted in the Helios-9 admin panel

πŸ—οΈ Architecture

API-First Design

β”Œβ”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”    β”Œβ”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”    β”Œβ”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”
β”‚   AI Client     │────│  Helios-9 MCP    │────│  Helios-9 API   β”‚
β”‚  (Claude, etc.) β”‚    β”‚     Server       β”‚    β”‚   Application   β”‚
β””β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”˜    β””β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”˜    β””β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”˜
                               β”‚                          β”‚
                       β”Œβ”€β”€β”€β”€β”€β”€β”€β–Όβ”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”              β”‚
                       β”‚  Authentication  β”‚              β”‚
                       β”‚   (API Key)      β”‚              β”‚
                       β””β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”˜              β”‚
                                                         β”‚
                                                β”Œβ”€β”€β”€β”€β”€β”€β”€β”€β–Όβ”€β”€β”€β”€β”€β”€β”€β”€β”
                                                β”‚    Database     β”‚
                                                β””β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”˜

Benefits of API Integration

  • Centralized Auth: Authentication handled by main application

  • Consistent Data: Single source of truth for all data

  • Security: API-level security controls and monitoring

  • Scalability: Can serve multiple MCP clients

  • Maintainability: Single codebase for data operations

πŸ“ˆ Monitoring

Health Checks

The server provides health information through logging:

  • API connection status

  • Authentication state

  • Tool execution metrics

  • Error rates and types

Metrics Available

  • Tool call frequency

  • Response times

  • Authentication success/failure

  • API endpoint usage patterns

πŸ› οΈ Troubleshooting

Common Issues

Authentication Failed

# Check API key validity
curl -H "Authorization: Bearer YOUR_API_KEY" https://www.helios9.app/api/auth/validate

Connection Issues

# Verify API URL is accessible
curl https://www.helios9.app/api/health

Permission Errors

  • Check API key permissions in Helios-9 admin panel

  • Ensure key has access to required resources (projects, tasks, documents)

Log Analysis

# Enable debug logging
LOG_LEVEL=debug npm start

# Look for API-specific errors
grep "API Error" logs/*.log

🀝 Contributing

Development Setup

  1. Fork the repository

  2. Create feature branch

  3. Make changes with tests

  4. Submit pull request

Code Style

  • TypeScript strict mode

  • ESLint configuration

  • Prettier formatting

  • Conventional commits

πŸ“ License

This project is part of the Helios-9 platform. See the main project LICENSE for details.

πŸ†˜ Support

Documentation

Community

  • GitHub Issues for bugs and features

  • Discussions for questions and ideas

  • Discord for real-time chat

πŸ“¦ Publishing to npm

For Maintainers

  1. Login to npm:

    npm login
    # Enter your npm credentials
  2. Verify package before publishing:

    # Dry run to see what will be published
    npm publish --dry-run
    
    # Check package size
    npm pack --dry-run
  3. Publish to npm:

    # For initial publish or updates
    npm publish
    
    # For beta/alpha releases
    npm publish --tag beta
  4. Verify publication:

    # Check if package is available
    npm view helios9-mcp-server
    
    # Test installation
    npx -y helios9-mcp-server@latest --help

Version Management

Update version before publishing:

# Patch release (1.0.0 -> 1.0.1)
npm version patch

# Minor release (1.0.0 -> 1.1.0)
npm version minor

# Major release (1.0.0 -> 2.0.0)
npm version major

Built with ❀️ for the AI-native future of project management

πŸš€ Roadmap

Coming Soon

  • Semantic Search: AI-powered search using OpenAI embeddings and Supabase pgvector

  • Task Dependencies: Link related tasks and track workflows

  • AI Conversations: Save and analyze AI agent interactions

  • Advanced Analytics: Project insights and productivity metrics

  • Bulk Operations: Update multiple items at once

  • Workflow Automation: Trigger-based task creation and updates

Future Vision

  • Multi-agent collaboration support

  • Custom tool creation framework

  • Integration with popular project management tools

  • Real-time collaboration features

Available Tools

65 tools
add_document_collaboratorC

Add a collaborator to a document with specific permissions

Inputs: user_id (required), document_id (required), notify, permission_level.

add_task_dependencyC

Add a dependency relationship between tasks

Inputs: task_id (required), depends_on_task_id (required), dependency_type.

analyze_conversationC

Analyze an AI conversation to extract insights, themes, and patterns

Inputs: conversation_id (required).

analyze_document_contentC

Perform advanced analysis on document content

Inputs: document_id (required), analysis_types, include_suggestions.

archive_projectB

Archive or unarchive a project

Inputs: project_id (required), reason, archive.

associate_document_with_initiativeA

Link an existing document to an initiative

Inputs: initiative_id (required), document_id (required).

bulk_document_operationsC

Perform bulk operations on multiple documents

Inputs: document_ids (required), operation (required), operation_data.

bulk_update_projectsB

Update multiple projects at once with common settings

Inputs: updates (required), project_ids (required), reason.

bulk_update_tasksC

Update multiple tasks at once

Inputs: updates (required), task_ids (required), cascade_dependencies.

create_documentB

Create a new document with markdown content and optional frontmatter metadata

Inputs: title (required), content (required), project_id (required), document_type (required), +1 more.

create_initiativeC

Create a new initiative

Inputs: name (required), objective (required), owner_id (required), project_ids (required), +7 more.

create_projectC

Create a new project with specified details

Inputs: name (required), status, description.

create_taskC

Create a new task in a project

Inputs: title (required), project_id (required), due_date, priority, +3 more.

create_task_workflowB

Create a workflow with multiple connected tasks

Inputs: tasks (required), project_id (required), workflow_name (required), auto_start.

create_trigger_automationC

Create automated workflows triggered by specific events

Inputs: automation_name (required), trigger_events (required), automated_actions (required), conditions, +1 more.

create_workflow_ruleC

Create an automation rule that triggers actions based on events

Inputs: name (required), trigger (required), actions (required), description, +2 more.

debug_environmentB

Debug tool to check MCP server environment and configuration

Inputs: no named parameters.

disassociate_document_from_initiativeA

Remove the link between a document and an initiative

Inputs: initiative_id (required), document_id (required).

duplicate_projectB

Create a copy of an existing project with customizable options

Inputs: new_name (required), source_project_id (required), reset_dates, new_owner_id, +2 more.

execute_workflow_ruleB

Manually execute a workflow rule for testing

Inputs: rule_id (required), test_data, dry_run.

extract_action_itemsA

Extract actionable items from a conversation and optionally create tasks

Inputs: conversation_id (required), auto_create_tasks.

generate_context_summaryC

Generate intelligent summary from aggregated context data

Inputs: context_data (required), summary_focus, target_audience.

generate_conversation_summaryC

Generate different types of summaries from a conversation

Inputs: conversation_id (required), summary_type.

generate_custom_reportC

Generate a custom analytics report with specified metrics and visualizations

Inputs: report_name (required), data_sources (required), metrics_config, output_format, +1 more.

generate_document_templateC

Generate a document template based on type and requirements

Inputs: template_type (required), ai_optimized, project_context, include_examples.

get_automation_analyticsC

Get analytics and performance data for workflow automations

Inputs: project_id, time_range, include_inactive.

get_conversationsB

Retrieve AI conversations for a project with optional filtering

Inputs: project_id (required), limit, conversation_type, related_to, +1 more.

get_documentB

Get a document by ID with basic information

Inputs: document_id (required).

get_document_collaborationA

Get collaboration history and current collaborators for a document

Inputs: document_id (required), time_range, include_activity.

get_document_contextB

Get document with full context including links, references, and AI metadata

Inputs: document_id (required).

get_enhanced_project_contextB

Get project context including all initiatives

Inputs: project_id (required).

get_initiativeC

Get detailed information about a specific initiative

Inputs: initiative_id (required).

get_initiative_contextC

Get rich context about an initiative for AI understanding

Inputs: initiative_id (required).

get_initiative_insightsC

Get AI-powered insights and recommendations for an initiative

Inputs: initiative_id (required).

get_projectC

Get detailed information about a specific project including tasks and documents

Inputs: project_id (required).

get_project_analyticsC

Get comprehensive analytics and insights for projects

Inputs: project_ids, time_range, metrics, include_predictions, +1 more.

get_project_contextA

Get comprehensive project context including statistics, recent activity, and team information for AI understanding

Inputs: project_id (required).

get_project_insightsC

Get deep analytics and insights for a specific project

Inputs: project_id (required), insight_types, include_recommendations.

get_project_timelineB

Get project timeline with milestones and key events

Inputs: project_id (required), time_range, include_completed.

get_search_analyticsB

Get analytics about search patterns and performance

Inputs: time_range, project_id, include_performance.

get_search_suggestionsC

Get intelligent search suggestions and autocomplete

Inputs: partial_query (required), suggestion_types, context_project_id, max_suggestions.

get_smart_contextC

Get intelligent context aggregation based on natural language query across projects, tasks, and documents

Inputs: query (required), project_id, context_types, max_results_per_type, +1 more.

get_taskB

Get a task by ID with full details

Inputs: task_id (required).

get_task_dependenciesB

Get all dependencies for a task or project

Inputs: task_id, project_id, include_transitive.

get_task_workflow_statusA

Get status and progress of a task workflow

Inputs: project_id (required), workflow_name (required).

get_team_productivityC

Analyze team productivity patterns and performance

Inputs: team_members, project_id, time_range, productivity_dimensions.

get_workspace_contextB

Get complete workspace hierarchy and insights

Inputs: no named parameters.

get_workspace_healthC

Get comprehensive workspace health metrics and indicators

Inputs: health_categories, alert_thresholds, include_recommendations.

get_workspace_overviewC

Get comprehensive overview of entire workspace with analytics and insights

Inputs: include_analytics, time_range, focus_areas.

list_documentsC

List documents with optional filtering by project or document type

Inputs: limit, search, project_id, document_type.

list_initiativesC

List all initiatives with optional filtering

Inputs: project_id, status, priority, search, +1 more.

list_projectsC

List all projects with optional filtering by status

Inputs: limit, search, status.

list_tasksC

List tasks with optional filtering by project, initiative, status, or assignee

Inputs: limit, search, status, project_id, +2 more.

list_workflow_rulesA

List all automation rules for a project or globally

Inputs: project_id, enabled_only.

prompt_to_projectC

Convert a natural language project description into structured project entities. In analyze mode, returns a template for the AI agent to fill. In create mode, executes the agent-provided plan.

Inputs: prompt (required), execution_mode (required), project_plan.

save_conversationB

Save an AI conversation with project context for future reference and analysis

Inputs: project_id (required), messages (required), title, context, +1 more.

search_documentsC

Search documents by content with advanced filtering and ranking

Inputs: query (required), limit, project_id, document_types, +1 more.

search_workspaceC

Search across all entity types with initiative awareness

Inputs: query (required), filters, limit.

update_documentC

Update an existing document with new content or metadata

Inputs: document_id (required), title, content, metadata, +1 more.

update_initiativeC

Update initiative details

Inputs: initiative_id (required), name, objective, description, +7 more.

update_projectB

Update an existing project with new information

Inputs: project_id (required), name, status, description.

update_taskC

Update an existing task with new information

Inputs: task_id (required), title, status, due_date, +4 more.

Tool Schema Changelog

Recent tool additions, removals, and schema changes observed during successful MCP inspections.

Loading tool schema changelog…

    TDQS

    C2.6/5.0

    Scored across 65 tools

    Disambiguation2/5

    The core CRUD tools are distinct, but there is heavy overlap among search, context, and analytics tools (universal_search vs semantic_search vs search_workspace; get_project_context vs get_enhanced_project_context vs get_project_insights). This makes it difficult for an agent to confidently choose the right tool for a given request.

    Naming Consistency4/5

    Most tools follow a clear snake_case verb_noun pattern like create_project, list_tasks, and update_document. However, a few outliers such as universal_search, debug_environment, bulk_document_operations, and prompt_to_project break the pattern, keeping it from being fully consistent.

    Tool Count1/5

    With 65 tools, the server far exceeds the range where a tool set remains navigable. Many tools appear to be near-duplicates in the search, context, and analytics categories, and the sheer count will overwhelm agents rather than improve capability.

    Completeness3/5

    Core CRUD is present for projects, tasks, documents, and initiatives, with additional workflow, conversation, and analytics features. However, lifecycle coverage is incomplete: there are no delete/archive operations for tasks, documents, or initiatives, no update/delete for workflow rules, and document collaborator management only supports adding collaborators.

    Maintenance

    ActivityInactive
    ResponsivenessNo recent community issues

    Related MCP Connectors

    Related MCP Servers

    • -
      license
      Not graded
      quality
      Not graded
      maintenance
      Enables AI assistants to create and manage development projects with structured backlogs, including tasks, requirements, and progress tracking. Provides a bridge between AI development assistants and project management workflows through standardized MCP tools.
      -
    • A
      license
      B
      quality
      C
      maintenance
      Enables AI agents to create, manage, and search hierarchical plans with phases, tasks, and milestones through a comprehensive planning API. Supports CRUD operations, batch updates, rich context retrieval, and artifact management for structured project planning.
      37
      37 npm
      4
      MIT
    • F
      license
      Not graded
      quality
      D
      maintenance
      A comprehensive project management system that provides a full-featured Kanban board and dashboard accessible to AI agents. It enables agents to programmatically manage projects, tasks, and workflows through a suite of 13 specialized tools and 4 resource types.
      22 npm
      4
      -
    • A
      license
      B
      quality
      C
      maintenance
      Enables AI assistants to interact with ProjectHub for comprehensive project management through natural language. It provides 25 tools to manage tasks, workspaces, time tracking, notes, and discussions via the ProjectHub API.
      47
      13 npm
      MIT