@hailer/mcp 0.0.1

package/.claude/commands/tool-builder.md

@@ -0,0 +1,37 @@
+---
+description: Activate tool-builder mode to implement a new MCP tool
+---
+
+Load the `tool-builder` skill and enter tool-building mode.
+
+**What tool should I build?**
+
+Please provide:
+
+- **Tool Name**: `tool_name` (snake_case)
+- **Purpose**: What does it do?
+- **API Endpoint**: `v3.endpoint.method`
+- **Request Format**: `[arg1, arg2]`
+- **Response Format**: What the API returns
+- **Target File**: Which file in `src/mcp/tools/`?
+- **Tool Group**: READ | WRITE | PLAYGROUND
+
+---
+
+**Example:**
+```
+Tool Name: list_insights
+Purpose: List all insights in workspace
+API Endpoint: v3.insight.list
+Request: [workspaceId]
+Response: { insights: [{_id, name, query, sources}] }
+Target File: insight.ts
+Tool Group: PLAYGROUND
+```
+
+I'll:
+1. Load tool-builder skill
+2. Read existing patterns in target file
+3. Implement the tool
+4. Register in src/app.ts
+5. Report what was created

package/.claude/commands/ws-pull.md

@@ -0,0 +1,44 @@
+---
+description: Pull workspace configuration from Hailer (READ-ONLY)
+---
+
+Pull the current workspace configuration from Hailer and save it locally.
+
+**What this does:**
+- Downloads workflows, insights, teams, groups, and phases from Hailer workspace
+- Saves configuration as JSON files to the `WORKSPACE_CONFIG_PATH` directory
+- READ-ONLY operation - does not modify anything on Hailer
+- Safe to run anytime
+
+**Requirements:**
+- Must have `WORKSPACE_CONFIG_PATH` set in `.env.local`
+- Hailer credentials must be configured
+
+**Instructions for Claude:**
+
+1. Read `.env.local` file to get `WORKSPACE_CONFIG_PATH`
+2. Run: `cd "$WORKSPACE_CONFIG_PATH" && npm run ws-pull`
+3. **AUTOMATICALLY read the generated files to load context:**
+   - Read `workspace/enums.ts` (complete file - contains ALL field and phase IDs)
+   - List `workspace/` directory to see all workflow folders
+   - Read 1-2 example workflow configs (main.ts, fields.ts, phases.ts) to understand structure
+4. Provide summary of what workflows were pulled and confirm context is loaded
+
+**What gets downloaded:**
+- `workspace/enums.ts` - Type-safe field and phase ID enums for ALL workflows
+- `workspace/workflows.ts` - Main workflows export
+- `workspace/insights.ts` - SQL insight definitions
+- `workspace/teams.ts` - Team structures
+- `workspace/groups.ts` - User groups
+- `workspace/<workflow_name>/` - Individual workflow configs (main.ts, fields.ts, phases.ts)
+
+**Why automatic reading matters:**
+- Loads all field/phase IDs into conversation context immediately
+- Enables local-first strategy without manual file reads
+- Saves 75% of API calls and hundreds of tokens on subsequent operations
+- You'll know the workspace structure instantly
+
+**Common use cases:**
+- Backup current workspace configuration
+- Review workflow structures locally
+- Prepare for making configuration changes

package/.claude/settings.json

@@ -0,0 +1,8 @@
+{
+  "permissions": {
+    "deny": [
+      "Read(./.env.local)",
+      "Read(**/.env.local)"
+    ]
+  }
+}

package/.claude/settings.local.json

@@ -0,0 +1,49 @@
+{
+  "permissions": {
+    "allow": [
+      "mcp__hailer__create_activity",
+      "mcp__hailer__list_workflow_phases",
+      "mcp__hailer__list_workflows",
+      "mcp__hailer__show_activity_by_id",
+      "mcp__hailer__get_workflow_schema",
+      "mcp__ide__getDiagnostics",
+      "mcp__hailer__remove_workflow",
+      "Read(//tmp/**)",
+      "mcp__hailer__install_workflow",
+      "mcp__hailer__update_workflow_field",
+      "mcp__hailer__update_activity",
+      "Skill(agent-building)",
+      "mcp__hailer__search_workspace_users",
+      "mcp__hailer__add_discussion_message",
+      "mcp__hailer__join_discussion",
+      "mcp__hailer__fetch_discussion_messages",
+      "mcp__hailer__list_activities",
+      "mcp__hailer__get_insight_data",
+      "mcp__hailer__create_insight",
+      "mcp__hailer__preview_insight",
+      "mcp__hailer__remove_insight",
+      "mcp__hailer__create_app",
+      "mcp__hailer__scaffold_hailer_app",
+      "mcp__hailer__update_app",
+      "mcp__hailer__publish_hailer_app",
+      "Bash(npm run build:*)",
+      "Bash(npm pack)",
+      "Bash(yes:*)",
+      "Bash(printf:*)",
+      "Bash(script -qec:*)",
+      "mcp__hailer__list_workflows_minimal",
+      "Skill(hailer-api)",
+      "Skill(publish-hailer-app-skill)",
+      "Bash(find:*)",
+      "mcp__hailer__list_templates",
+      "Skill(insight-api)",
+      "Bash(node -e:*)",
+      "mcp__hailer__create_template",
+      "mcp__hailer__update_workflow_phase"
+    ]
+  },
+  "enableAllProjectMcpServers": true,
+  "enabledMcpjsonServers": [
+    "hailer"
+  ]
+}

