# Twinbly CLI and MCP server for Gaussian splatting

Use Twinbly cloud processing from your terminal or a coding assistant. Turn overlapping photos or video into 3D Gaussian splats, then build your own interface around the available output. The CLI and local Model Context Protocol (MCP) server are available now as the same versioned download.

## Choose how to connect

| Tool | Use it for |
| --- | --- |
| CLI | Scripts, terminal workflows and coding agents that can run commands |
| Local MCP server | A trusted assistant that can discover and call structured Twinbly tools |
| HTTP API | Your application's backend and broader documented operations |

The CLI and MCP share the workflow: inspect capabilities, review an estimate, create and upload a capture, explicitly approve paid processing, check progress and retrieve available results. [Legend Guide](https://www.twinbly.com/developers/legend-guide) shows a real product built around Twinbly processing and 3D output.

## Download the official tools

Version **0.1.0** requires **Node.js 22 or newer**. Download the [executable](https://www.twinbly.com/developers/tools/0.1.0/twinbly.cjs), [checksum manifest](https://www.twinbly.com/developers/tools/0.1.0/manifest.json) and [third-party notices](https://www.twinbly.com/developers/tools/0.1.0/THIRD-PARTY-NOTICES.txt). Follow the [checksum and complete setup instructions](https://www.twinbly.com/developers#cli-mcp).

After checking the download, these commands need no key and start no processing:

```sh
node twinbly.cjs version
node twinbly.cjs capabilities
node twinbly.cjs help
```

For account and processing operations, create a [self-service processing API key](https://www.twinbly.com/dashboard/developers/keys) and use your Twinbly wallet. Keep the key in a private environment file or your host's secret environment settings. Do not put keys in prompts or command arguments.

## Connect an AI coding assistant

The MCP server runs locally over standard input/output. Configure your trusted MCP-capable host to launch Node with the downloaded executable, the `mcp` command, an input folder and a private local state folder. The [full guide](https://www.twinbly.com/developers#cli-mcp) provides the configuration example and file permissions.

Start by asking: "List Twinbly's capabilities. Explain the capture requirements and show me an estimate before starting paid processing."

Paid MCP starts require the host to show a confirmation form. If your host does not support that form, use its other tools and approve the start through the CLI. A host supporting MCP does not by itself establish that every Twinbly operation works in that host.

## Build your own branded 3D experience

Your backend can submit a capture and retrieve assets for your own compatible web or native viewer. Your product controls its interface, customer accounts, access and customer billing. You do not need to send customers through Twinbly's upload interface. See the [API workflow](https://www.twinbly.com/developers) and [coding-agent brief](https://www.twinbly.com/developers/agent-brief.md).

## Availability and limits

- The supported distribution today is the direct download above. An npm package and MCP registry listing are not yet available; do not guess a package name.
- There is no hosted MCP URL in this release. A browser-only chat needs a supported local host or another integration.
- An estimate is not a price cap or a completion deadline. Queue time and processing time can differ; review the current estimate before approving a charge.
- Training completion and converted-format readiness are separate. Inspect the actual downloads; not every format is available for every job.
- The tools do not automatically publish a public Twinbly scene or expose every editor feature. Your application decides how to use and share the results.

[Pricing](https://www.twinbly.com/pricing) · [Service terms](https://www.twinbly.com/terms) · [Product updates](https://www.twinbly.com/updates/twinbly-cli-and-local-mcp)
