Omnispindle CLI Bridge - Gemini Knowledge Repository

A curated collection of documentation and code examples for integrating Omnispindle MCP todo server capabilities with Gemini via gems. At the time of writing, Gemini does not support MCP integration, so this repository serves as a bridge to allow Gemini(or any other LLM) to interact with the Omnispindle ecosystem via a little copy-paste.

Purpose

This project houses the documentation needed to understand and integrate with the Omnispindle ecosystem. It's designed to be fed into Gemini gems as a knowledge package, providing:

• Function signatures and interfaces
• Usage examples and patterns
• Project validation logic
• Data structure definitions

Repository Contents

📋 Core Interface Files

• omnispindle_init.py - Function signatures for MCP integration
• tools_summary.py - shows the LLM the validation logic
• requirements.txt - Dependencies for understanding the ecosystem

📚 Documentation Files

• README_Omnispindle.txt - Original Omnispindle project documentation
• README_Swarmonomicon.txt - Swarmonomicon project overview

• README_TodoMill.txt - TodoMill project overview
• README_RegressionTestKit.txt - RegressionTestKit project overview
• README_Dirname.txt - Dirname project overview
• project_overview.txt - Comprehensive system architecture

🎯 Gemini Integration Files

• prompt_file_no_upload.md - Prompt template for creating our MCP CLI bridge gem

🎯 For Gemini Integration

When creating a Gemini gem that needs to interact with the Omnispindle ecosystem, feed these files to provide context on:

1. Available Functions: Todo management, lessons learned, MQTT pub/sub
2. Project Validation: Supported projects and naming conventions
3. Data Formats: Expected input/output structures
4. Integration Patterns: How to properly interface with the MCP server

Key Functions Available

Todo Management

add_todo_tool(description, project, priority="Medium", target_agent="user", metadata=None)
query_todos_tool(query_or_filter=None, fields_or_projection=None, limit=100)
update_todo_tool(todo_id, updates)
mark_todo_complete_tool(todo_id)
list_todos_by_status_tool(status, limit=100)
list_project_todos_tool(project, limit=5)

Knowledge Base

add_lesson_tool(language, topic, lesson_learned, tags=None)
search_lessons_tool(query, fields=None, limit=100)
list_lessons_tool(limit=100)
get_lesson_tool(lesson_id)

MQTT Communication

mqtt_publish_tool(topic, message, retain=False)
mqtt_get_tool(topic) # sub -C(ount) 1 to get a single message

Supported Projects

The system validates and works with these projects:

🌟 Core Ecosystem Projects

• madness_interactive - Parent Project of chaos - Main project repository
• omnispindle - MCP server for Managing AI todo list in python
• swarmonomicon - Todo worker and generation project in rust
• todomill_projectorium - Todo list management Dashboard on Node-red

🧪 Testing & Quality Assurance

• regressiontestkit - Parent repo for Work projects. Balena device testing in python
• quality_assurance - Quality assurance tasks

🖥️ Automation & Desktop Tools

• hammerspoon - MacOS automation and workspace management
• hammerghost - MacOS automation menu in hammerspoon based on eventghost
• eventghost - Event handling and monitoring automation. Being rewritten in Rust
• eventghost-rust - Rust rewrite of EventGhost automation system
• tinker - Browser testing automation framework in Rust

📱 Mobile & Device Management

• cogwyrm - Mobile app for Tasker interfacing with madness network
• balena_device_management - Device deployment and management tasks

🚀 Infrastructure & Deployment

• docker_implementation - Tasks todo with docker and deployment
• fastmcp - FastMCP server implementations and templates
• lab_management - Lab management general project

📚 Documentation & Knowledge

• documentation - Documentation for all projects
• spindlewrit - Writing and documentation project

🌐 Web & Frontend

• inventorium - Madnessinteractive.cc website and Todo Dashboard - React

📋 Available Projects Array

scope.availableProjects = [
  "madness_interactive",
  "omnispindle",
  "swarmonomicon",
  "todomill_projectorium",
  "regressiontestkit",
  "quality_assurance",
  "hammerspoon",
  "hammerghost",
  "eventghost",
  "eventghost-rust",
  "tinker",
  "cogwyrm",
  "balena_device_management",
  "docker_implementation",
  "fastmcp",
  "lab_management",
  "documentation",
  "spindlewrit",
  "inventorium"
]

Data Structures

Todo Item Format

{
  "id": "unique_id",
  "description": "Task description",
  "project": "validated_project_name",
  "priority": "Low|Medium|High",
  "target_agent": "user",
  "status": "pending",
  "created_at": "2024-01-01T00:00:00Z",
  "metadata": {
    "ticket": "PROJ-123",
    "tags": ["feature", "urgent"],
    "notes": "Additional context"
  }
}

Lesson Item Format

{
  "id": "unique_id",
  "language": "Python",
  "topic": "Async Patterns",
  "lesson_learned": "Use asyncio.gather() for parallel execution",
  "tags": ["async", "performance"],
  "created_at": "2024-01-01T00:00:00Z"
}

Usage in Gemini Gems

When creating a gem that needs MCP integration:

1. Feed this entire repository to Gemini for context
2. Reference the function signatures in omnispindle_init.py
3. Use the prompt template in prompt_file_no_upload.md to create your MCP CLI bridge gem

---

Note: This is a knowledge repository, not executable code. Use these files to understand the Omnispindle ecosystem when building Gemini gems that need MCP integration.