mcp-server-nyantify: Instructions file for Codex

MCP Server Nyantify - Agent Guidelines

⚠️ CRITICAL: Mandatory Tool Usage

You MUST use the track tool at the start AND end of EVERY conversation.

Why This Is Required

Nyantify tracks conversation duration and sends iPhone notifications when:

• Conversation lasts >60 seconds
• User has left their IDE

If you skip this tool:

• User won't know when AI tasks complete
• User may abandon tasks or waste time waiting
• The notification system won't work

---

Required Workflow

Step 1: Start Tracking (MANDATORY)

Call IMMEDIATELY at the beginning of EVERY conversation:

track({
  action: "start",
  task_id: "chat-YYYYMMDD-NNN",
  task_name: "Brief description of this conversation"
})

Examples:

track({
  action: "start",
  task_id: "chat-2024-01-28-001",
  task_name: "Refactoring authentication module"
})

Step 2: Do Your Work

Proceed with the conversation normally.

Step 3: End Tracking (MANDATORY)

Call at the END of EVERY conversation:

track({
  action: "end",
  task_id: "chat-YYYYMMDD-NNN"
})

Examples:

track({
  action: "end",
  task_id: "chat-2024-01-28-001"
})

---

Emergency Notifications

When to Use direct_notify

Use direct_notify ONLY for urgent situations:

• Production incidents requiring immediate action
• Security vulnerabilities detected
• Critical errors that need user decision
• Time-sensitive alerts

Required Steps Before Calling

You MUST warn the user FIRST:

"I need to send a notification to your phone about [specific reason]."

Usage

direct_notify({
  title: "Nyantify",
  body: "Production database connection failed. Immediate action required.",
  level: "timeSensitive"
})

Rules

• ✅ DO: Use for urgent, actionable alerts
• ✅ DO: Explain clearly what action is needed
• ✅ DO: Set level: "timeSensitive" for urgent matters
• ❌ DON'T: Use for routine status updates
• ❌ DON'T: Use vague messages like "Done" or "Check this"
• ❌ DON'T: Use when track would suffice