About Slipway
Slipway is a deterministic Rust MCP server for owners building, signing, verifying, installing, and preparing releases of their own Android apps. Its staged gates and append-only receipts track consequential actions, while store submission remains a human task.
Key features
- 01Build and install Android apps
- 02Sign and verify build artifacts
- 03Prepare app release bundles
- 04Gate consequential signing actions
- 05Append actions to receipt logs
Use cases
- 01Build an owned Android app
- 02Verify and sign a release build
- 03Prepare a bundle for human submission
MCP support
Slipway is a Rust MCP server that exposes Android app build, signing, verification, installation, and release-preparation operations to MCP clients.
Configuration
Local server config is the same for every client. Copy it into your client’s MCP config file.
We haven’t collected a package or remote endpoint for this server. Follow the instructions in the project README.
Tools
Local servers expose tools only once running on your machine, and the maintainer has not provided a tool list.
Details
From the project READMEslipway
A small deterministic Rust MCP server that builds, signs, verifies, installs, and prepares releases of the Owner's own Android apps — and nothing else. Slipway never sees reference artifacts: the methodology firewall keeps fathom (which censuses) and slipway (which ships) separate, and the study document is the only bridge (workflow SB-1: study → bridge → build → census-back → conformance diff).
Posture: read-class tools land and gate first; signing is
consequential-class, gated by the signed-authority chain from its
first day; every action appends to the slipway.receipt log; the
release bundle is the deliverable and store submission stays a
human act. No build is authorized by the program documents alone —
stages run on the Owner's word.
Progress
7% — 2 of 28 gates closed, 3 delivered and awaiting gate — updated 2026-10-21. Full record: CHECKLIST.md — every item traces to a stage gate in the program documents; the bar moves only on gated evidence.
Progress here is tracked from ideation to the finished 1.0 and beyond: each checklist item is a stage gate from the program documents, and it closes only on verified evidence.
License
Apache-2.0 — see LICENSE.
Comments
New to MCP?
From what the protocol is to installing your first server, these answers cover most first questions.
An open protocol that defines how AI applications connect to external tools and data in a uniform way. Clients talk to the model; MCP servers provide tools, resources and prompt templates. They exchange standard messages, so one server can be reused by many clients.