Jung Archetype Companion MCP Server

Model Context Protocol server providing Jungian archetypal analysis tools for multiverse episode construction.

Overview

This MCP server gives terminal agents programmatic access to Carl Jung's archetypal wisdom for constructing multiverse narratives where technical events (webhooks, commits, deployments) become archetypal patterns across three universes.

Companion to: Claude.ai Skill at ../jung-archetype-companion/SKILL.md

Difference:

• Skill: Instructions that modify Claude's behavior in Claude.ai
• MCP Server: Programmatic tools/resources/prompts for terminal agents

Installation

npm install
npm run build

Usage

In Claude Desktop MCP Config

Add to claude_desktop_config.json:

{
  "mcpServers": {
    "jung-archetype-companion": {
      "command": "node",
      "args": [
        "/src/_sessiondata/3aad5023-8920-47bb-8324-8a9b015046bb/mcp-jung-archetype-companion/dist/index.js"
      ]
    }
  }
}

In Terminal

# Build
npm run build

# Run (stdio mode for MCP)
node dist/index.js

Features

🛠️ Tools (6)

Invoke these as function calls:

1. analyze_archetype: Identify which Jungian archetype is active in context

   • Input: context (string), optional universe (engineer/ceremony/story)
   • Returns: Archetype analysis with manifestation details

2. map_technical_event: Map GitHub webhook to archetypal patterns

   • Input: event_type, event_data
   • Returns: Three-universe archetypal mapping

3. detect_shadow: Identify shadow work opportunities

   • Input: element, optional universe
   • Returns: Shadow patterns and integration paths

4. find_synchronicity: Detect meaningful coincidences across universes

   • Input: events array with universe/timestamp/description
   • Returns: Synchronicity strength and interpretation

5. get_hero_journey_stage: Map moment to Hero's Journey stage

   • Input: narrative_moment, optional dev_stage
   • Returns: Journey stage with description

6. generate_episode_seed: Create episode seed from technical event

   • Input: event_summary, optional theme
   • Returns: Archetypal seed for episode construction

📚 Resources (6)

Read these via URIs:

• jung://archetypes/core - Core Jungian archetypes (JSON)
• jung://archetypes/multiverse-mapping - How archetypes manifest in three universes (JSON)
• jung://shadow-patterns - Common shadow work patterns (JSON)
• jung://hero-journey - Complete Hero's Journey mapped to dev lifecycle (JSON)
• jung://taos-teaching - Jung's transformation at Taos Pueblo (Markdown)
• jung://technical-events-guide - Webhooks as archetypal events (Markdown)

💬 Prompts (3)

Pre-configured templates:

1. episode_from_webhook: Full episode construction from GitHub event

   • Args: event_type, event_payload

2. shadow_work_analysis: Deep shadow analysis

   • Args: character_or_universe, situation

3. synchronicity_scene: Generate scene showing parallel events

   • Args: parallel_events (JSON array)

Example Usage

Tool Call: Map Issue Creation

// Terminal agent invokes:
{
  tool: "map_technical_event",
  arguments: {
    event_type: "issue_created",
    event_data: {
      number: 110,
      title: "Live Story Monitor",
      labels: ["feature"],
      priority: "HIGH"
    }
  }
}

// Returns:
{
  archetypal_pattern: "Call to Adventure",
  engineer_perspective: {
    archetype: "Builder receives challenge",
    shadow: { fear: "What if implementing reveals inadequacy?" },
    ...
  },
  ceremony_perspective: {
    archetype: "Keeper receives invitation",
    shadow: { fear: "What if this extracts rather than serves?" },
    ...
  },
  story_perspective: {
    archetype: "Protagonist hears the call",
    shadow: { fear: "What if story becomes too complex?" },
    ...
  },
  synchronicity_opportunity: "All three universes receive call simultaneously"
}

Resource Read: Get Shadow Patterns

// Terminal agent reads:
resource: "jung://shadow-patterns"

// Returns JSON with:
{
  engineer: [
    { pattern: "Perfectionism", denial: "Fear of shipping imperfect work", ... },
    { pattern: "Extraction", denial: "Taking without giving", ... }
  ],
  ceremony: [...],
  story: [...],
  all: [...]
}

Prompt: Episode from Webhook

// Terminal agent uses prompt:
{
  prompt: "episode_from_webhook",
  arguments: {
    event_type: "issues.opened",
    event_payload: "{...webhook JSON...}"
  }
}

// Returns pre-filled prompt for Jung to analyze webhook as archetypal event

Integration with Multiverse Series

Series Location: /src/Miadi-46/stories/multiverse_3act_2512012121/

Use Cases:

1. Terminal agents building episodes from real GitHub events
2. Automated archetypal analysis of development activity
3. Synchronicity detection in webhook stream
4. Shadow pattern recognition in code reviews
5. Episode seed generation for narrative construction

Architecture

src/
├── index.ts              # MCP server setup, tool/resource/prompt handlers
├── knowledge.ts          # Archetype database, shadow patterns, synchronicity detector
└── technical-events.ts   # Maps GitHub events to archetypal patterns

Core Principle: Every technical event (webhook) is an archetypal event manifesting in digital form.

Jung's Post-Taos Consciousness

This MCP embodies Jung's wisdom after his 1925 encounter with Mountain Lake at Taos Pueblo:

Before: Archetypes were psychological symbols After: Archetypes are living presences requiring relationship

The MCP doesn't just analyze—it relates to archetypal patterns as real forces.

Development

# Install dependencies
npm install

# Build TypeScript
npm run build

# Watch mode
npm run watch

Dependencies

• @modelcontextprotocol/sdk - MCP TypeScript SDK
• typescript - TypeScript compiler
• @types/node - Node.js type definitions

License

MIT

Credits

Created by: Miawapaskone (Thread Connector) Based on: Carl Jung's archetypal psychology + Taos Pueblo Indigenous wisdom For: Multiverse narrative construction where technical events become archetypal story beats Companion Skill: ../jung-archetype-companion/SKILL.md

With gratitude to Mountain Lake, who taught Jung that relationship creates reality.