Power your agent
URL ของผู้เผยแพร่เอง ไม่ใช่เอนด์พอยต์ของ PlugMCP
Host a copy with our keys and logs.
https://mcp.dreamagent.cloud/mcpปุ่ม Claude ด้านบนจะเปิด Claude พร้อมกรอกชื่อและ URL ให้แล้ว คุณยังต้องยืนยันที่นั่นเอง
claude mcp add --transport http io.github.nivethaug-dreamagent https://mcp.dreamagent.cloud/mcpRun in a terminal.
{ "mcpServers": { "io.github.nivethaug-dreamagent": { "command": "npx", "args": [ "-y", "mcp-remote", "https://mcp.dreamagent.cloud/mcp" ] } }}claude_desktop_config.json
URL แบบรีโมตหรือคำสั่งบนเครื่องของคุณ? การติดตั้งสองแบบต่างกันอย่างไร
รันบน PlugMCP
A new server you create. It is not this listing's official endpoint. Use the publisher install when you want their URL and their credentials.
เปิดจากผู้เผยแพร่
Turn natural-language requests into deployed applications.
Connect ChatGPT, Claude, or any MCP client to DreamAgent — build websites, Telegram bots, Discord bots and schedulers from a conversation, watch them go live, then keep iterating.
streamable-http · OAuth 2.1 + PKCE · 24 tools · Python /
Build and deploy websites, Telegram and Discord bots from chat via the DreamAgent platform.
DreamAgent is an AI app-builder platform: you describe what you want, its agent writes the code, runs the tests, rebuilds, redeploys to production and commits to git — automatically. This MCP server exposes that power to your AI chat, so:
You: "Create a Telegram bot called WeatherBot — token
123:ABC— it replies with the weather when I send a city name."ChatGPT: creates it → polls → "WeatherBot is live."
You: "Add a /forecast command for 5-day forecasts."
ChatGPT: sends the edit → the agent codes, tests, redeploys → done.
Long operations are submit-then-poll — create → poll status, edit → poll progress. Every file change is committed and pushed automatically, so each edit lands in session history and version history (restorable). The agent handles code, tests, rebuild, redeploy and git commits by itself; prompts only describe the change.
With the official app (recommended): find DreamAgent in the ChatGPT app directory → Connect → sign in with your DreamAgent account (email or Google).
As a custom connector:
Claude → Settings → Connectors → Add custom connector:
DreamAgenthttps://mcp.dreamagent.cloud/mcpClick Connect, sign in with DreamAgent, done.
{
"mcpServers": {
"dreamagent": {
"type": "streamable_http",
"url": "https://mcp.dreamagent.cloud/mcp"
}
}
}
Auth is OAuth 2.1 (authorization-code + PKCE, RFC 7591 dynamic registration)
— or pass a DreamAgent API key as Authorization: Bearer da_... /
?key=da_....
<from Discord dev portal> —
it shows crypto prices with /price and /top commands"ChatGPT / Claude / Glama
│ MCP (streamable HTTP) + OAuth 2.1
▼
mcp.dreamagent.cloud ── this server (FastMCP)
│ per-request Bearer = the user's own DreamAgent API key
▼
api.dreamagent.cloud ── DreamAgent platform
└── agent writes code → tests → rebuild → deploy → git commit
Every request runs as the connected user — DreamAgent's ownership checks, plan limits and AI-credit billing apply exactly as in the dashboard.
da_...) at connect time — visible and revocable any time in
Settings → Connect to ChatGPT. Revoking disconnects that client instantly;
other clients keep working.Privacy: dreamagent.cloud/privacy · Terms: dreamagent.cloud/terms
Coming soon — a GIF of "Create a Telegram bot" end-to-end from ChatGPT.
The hosted endpoint (mcp.dreamagent.cloud) is the easiest way to connect.
To run your own:
git clone https://github.com/nivethaug/dreamagent-mcp-server
cd dreamagent-mcp-server
pip install -r requirements.txt
cp .env.example .env # optional: your account for local stdio mode
python server.py # stdio
python server.py --http --port 8800 # remote MCP (put behind HTTPS)
Hardening on the production host: the service runs under pm2 via
run-mcp.sh, which joins the dedicated cgroup dreamagent-mcp-egress.
Host firewall rules (/usr/local/sbin/mcp-egress-rules.sh, applied by the
mcp-egress-block.service systemd unit) block NEW connections from that
cgroup to all internal ranges (loopback/RFC1918/link-local/CGNAT/multicast,
v4+v6) while allowing DNS and public traffic — so screenshots can never
reach internal services, even through redirects or subresources.
System dependency — Chromium: the dreamagent_screenshot_website
tool renders pages with a system Chromium/Chrome binary (checked in order:
/usr/bin/chromium, /usr/bin/chromium-browser, /usr/bin/google-chrome,
then PATH). pip does not install it — on Debian/Ubuntu:
apt-get install -y chromium # or chromium-browser / google-chrome
Without it, every other tool works; the screenshot tool returns a clear "no headless chromium binary" error.
Three modes of authentication, in priority order per request:
Authorization: Bearer da_... header (OAuth clients / API clients)?key=da_... URL parameter (NoAuth custom connectors)DREAMAGENT_EMAIL / DREAMAGENT_PASSWORD env (personal self-host)Layout: server.py (tools) · oauth.py (OAuth 2.1 provider: /register,
/authorize, /token, /.well-known/*) · dreamagent_client.py (API
client) · auth.py (login mode) · plugin/ (Codex plugin package).
OAuth client registrations persist in oauth_clients.json; extend trusted
gateway callbacks via TRUSTED_OAUTH_REDIRECTS.
MIT
Build and deploy websites, Telegram and Discord bots from chat via the DreamAgent platform.
{ "mcpServers": { "io.github.nivethaug-dreamagent": { "url": "https://mcp.dreamagent.cloud/mcp", "headers": {} } }}เครื่องมือ
ยังไม่มีรายการเครื่องมือ เซิร์ฟเวอร์แบบรีโมตจะได้รายการหลังการตรวจสอบสถานะครั้งแรก
FAQ
คัดลอกคอนฟิก http สำหรับ Cursor, Claude Desktop, Claude Code หรือ VS Code ได้ในหน้านี้ คอนฟิกนี้ใช้การติดตั้งของผู้เผยแพร่ ไม่ใช่พร็อกซีของ PlugMCP
ระเบียนนี้ไม่ได้ระบุตัวแปรสภาพแวดล้อมที่จำเป็น
DreamAgent เข้าถึงได้ผ่าน HTTP
ตรวจสอบล่าสุดเมื่อ 2026-11-10 Build and deploy websites, Telegram and Discord bots from chat via the DreamAgent platform.
