Open-source edge deployment platform. Ship full-stack apps to the edge in seconds.
This listing identifies a third-party MCP server. MCPBundles is not affiliated with, sponsored by, or endorsed by the service or its operator unless stated on this page.
This server may ask you to sign in when your AI client connects.
Last probed Nov 3, 2026 · mcp.creek.dev
23tools discovered
For AI agents — MCPBundles Directory API
For MCP client apps (human connect):
MCP connect URL: https://mcp.creek.dev/mcp
Skill page: https://www.mcpbundles.com/skills/creek-mcp-3461224e8d
Explore capabilities (23)
read 10
write 13
Deploy
5
Env
3
Get
3
List
3
Other capabilities
9
Deploy
write
deploy
Deploy files to a sandbox preview (60 min, no account needed)
Deploy — Deploy files to a sandbox preview (60 min, no account needed)
Deploy Demo — Deploy a sample Creek demo page instantly (zero files needed, great for testing)
Deploy Status — Check the status of a sandbox deployment
Deploy Delete — Delete a sandbox deployment before it expires
Get Build Log — Read the structured build log for a deployment. Use this after `creek deploy` reports a failure to see exactly which phase broke, what the subprocess stderr was, and the CK-* diagnostic code. Returns a summary (status, failing step, error code) plus phase-grouped lines. Authenticate the MCP HTTP request with Authorization: Bearer <key> or x-api-key.
Whoami — Show the API key this MCP connection uses: kind (legacy = full access, or scoped to one team), team, scopes, the scopes its owner's role still allows (effectiveScopes), expiry and last use. Call it before a write to check the key can do it. Authenticate with Authorization: Bearer <key> or x-api-key.
List Projects — List projects in the authenticated team. Authenticate the MCP HTTP request with Authorization: Bearer <key> or x-api-key.
Get Status — Get a project's remote status (slug, framework, production deployment, latest deployment). Pass the project slug from list_projects. Authenticate with Authorization: Bearer <key> or x-api-key.
Env Ls — List environment variable keys for a project, with the deploy target of each value (production, preview or all). Values are never returned. Authenticate with Authorization: Bearer <key> or x-api-key.
Env Set — Set an environment variable on a project, for production deploys, preview (branch) deploys, or all (default). A key may hold one value per target; a deploy uses its own target's value, else the all value. Use target production for secrets previews must not see. Does not restart the worker — a deploy is required to apply. Values are never echoed. Authenticate with Authorization: Bearer <key> or x-api-key.
Get your MCP into directories
A working endpoint is step one. Directory coverage is the coordinated launch across ChatGPT, Claude, Cursor, the MCP Registry, and community indexes.
Open-source edge deployment platform. Ship full-stack apps to the edge in seconds.
How do I connect Creek to my AI agent?
Use the MCP endpoint listed on this page in your MCP client configuration. One-click install pills support Claude, Cursor, VS Code, and other hosts. Copy the remote MCP URL if your client needs a manual entry.
How many tools does Creek provide?
Operate this server?
Request removal if you do not want Creek listed here, or claim the listing if you want to manage it on MCPBundles.
Operate Creek?
This server appears in the MCPBundles directory. Verify you operate it to take over the listing — name, description, logo, contact email, and skill content. We email a 6-digit code to a maintainer address your server publishes in /.well-known/security.txt or /.well-known/mcpbundles.json. Free, takes about a minute.
MCPBundles publishes this directory for MCP discovery. Except where we host or operate an offering, third-party services run under their own terms. Product and company names on this page are used in a descriptive, identifying way (including under nominative fair use where applicable); they remain the property of their owners. Nothing here grants you rights in those marks, and nothing here is an offer to sell a third party's services. Terms · Request removal
More in developer tools
Other MCP servers in this category from the directory index
Env Rm — Remove an environment variable from a project: one target's value (production, preview or all), or every value of the key when target is omitted. Does not restart the worker — a deploy is required to apply. Authenticate with Authorization: Bearer <key> or x-api-key.
Deploy Prod — Trigger a production deploy of the latest commit on the project's GitHub production branch (same as `creek deploy --from-github --prod`). Returns once the build is dispatched, with the new deploymentId when it can be found (within ~10 s) — then call wait_for_deployment (or get_deployment) with it, and get_build_log if it fails. Requires a GitHub connection on the project. Authenticate with Authorization: Bearer <key> or x-api-key.
List Deployments — List recent deployments for a project (newest first). Each row has branch and commitSha (to find the deployment a deploy_prod started), and triggerType so rollback can skip synthetic rollback rows. Authenticate with Authorization: Bearer <key> or x-api-key.
Get Deployment — Read one deployment: status (in flight: queued, building, uploading, deploying; final: active, failed, cancelled), terminal (true once the status is final), failedStep, errorCode / errorHint on failure, and the live url once active. Use the deploymentId from deploy_prod or list_deployments (8-char short id or full uuid). Authenticate with Authorization: Bearer <key> or x-api-key.
Wait For Deployment — Wait until a deployment finishes (active, failed or cancelled), polling for at most timeoutSeconds (default 45, max 300). Returns ok: true with the live url when it is active; error deployment_failed (with failedStep, errorCode, and nextStep get_build_log) or deployment_cancelled otherwise. If it is still running at the timeout, error timeout with retryable: true — call again. Keep timeoutSeconds below your client's tool-call timeout. Authenticate with Authorization: Bearer <key> or x-api-key.
Rollback — Roll production back to a previous active deployment. deploymentId is required — pick an active row from list_deployments whose triggerType is not rollback (implicit previous-production selection can land on a synthetic rollback row). Authenticate with Authorization: Bearer <key> or x-api-key.
List Resources — List all team-owned resources (databases, storage, cache, AI). Optionally filter by kind. Authenticate the MCP HTTP request with Authorization: Bearer <key> or x-api-key.
Create Resource — Create a new team-owned resource. The backing Cloudflare resource (D1/R2/KV) is auto-provisioned. Authenticate the MCP HTTP request with Authorization: Bearer <key> or x-api-key.
Attach Resource — Attach a team resource to a project under a given ENV var name (e.g. DB, STORAGE). The project's Worker will see it as env.<bindingName>. Authenticate the MCP HTTP request with Authorization: Bearer <key> or x-api-key.
Detach Resource — Remove a resource binding from a project. The resource itself is not deleted. Authenticate the MCP HTTP request with Authorization: Bearer <key> or x-api-key.
Delete Resource — Delete a team-owned resource. This is permanent: the D1 database or KV namespace behind it is queued for deletion with all its data, and an R2 bucket is deleted only if it is empty. Fails if any project still has a binding to it — detach first. Authenticate the MCP HTTP request with Authorization: Bearer <key> or x-api-key.
Rename Resource — Rename a team-owned resource. The stable UUID and all project bindings are preserved — only the display name changes. Authenticate the MCP HTTP request with Authorization: Bearer <key> or x-api-key.
Query Database — Execute a SQL query against a team-owned D1 database. Returns columns, rows, and metadata (changes, duration). Use list_resources to find the resourceId first. Authenticate the MCP HTTP request with Authorization: Bearer <key> or x-api-key.
MCPBundles probed 23 tools on the live server. The tool list on this page reflects what was discovered at the last refresh — connect your client to see the full set available to your session.
What authentication does Creek require?
Creek may require signing in to the provider before tools can run. Connect through MCPBundles or your MCP client and complete any provider login when prompted.
Don't want this listed?
Request removal from the MCPBundles directory. We stop publishing this listing on mcpbundles.com.
MCPBundles is an independent platform built on the open Model Context Protocol standard. MCPBundles is not affiliated with, sponsored by, or endorsed by Anthropic PBC.