Mach5 One

Mach5 One is the single-node Mach5 server. It runs the Mach5 HTTP API, Data Explorer, MCP endpoint, and PostgreSQL-compatible SQL endpoint from one binary.

Use this repository to download Mach5 One, initialize a local data directory, start the server, connect clients, configure agents, and report runtime issues.

Mach5 One uses common Mach5 features and APIs. This repository documents the Mach5 One runtime experience; feature-level docs belong to common Mach5 documentation.

Quick start

# Create the default config and data directories
mach5-one init

# Start Mach5 One
mach5-one start

Default endpoints:

Web UI and HTTP API: http://localhost:8080
MCP:                 http://localhost:8080/mcp
PostgreSQL wire:     localhost:5432

Show the installed version:

mach5-one version

Use a custom config file:

mach5-one --config ./mach5-one.toml start

You can also set the config path with MACH5_ONE_CONFIG.

What Mach5 One provides

Mach5 One provides local access to shared Mach5 capabilities through a single-node server:

• Mach5 HTTP APIs under /apis
• API reference at /apis/rapidoc
• OpenAPI spec at /apis/openapi.json
• Data Explorer at / when UI assets are configured
• MCP endpoint at /mcp
• PostgreSQL-compatible SQL endpoint on the configured pg_port
• Local session endpoint at /session
• Version endpoint at /version.txt

Install

See docs/install.md.

Mach5 One binaries are published through GitHub Releases:

https://github.com/mach5-io/mach5-one/releases/latest

Configure

mach5-one init creates the default config file at:

~/.mach5-one/mach5-one.toml

The default data directory is:

~/.mach5-one/data

See docs/configuration.md.

Website documentation

This repository contains Mach5 One runtime documentation. The Mach5 website contains the complete versioned documentation set, including shared Mach5 feature docs and Mach5 Enterprise docs.

• Mach5 One docs in this repository cover installing, configuring, starting, connecting to, and troubleshooting the single-node server.
• Common Mach5 docs cover concepts and APIs shared by Mach5 One and Mach5 Enterprise.
• Enterprise docs cover multi-node deployment, scale, operations, governance, and production service-level requirements.

See the website docs scope guide: https://mach5.io/docs/next/overview/docs-scope

Use Mach5 One

• First-run guide: docs/quickstart.md
• Configuration: docs/configuration.md
• HTTP API examples: examples/curl/
• SQL examples: docs/query-examples.md
• Data loading guidance: docs/ingest-examples.md
• Troubleshooting: docs/troubleshooting.md

Use Mach5 One with an AI agent

Mach5 One exposes MCP at:

http://localhost:8080/mcp

See:

• AGENTS.md
• docs/mcp.md
• docs/agent-quickstart.md
• examples/agent-configs/

Looking for Mach5 Apps?

Mach5 Apps are packaged workflows, data models, queries, and agent-ready capabilities that run on Mach5 One and Mach5 Enterprise.

Reusable app catalogs are separate from this runtime repository. This repository focuses on the Mach5 One server, API/MCP setup, and first-run examples.

See docs/where-to-find-apps.md.

Repository structure

.
├── README.md
├── AGENTS.md
├── CHANGELOG.md
├── SECURITY.md
├── LICENSE.md
├── llms.txt
├── llms-full.txt
├── docs/
├── examples/
└── .github/
    └── ISSUE_TEMPLATE/

Issues and feedback

Use GitHub Issues in this repository for:

• Installation problems
• Server startup problems
• HTTP API issues
• PostgreSQL endpoint issues
• MCP integration issues
• Documentation gaps
• Runtime feature requests
• Agent-generated runtime reports

When filing an issue, include:

• Mach5 One version (mach5-one version)
• Operating system and architecture
• Install method
• Config file path, with secrets removed
• Steps to reproduce
• Expected behavior
• Actual behavior
• Relevant logs or error messages

Security issues must not be reported through public GitHub issues. See SECURITY.md.

License and terms

See LICENSE.md.