MCP reference
The Dropway MCP server
Connect Dropway to your AI tools over the Model Context Protocol. An assistant can browse, create, deploy, and re-share your sites, all scoped to your organization and gated by OAuth.
Build, then deploy, without leaving the chat
Ask your assistant to build something, then ask it to ship it. With the Dropway MCP server connected, it calls deploy_site and hands back a live, access-controlled URL, no copy-pasting files, no dashboard round-trip.
- Runs as you, scoped to your organization by row-level security.
- Public sites go live; gated sites stay private and reachable only through the authorized connection.
- Owners and admins can switch MCP access off per org at any time.
Connect your tool
Add Dropway as a custom connector. The first time you use it, a browser tab opens to sign in and approve access. No API keys to copy.
- Open Claude and go to Settings → Connectors.
- Click Add custom connector and paste the MCP server URL:MCP server URL
https://mcp.dropway.dev/mcp - Click Connect, then sign in to Dropway and approve “Authorize MCP access”. Dropway now appears as a connector and can browse and deploy your sites on request.
All four use the same endpoint:
https://mcp.dropway.dev/mcpWhat the assistant can do
Reads run directly off your org's data; writes go through the same authorization, quota, and audit as the dashboard.
| Tool | What it does |
|---|---|
list_sites | List your sites with their access mode, live status, and URL. |
list_files | List the files in a site's current version. |
read_file | Read one file from a site. |
download_site | Download every file of a site at once. |
create_site | Create a new site. |
deploy_site | Upload files and publish them to a live URL. |
set_site_access | Change a site's sharing (public, org-only, password, or allowlist). Owner/admin only. |
share_chat | Share the session transcript as a chat log: to your org's library, or attached to a site as its “How this was made” panel. |
append_chat | Add follow-up turns or action annotations to a shared chat as the work continues. |
get_site_chat | Read the shared chat log attached to a site (the transcript behind its “How this was made” panel). |
Share the story behind a site
When an assistant builds and deploys a site, it can publish the conversation that produced it alongside the artifact.
Call share_chat to save the session transcript as a Dropway chat log. Attach it to a site (by slug) and it renders as that site’s “How this was made” panel, the story behind the artifact, served under the site’s own access control. Leave it unattached and it goes to your organization’s chat library instead.
As the work continues, append_chat adds follow-up turns and short action annotations (a file edit, a tool run) so the log stays current. get_site_chat reads a site’s attached log back. One log attaches per site, and a gated site keeps its chat as private as its files.
dropway chat.How access works
The MCP server reuses Dropway's identity and authorization, it never gets a side door.
- OAuth 2.1. Connecting runs a standard browser sign-in and consent against your Dropway account; the tool receives a short-lived token, not a password or a long-lived key.
- Scoped to your org. Every call is bound to one organization and filtered by the same row-level security as the rest of the platform.
- Owner controlled. Owners and admins can turn MCP access off for the whole org in
Settings; it takes effect immediately, even for already-issued tokens.
Self-hosting
The MCP server ships with the self-host stack.
When you run Dropway yourself, the MCP server comes up alongside the rest on port 8092. Use your own URL as the connector endpoint instead of the hosted one:
http://localhost:8092/mcpGet a Dropway account
Sign in once in your AI tool and start shipping sites from chat. Prefer the terminal? The CLI does the same deploy.