Results for github-to-omnifocus

Sync the issues assigned to you, to omnifocus

Import GitHub Issues into Omnifocus

Model Context Protocol (MCP) server that integrates with OmniFocus for AI assistant interaction

MCP server exposing the full OmniFocus surface to LLM agents — 80 typed tools spanning tasks, projects, tags, folders, perspectives, forecast, review, notes, attachments, and sync, with a strict typed-error taxonomy and per-tool circuit breakers, rate lim

Sync GitHub issues to OmniFocus

🚀 NEW: Native Custom Perspective Access! Enhanced MCP server with OmniFocus custom perspective support, hierarchical task display, AI-optimized tool selection, and comprehensive task management

A command-line interface for OmniFocus on macOS

MCP server for OmniFocus via Omni Automation API

Standalone OmniFocus reader and CLI for local macOS installs and encrypted vaults.

A utility-first CSS framework for rapidly building custom user interfaces.

Create binary artifacts hosted by github and install them without compiling.

PostCSS plugin for Tailwind CSS, a utility-first CSS framework for rapidly building custom user interfaces

Super-fast alternative for babel

A utility-first CSS framework for rapidly building custom user interfaces.

A utility-first CSS framework for rapidly building custom user interfaces.

Node-based CLI tool to sync GitHub issues to Omnifocus

A Jest transformer with source map support that lets you use Jest to test projects written in TypeScript

Run commands concurrently

Generate a markdown (GFM) table

The Expo CLI

Node's domain module for the web browser. This is merely an evented try...catch with the same API as node, nothing more.

Source maps support for istanbul

A small, fast, and correct TOML parser/serializer

semantic-release plugin to publish a GitHub release and comment on released Pull Requests/Issues

Plugin for omnifocus gem to provide github BTS synchronization. Support for Github Enterprise: In your git config, set the key github.accounts to a space separated list of github accounts. git config --global github.accounts "github myghe" For each account API and web end points and authentication information should be stored in the git config under a key matching the account. For example: git config --global github.user me git config --global github.password mypassword git config --global myghe.api https://ghe.mydomain.com/api/v3 git config --global myghe.api https://ghe.mydomain.com/ For each account can you specify the following parameters: * api - specify an API endpoint other than https://api.github.com. This is so you can point this at your Github Enterprise endpoint. * web - specify an API endpoint other than https://www.github.com. This is so you can point this at your Github Enterprise endpoint * user, password - A username and password pair for Basic http authentication.