Is Temporal Cortex open source?

Temporal Cortex is built on open-source foundations. The core libraries are MIT/Apache-2.0 licensed. The MCP server binary is free to use with no limits.

What open-source repositories does Temporal Cortex maintain?

Temporal Cortex maintains 3 public repositories: temporal-cortex-core (TOON encoder + Truth Engine in Rust, MIT/Apache-2.0), temporal-cortex-mcp (MCP server docs and configs, MIT), and temporal-cortex-skill (Agent Skill for the 4-step scheduling workflow, MIT). Published packages are available on npm, crates.io, and PyPI.

temporal-cortex-core

TOON encoder + Truth Engine. Deterministic RRULE expansion, availability merging, and calendar time math.

MIT / Apache-2.0
Rust + JS + Python
temporal-cortex-mcp

MCP server documentation, configs, and community. The npm binary that gives AI agents 11 calendar tools.

MIT
Documentation
temporal-cortex-skill

Agent Skill teaching AI agents the 4-step scheduling workflow: orient → resolve → query → book.

MIT
SKILL.md + Scripts

Why is Temporal Cortex built with Rust?

Calendar scheduling for AI agents requires deterministic computation, memory safety, and cross-platform portability. Temporal Cortex is built in Rust and compiled to native binaries, WebAssembly, and Python bindings — one codebase, every platform.

510+

Rust tests

Unit + integration tests across 6 crates

9,000+

Property tests

Proptest + fuzzing for RRULE edge cases

5

Platform binaries

macOS (ARM + x64), Linux (ARM + x64), Windows

3

Language bindings

Rust + JavaScript/WASM + Python

Why Rust for scheduling infrastructure?

  • Memory safety without garbage collection — no runtime pauses, no undefined behavior, no data races in concurrent agent scenarios
  • Deterministic computation — RRULE expansion, timezone math, and availability merging produce identical results on every platform, every time
  • WebAssembly compilation — the same Rust code runs natively on servers and as WASM in browsers and edge runtimes, enabling offline-capable scheduling
  • Single-digit millisecond latency — native binary performance means temporal context, datetime resolution, and availability computation complete in under 5ms

How do I contribute to Temporal Cortex?

Contributions are welcome to all public repositories. Open issues for bug reports and feature requests, submit pull requests for code changes, or improve documentation. Every contribution helps make calendar scheduling better for AI agents.

Frequently asked questions

What license is Temporal Cortex?

The core libraries (TOON encoder and Truth Engine) are dual-licensed under MIT and Apache-2.0. The MCP server documentation and Agent Skill are MIT licensed. The MCP server npm binary is free to use with no limits. The commercial platform (API, portal, metering) is proprietary.

How do I contribute to Temporal Cortex?

Contributions are welcome to all public repositories. You can open issues for bug reports and feature requests, submit pull requests for code changes, or improve documentation. The main repositories are temporal-cortex-core (Rust + JS + Python), temporal-cortex-mcp (documentation and configs), and temporal-cortex-skill (Agent Skill).

What is the Truth Engine?

The Truth Engine is a deterministic RRULE expansion library written in Rust with JavaScript/WASM and Python bindings. It expands RFC 5545 recurrence rules into individual event occurrences, correctly handling DST transitions, BYSETPOS modifiers, EXDATE exceptions with timezone offsets, leap-year recurrences, and INTERVAL>1 with BYDAY. It replaces unreliable LLM inference with deterministic computation.