MCP.DEEPLOGIC.SO

Ship it to DeepLogic

A remote MCP server that lets Claude publish a vibe-coded project straight from the conversation to a live URL — each project in its own Docker container, listed in the Innovation Center gallery.

Open the Lab gallery → Connect a client

CONVERSATION → CONTAINER

you › “publish this to DeepLogic” claude › publish_project(name, description, files…) mcp.deeplogic.so › detecting stack · building image · starting container live at deeplogic.so/lab/<slug>/

Connect

ENDPOINThttps://mcp.deeplogic.so/<secret>/mcp

Replace <secret> with the access key — ask Michael for it; it is never published on this page. The key in the URL is the auth: no OAuth, no extra headers.

claude.ai · desktop

Settings → Connectors
Add custom connector
Name DeepLogic Lab, paste the endpoint URL, add.

Claude Code

claude mcp add \
  --transport http \
  deeplogic-lab \
  <endpoint URL>

Codex CLI

# ~/.codex/config.toml
[mcp_servers.deeplogic_lab]
url = "<endpoint URL>"

Older Codex builds without native HTTP support can bridge via npx mcp-remote <endpoint URL> as a stdio server.

Tools

publish_project

Publish or republish a project (name, description, files[], optional start_command). Auto-detects: Dockerfile → built as-is · package.json → Node 22 · requirements.txt / app.py → Python 3.12 · otherwise static. Returns the live URL.

list_projects

Everything currently in the Lab, with live/stopped status.

get_logs

Container logs for a project — Claude reads them, fixes the bug, republishes.

unpublish_project

Stop the container and remove the project.

Rules of the Lab

Apps are served under /lab/<slug>/ — use relative asset paths.
Server apps must listen on process.env.PORT || 8080.
Republishing with the same name replaces the project at the same URL.
Per container: 0.5 CPU · 512 MB RAM · 5 MB payload · max 20 live projects.

This is a demo playground, not production hosting. Containers are isolated and resource-capped, and anything can be unpublished at any time.