package/.claude/skills/activity-api/SKILL.md

@@ -0,0 +1,96 @@
+---
+name: Activity API Reference
+description: Complete reference for Hailer Activity API endpoints (v2 and v3) - use when building activity-related MCP tools
+---
+
+# Activity API Reference Skill
+
+This skill provides comprehensive documentation for all Hailer Activity API endpoints. Use this as a reference when building MCP tools that interact with activities.
+
+## When to Use This Skill
+
+Invoke this skill when:
+- Building new activity-related MCP tools
+- Understanding available activity operations
+- Implementing activity creation, updates, or queries
+- Working with activity links, templates, or bulk operations
+- Exploring timeline, kanban, or calendar views
+
+## Quick Navigation
+
+### Core Activity Operations
+- **v3.activity.list** - List activities with advanced filtering and pagination
+- **v3.activity.create** - Create a single activity
+- **v3.activity.createMany** - Batch create multiple activities
+- **v3.activity.updateMany** - Batch update multiple activities
+- **v3.activity.template.create** - Get activity template with field definitions
+
+### Activity Relationships
+- **v3.activity.linkedFrom.overview** - View activities linked to a target activity
+- **v3.activity.linkedFrom.search** - Search linked activities
+- **v2.activities.copy** - Copy activities with optional renaming
+
+### Views & Visualization
+- **v3.activity.kanban.list** - Kanban board view
+- **v3.activity.timeline** - Timeline/calendar view with grouping
+- **v3.activity.events** - Calendar events from date fields
+
+### Advanced Operations
+- **v3.activity.evaluateMany** - Dry-run function field evaluations
+- **v3.activity.permissions** - Check user permissions
+- **v3.activity.removed.overview** - List deleted activities
+- **v3.activity.removed.recover** - Restore deleted activities
+
+## Documentation
+
+See [Activity API Endpoints](references/activity-endpoints.md) for complete endpoint documentation with request/response schemas.
+
+## Key Concepts
+
+### Activity Creation Pattern
+```typescript
+// 1. Get template to understand required fields
+const template = await getActivityTemplate(workflowId, phaseId);
+
+// 2. Create activity with proper field structure
+const result = await createActivity(workflowId, {
+  name: "Activity Name",
+  fields: {
+    [fieldId]: value,  // Use fieldIds from template
+  },
+  phaseId: phaseId,
+  teamId: teamId  // Required if no default owner
+});
+```
+
+### Filtering Activities
+```typescript
+// Use filters object for complex queries
+const activities = await listActivities(workflowId, {
+  filters: {
+    and: [
+      { [fieldId]: { equalTo: "value" } },
+      { [dateFieldId]: { between: [startMs, endMs] } }
+    ]
+  },
+  returnFlat: true  // Use flat structure for easier field access
+});
+```
+
+### returnFlat Mode
+- **returnFlat: false** - Fields nested in `fields` object with complex structure
+- **returnFlat: true** - Fields flattened to root level, accessible by field key
+
+## Common Use Cases
+
+1. **List activities in a workflow/phase**: Use `v3.activity.list`
+2. **Create multiple activities**: Use `v3.activity.createMany` with template
+3. **Update activity fields**: Use `v3.activity.updateMany`
+4. **View activity relationships**: Use `v3.activity.linkedFrom.overview`
+5. **Get field definitions**: Use `v3.activity.template.create`
+6. **Timeline/calendar view**: Use `v3.activity.timeline` or `v3.activity.events`
+
+## Next Steps
+
+For complete endpoint documentation with request/response schemas, see:
+- [Activity API Endpoints](references/activity-endpoints.md) - All v2 and v3 endpoints