Home

Titian Wiki

Titian connects local development projects to remote MCP clients through one authenticated HTTPS gateway. Each project gets its own connection URL, OAuth credentials, Desktop Commander process, and configured folders.

Use one connection for a repository, separate connections for unrelated projects, or one connection covering a backend and a mobile application.

Start here

1. Getting Started — install Titian and connect your first client.
2. Managing Projects — add projects, configure multiple roots, and manage their lifecycle.
3. Authentication and Metadata — OAuth, consent PINs, and project identification.
4. Architecture and Ports — understand the gateway and per-project services.
5. Troubleshooting — diagnose unavailable connections and OAuth failures.
6. FAQ — common questions and practical answers.
7. Maintenance and Recovery — updates, logs, backups, and migration.

Supported setup

The service manager runs on macOS with Python 3.10+, Node.js 22+, npm, and Git. Remote clients must support Streamable HTTP MCP and OAuth dynamic client registration. Public access requires an HTTPS reverse proxy; the getting-started guide uses Tailscale Funnel.

Titian is designed for a single owner. Configured folders are not an operating-system sandbox: terminal tools run with the permissions of the account running Titian. Read the security policy before exposing it.

Source and support

• Source repository and README
• Issues for reproducible bugs and feature requests.
• Report vulnerabilities privately using the repository's Security reporting flow.

Examples use placeholders. Replace hostnames, slugs, and paths with your own values. Never publish your consent PIN, tokens, OAuth state, or private logs in an issue.