uivoid
MCP-native hosting · free to start

Stop building
backoffice UIs.

Let your agent call the API directly. uivoid turns your database schema and internal APIs into scoped, audited MCP tools — deployed in minutes, not maintained for months.

free to start · no signup required to try it · Postgres, Django admin, REST

zsh — sowe/
$ npx uivoid create
✔ introspecting schema … 14 tables
✔ curated 9 scoped tools
✔ container built · 118MB
✔ live → sowe.uivoid.app
agent> get_overdue_invoices()
← 3 rows · read scope · 41ms
the problem

Every schema change is a UI ticket.

Internal backoffices are expensive to build and even more expensive to maintain. Every migration means new fields, new forms, new validation, new screens — for a tool nobody outside the team ever opens. Meanwhile, an LLM that can safely call get_customer or update_order_status doesn't need a screen at all.

backofficestatus quo

Weeks to build. Breaks on every migration.

  • New column → new form, new validation, new screen
  • Schema drift means a full redeploy cycle
  • Engineering time spent on UI nobody outside the team sees
  • Auth bolted on per-screen, inconsistently
uivoiduivoid

Minutes to deploy. Regenerates itself.

  • +Introspects your schema — no manual mapping
  • +Tools regenerate as the schema drifts
  • +Curated, scoped tools: read / write / destructive
  • +The agent — or a person prompting it — is the interface
how it works

From schema to scoped tools, four steps.

  1. 01
    create

    npx uivoid create scaffolds a new project — the CLI does the setup, you don't hand-roll config.

  2. 02
    introspect

    uivoid reads your Postgres schema, Django admin, or REST surface and suggests operations worth exposing.

  3. 03
    scope

    Not a 1:1 table dump — curated tools labeled read / write / destructive, named for an LLM to reason about correctly.

  4. 04
    deploy

    Ships to a container on uivoid's hosting, live at yourorg.uivoid.app — preview and production URLs, versioned like any deploy.

uivoid — suggested tools for sowe.db
> analyzing 14 tables, 3 join views
get_customer read
list_overdue_invoices read
update_order_status write
create_refund write
delete_customer destructive*
* requires elevated scope + confirmation
auth

Not a shared-secret toy.

Platform login is standard email/OAuth — we didn't reinvent that. Per-tool access is where it matters, and it depends on what you've already got.

already have an idp

Resource server in front of your IdP

The deployed MCP server acts as an OAuth 2.1 resource server in front of your real identity provider — per-user permissions carry through instead of flattening everyone into one shared credential.

agentuivoid (resource server)
your IdP · token check
your database / API
no auth system yet

Scoped keys, issued and revocable

uivoid issues per-project API keys with explicit scopes. One compromised key doesn't require rotating everything — and every call is attributable in the audit log.

readwritedestructive

sk_live_sowe_7f2a… · revoked 2026-08-30 · 0 calls since

why uivoid

Built for teams who'd rather not build a UI.

uivoid is free to start and secure by default — scoped tools, OAuth 2.1, and a full audit trail on every call. No backoffice to build, no auth system to bolt on later.

solo devs & small teams

Stop maintaining an internal backoffice for your own fast-moving schema. Point uivoid at the database, ship the tools instead.

small businesses

No existing auth system? Get a safe, scoped way to let an agent operate your internal tools without building anything custom.

growing teams

Already have an IdP? Give agents scoped, audited access to internal systems without exposing raw DB or API access.

free to start

Remove the screen.

uivoid is early and free to start. Try the CLI, read the source, or tell us what your backoffice looks like — we're building against it.

Star on GitHub

or write to hello@uivoid.app