publishwith.ai logo
Open Beta — Free for Everyone
MCP publishing runtime for AI agents

Your AI built it. Now give it a secure URL.

publishwith.ai lets Claude, Codex, ChatGPT, and other MCP clients publish authenticated dashboards, reports, and micro-apps with a database, permissions, versions, and audit logs already wired in.

One MCP connection. No deployment pipeline. No separate app builder.

publishwith.ai / apps / board-revenue-q3 Published v12

Board revenue dashboard

Private app. Exec group only. SQLite-backed SSR with JSON endpoints.

Revenue $4.8M +18.2%
Active users 38.4k +9.7%
Views 186 audited
13:42Claude Codepublished v12
13:43Accessexec-team viewer
13:44Auditfirst secure view

Publishing becomes an agent action.

The agent does the boring production work directly through MCP: creates the app, loads data, publishes a version, and sets who can see it.

1

Connect once

Add publishwith.ai to your MCP client. Claude Desktop, Claude Code, ChatGPT, Codex, and any compatible client can use the same publishing tools.

2

Ask for the app

"Build a sales dashboard from this data and share it with finance." The agent creates HTML, templates, tables, endpoints, and permissions.

3

Send the link

Your team gets an authenticated URL behind SSO. External viewers can receive revocable public read-only links when you allow it.

The gap is not generation. It is controlled distribution.

Agents can already create useful internal software. Teams still lose time turning that output into something secure enough to share.

Reports drift through Slack and email.

No versioning, no revocation, no clean answer to who saw what.

Static hosting stops at the easy part.

Authentication, access control, databases, and audit still need engineering time.

Internal apps need live data.

publishwith.ai gives each app isolated SQLite storage, dynamic rendering, and JSON endpoints.

User: Build a deployment KPI dashboard from this CSV.
Agent: Creating app deploy-kpis.
Agent: Creating SQLite schema and importing 14,208 rows.
Agent: Publishing dynamic routes and JSON API.
Agent: Granting viewer access to engineering-leads.
publishwith.ai: Published at /a/deploy-kpis/

Made for the way agents actually work.

The platform exposes a small set of publishing primitives instead of another UI workflow your team has to learn.

M

MCP-native

Create apps, publish versions, execute guarded SQL, inspect schemas, and manage ACLs from the agent.

D

Data included

Every app can have an isolated SQLite database for real dashboards instead of pasted screenshots.

V

Versioned

Publishes are immutable and auditable, so teams can trust the link they are opening.

Use it where quick output still needs real controls.

"Analyze Q3 revenue and publish a board report. Exec team only."

Executive reporting

Private, versioned reports with SSO, app-level permissions, and a clear audit trail.

"Create a KPI dashboard and update the data whenever I ask."

Live dashboards

Server-rendered pages and JSON endpoints backed by an app-specific SQLite database.

"Build a demo for Acme and give me a public link."

External sharing

Generate revocable read-only links without opening the whole app or adding a viewer account.

Security features are part of the publish path.

publishwith.ai is built for internal tools, customer-facing demos, and agent-created apps that need more than "here is an HTML file."

Corporate SSO

OIDC support for Azure AD, GitHub, Keycloak, and other identity providers.

Per-app ACLs

Owner, editor, and viewer roles for users and groups.

HTML sanitization

Uploaded HTML is sanitized and served with restrictive CSP headers.

Audit logging

Publish, view, access, and admin actions are logged with actor identity.

Guarded SQL

Agents can work with data while destructive operations stay classified and controlled.

Share links

Public read-only links are revocable, token based, rate limited, and tracked.

What changes compared with the usual workarounds.

publishwith.ai replaces the manual steps between "the agent made it" and "the right people can use it."

Capability Email / Slack Shared drive Static hosting publishwith.ai
Agent publishes directly - - - Yes
Per-app access control - Basic - Yes
Database-backed pages - - - Yes
Audit trail - Limited - Yes
Revocable public links - Limited - Yes
No deployment work Yes Yes - Yes
Open Beta — All features free until launch

Simple, transparent pricing

All features are unlocked during the beta. Billing starts when we launch — beta users get advance notice and a grace period.

Free

Personal projects and experimentation

€0/month
  • Up to 5 apps
  • 10 MB database per app
  • 3 share links per app
  • Built-in auth & social login
  • Static HTML & Markdown, Liquid SSR, JSON API
  • MCP access
  • Custom OIDC / SSO
  • Account deleted after 30 days inactivity
Get started free

Enterprise

Enterprises with advanced auth needs

€49/month
  • Unlimited apps
  • 1 GB database per app
  • Unlimited share links
  • Multiple OIDC / OAuth2 providers
  • Static HTML & Markdown, Liquid SSR, JSON API
  • MCP access
  • No account expiration
  • Priority support
  • Custom subdomain (yourteam.publishwith.ai) Phase 2
Start free beta

Prices are indicative and may change before general availability. Beta users will receive advance notice before billing begins.

Frequently asked questions

What is the open beta?
During the open beta, all features — including Team and Enterprise — are available to everyone for free. No credit card required. When we launch billing, all beta users will receive advance notice and a grace period before any charges begin.
What happens to my apps when billing starts?
Nothing changes automatically. You will receive an email before billing begins. If you choose the Free tier, any apps beyond the 5-app limit will be archived (not deleted) and you can choose which ones to keep active.
What does “inactivity deletion” mean for Free accounts?
Free accounts with no login or app access for 30 days receive a warning email. If the account remains inactive for 3 more days, it is deleted. This only applies to the Free tier — Team and Enterprise accounts are never auto-deleted.
What is MCP and why does it matter?
MCP (Model Context Protocol) is the standard protocol for AI agent tool use, supported by Claude, Codex, ChatGPT, and other major models. publishwith.ai exposes MCP tools so your AI agent can publish, update, and share apps directly — no manual deployment, no copy-paste, no separate build pipeline.
Can I use my own identity provider (SSO)?
Yes. The Team plan includes one OIDC provider (e.g. Google Workspace, Okta, Azure AD, Keycloak). Enterprise supports multiple OIDC/OAuth2 providers. The Free tier uses built-in email/password auth plus social login (GitHub, Google).
Is each app’s database isolated from other apps?
Yes. Every app gets its own dedicated SQLite database file. There is no cross-app or cross-tenant data mixing. You can query it from Liquid templates, the JSON API endpoints, or browse it directly in the admin panel.
Can I upload multiple files per app?
Yes. A single publish call can include as many files as needed — HTML, CSS, JS, images, fonts, and more. The full set of files becomes an immutable version. Asset size limits apply per plan: 50 MB total per version on Free and Team, 500 MB on Enterprise.

Give your AI agent a production publishing target.

For teams that want AI-generated apps, reports, and dashboards without losing authentication, data control, or auditability.

Start free