Main Sequence Python SDK
The Main Sequence Python SDK is the client and development toolkit for the Main Sequence platform.
The Main Sequence platform allows you to:
- rapidly build and deploy data products with normalized
MetaTablecontracts andTimeIndexTableUpdaterproducer workflows - deploy FastAPI services and supported application surfaces on the platform
- rapidly deploy agents using the Google Agent SDK
The key idea is that you can focus on development and deployment, while the platform handles the DevOps layer.
Repository Status
- Status: actively maintained
- Last commit:
2026-03-27-6aa5dea-docs logo fix v.3.17.6 - Open issues: GitHub Issues
- Documentation: Documentation Site
- Security policy: SECURITY.md
- Release history: CHANGELOG.md
- Major-version migrations: Migration guides
What this repository contains
This repository contains the SDK and documentation used to build and operate Main Sequence CodeRepositories.
Main package areas:
mainsequence.meta_tables:MetaTables,TimeIndexTableUpdaters, update workflows, and persistencemainsequence.client: API client models for CodeRepositories, jobs, time-index tables, sharing, and platform resourcesmainsequence.cli: themainsequencecommand-line interface
Repository areas:
docs/: knowledge guides, CLI docs, and generated reference docstests/: automated tests
Documentation map
The documentation is organized into three reading modes:
- Knowledge: deeper conceptual guides
- CLI: command-focused operational documentation
- Reference: generated API reference
Recommended entry points:
- Beginner tutorial:
- Knowledge:
- Migrations:
- CLI:
Quick start
Install the package:
pip install mainsequence
Authenticate:
mainsequence login
An already MCP-authenticated coding agent can establish the same persisted CLI
session with mainsequence login --mcp, then call the printed
auth.cli_authorize tool while the command waits. The backend supplies the
callback URI; tokens return directly to the CLI and are never exposed through
MCP.
Check that you can see your CodeRepositories:
mainsequence code-repository list
Create a new CodeRepository:
mainsequence code-repository create my-first-repository
Set it up locally:
mainsequence code-repository set-up-locally <CODE_REPOSITORY_UID>
cd my-first-repository
mainsequence code-repository build-local-venv --path .
From there, the normal learning path is:
- model your first canonical table with a backend-managed
MetaTable - create your first
TimeIndexTableUpdateras an opinionated MetaTable-backed update workflow - understand sharing and RBAC for published tables
- add an API or another application surface
- schedule jobs
- build supported application surfaces or downstream consumers
- package the CodeRepository as an agent-facing surface when it is ready
Installation for development
This repository uses pyproject.toml and a development dependency group.
With uv:
uv sync --group dev
Or with pip, install the package and the docs/test tools you need separately.
Common development commands
Run the CLI:
mainsequence --help
Run tests:
pytest
Serve the docs locally:
mkdocs serve
Build the docs:
mkdocs build
Lint the code:
ruff check .
Format the code:
black .
How to read this repository
If you are evaluating the platform:
- start with the separate canonical tutorial CodeRepository linked above
If you are building a feature and already know the area:
- go straight to the relevant guide in
docs/knowledge/
If you are operating CodeRepositories day to day:
- use
docs/cli/and themainsequence --helpcommand tree
If you need the exact SDK surface:
- use
docs/reference/
Package metadata
- Package name:
mainsequence - Python:
>=3.13 - CLI entry point:
mainsequence
Package metadata is defined in pyproject.toml.
License
This repository is distributed under the terms described in LICENSE.
1 maintainer
Release files for mainsequence 8.1.10
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | |
|---|---|---|---|
| mainsequence-8.1.10.tar.gz | 540.8 kB | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| mainsequence-8.1.10-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 952.6 kB
Release files / mainsequence-8.1.10.tar.gz
| Download URL | mainsequence-8.1.10.tar.gz |
|---|---|
| Size | 540.8 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
f86d5eb915e4db7084a501cd4696311ad0fa24b57e5827aebab3ba2c6e974e50
|
|
BLAKE2b-256 checksum How to use checksums |
eabe8abbd496d58ffc9367e88915fd1b284597a16304f67332f7df81611df8b9
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.14
|
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Sep 12, 2026.
Transparency logRelease files / mainsequence-8.1.10-py3-none-any.whl
| Download URL | mainsequence-8.1.10-py3-none-any.whl |
|---|---|
| Size | 411.8 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
e8bf016d71f1b439fdb6a0e4652ebf6f28b2732c8c7ba4aec5d44fb8a3e1632b
|
|
BLAKE2b-256 checksum How to use checksums |
50a147c1b92e8de7dfac435bbc9ee9516a35d9cd2f5cadfae718834b963eb754
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.14
|
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Sep 12, 2026.
Transparency log
