Pack local or remote codebases into AI-friendly files that LLMs and coding agents can read or search
Nothing to run from here
DreamAgent is installed from its publisher's own source and answers where it runs, so this marketplace is not in the path of a single call. There is no address here to send one to, and a panel that pretended otherwise would be showing you an answer we made up. Install it and call it from your own client — the Installation tab has the entry for each one.
24
tools declared
—
trust score
remote
at its publisher
—
calls last 7d
What it does
Build and deploy websites, Telegram and Discord bots from chat via the DreamAgent platform.
Quickstart
# 1 — add it to Claude Code
claude mcp add --scope user --transport http dreamagent-mcp https://mcp.dreamagent.cloud/mcp
# 2 — ask your agent for something these tools do
# dreamagent_list_projects, dreamagent_list_global_integrations, dreamagent_list_project_env and 21 more
DreamAgent costs nothing on mcprush: there is no plan to choose here, no cap to set and nothing mcprush can bill you for.
Publishernot claimed
NIAll 1 server
nivethaug1 server
1 category
Collected from a public index. Nobody has claimed this account, so nothing here was written by its author — claim it if it is yours.
Installation
Where are you running it?
Every route below installs the same thing and ends at the same approval screen. Nothing here runs on your machine and nothing runs on ours: this server answers at its publisher’s own address, and what you install is the connection straight to it.
Claude Codedeclared by this listing
This is a public server: it answers at its publisher’s own address and this marketplace is not in the path. Claude Code registers it in one command; --scope user makes it available in every project. The transport below is http, as the publisher's own manifest declares it.
claude mcp add --scope user --transport http dreamagent-mcp https://mcp.dreamagent.cloud/mcpReconnect, or start a new session, and the tools appear in the model’s tool list.
Free on mcprush, and it answers at its publisher’s own address: this marketplace is not in the path, so there is no key of ours to hold and no card to add.
What it writes
One config entry pointing straight at the publisher’s own address — this marketplace is not in the path, and nothing from this listing executes on your machine.
What you approve
24 tools, with what each one reads, writes and reaches shown before you agree — the same list on every route above. Read the tool surface.
Tool surface
What the model actually sees. Descriptions are diffed on every release — see version history.
List the user's DreamAgent projects. Returns each project's name, ID, type, status, and live domain (when available). Use when the user asks to see, find, select, or check their projects — and ALWAYS before modifying a project when its ID is not already known (resolve names to IDs here first).
| Parameter | Type | Required | Notes |
|---|---|---|---|
| status | no | optional exact-match filter (e.g. 'ready', 'failed'). During creation, projects report intermediate phases (creating/building/deploying/…), so filtering by 'creating' does not match every in-progress |
List the user's saved credentials (Global Integrations). ALWAYS call this before creating any bot project or asking the user for a token/API key. Saved credentials are referenced BY ID when creating projects: bot_token_integration_id for bot tokens, global_integration_ids for other keys. Secret values are never returned — only IDs and metadata (type, key name, verified, title). If nothing suitab
No parameter schema on file.
List a project's environment variables with their details. Shows each key's name, title, description, docs URL, and category — values are masked (secrets are never returned). Use to see which integrations a project already has before adding more, or to answer "what keys does my project have?". These are PROJECT-SPECIFIC variables — distinct from the user's Global Integrations — API-key credentia
| Parameter | Type | Required | Notes |
|---|---|---|---|
| project_id | integer | yes | the project to inspect. |
List DreamAgent Superpowers — the account's ready-made AI tools (song/video/image generation, voiceover, lip sync, voice clone, transcription, media processing, PDF tools) with their enabled state and beta pricing. Read-only; no credits consumed. Use when the user asks what AI tools/superpowers are available, whether a specific tool is enabled, or what they can add to a project. Tools shown as en
No parameter schema on file.
List the file tree of a DreamAgent project (source files only — hidden files like .env are excluded). Use before reading or editing a file to find the correct path.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| project_id | integer | yes | — |
Read a source file from a DreamAgent project. file_path is the project-relative path (from dreamagent_list_files), e.g. "src/pages/Home.tsx" or "telegram/main.py". Hidden files (.env) and binaries are not readable.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| project_id | integer | yes | — |
| file_path | string | yes | — |
WRITE ACTION — make SMALL targeted changes to an EXISTING file in a DreamAgent project via exact search/replace. PREFERRED over dreamagent_write_file for editing existing files: you send only the changed fragments (never the whole file) — cheaper, immune to payload size/safety blocks in the calling client, and cannot corrupt unchanged code. Use dreamagent_write_file only to CREATE files or for ful
| Parameter | Type | Required | Notes |
|---|---|---|---|
| project_id | integer | yes | project containing the file. |
| file_path | string | yes | project-relative path of the EXISTING file to edit. |
| edits | array | yes | list of edit objects: {"find": "<exact existing text>", "replace": "<new text>", "all": false} # optional: replace every occurrence |
| confirm | boolean | no | must be true to execute. |
| auto_commit | boolean | no | commit+push and record version history after saving (default true; pass false to batch several edit_file calls and finish with one dreamagent_commit_push). |
WRITE ACTION — overwrite or create one source file in a DreamAgent project with the exact content given. For CHANGING an existing file, prefer dreamagent_edit_file (small targeted find→replace edits — no need to send the whole file). By default the write is immediately committed and pushed to the project's GitHub repo and recorded in its session history & version history (so the user can restore/r
| Parameter | Type | Required | Notes |
|---|---|---|---|
| project_id | integer | yes | — |
| file_path | string | yes | — |
| content | string | yes | — |
| confirm | boolean | no | — |
| auto_commit | boolean | no | — |
Git diff of one project file against the last commit — shows the pending (not yet live) changes. Free, read-only. Use after edits to review exactly what changed before rebuilding.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| project_id | integer | yes | — |
| file_path | string | yes | — |
WRITE ACTION — delete one source file from a DreamAgent project. Hidden/credential files (.env, .git, keys) are rejected. By default the deletion is immediately committed and pushed (so it is recorded in session history & version history) — deleted files stay recoverable via git history / version restore. CONFIRM BEFORE CALLING — tell the user which file will be deleted and call only with confirm
| Parameter | Type | Required | Notes |
|---|---|---|---|
| project_id | integer | yes | — |
| file_path | string | yes | — |
| confirm | boolean | no | — |
| auto_commit | boolean | no | — |
WRITE ACTION — commit ALL pending changes in a DreamAgent project and push them to its private GitHub repo. The commit gets its own entry in the project's session history and version history, so the user can restore/revert to it in the DreamAgent dashboard. Use it to (a) commit several MCP writes/deletes as ONE version — write and delete with auto_commit=false first — or (b) retry a commit after
| Parameter | Type | Required | Notes |
|---|---|---|---|
| project_id | integer | yes | project to commit |
| message | string | no | short commit message, e.g. "Add pricing page hero section" (default "MCP edit: project <id>") |
| confirm | boolean | no | must be true to execute |
Version history of a DreamAgent project — recent commits (hash, message, status, timestamp) from its persistent commit log, newest first. Use it to review what changed and when; the user can restore any version from the DreamAgent dashboard version-history UI (mention the short hash so they can find it).
| Parameter | Type | Required | Notes |
|---|---|---|---|
| project_id | integer | yes | — |
| limit | integer | no | — |
WRITE ACTION — build & publish a DreamAgent project: rebuilds the app from the current source files and pushes the new version live. Use after finishing file edits (dreamagent_write_file) so the user's changes go live. Pro/paid accounts only. CONFIRM BEFORE CALLING — tell the user the project will be rebuilt and redeployed, and call only with confirm=true after they agree. ASYNCHRONOUS: kick-off
| Parameter | Type | Required | Notes |
|---|---|---|---|
| project_id | integer | yes | — |
| confirm | boolean | no | — |
WRITE ACTION — redesign a website project's UI to match a design image. Website projects only. The user provides an image (screenshot, mockup, AI-generated design) and instructions. You generate the image (e.g. DALL-E), encode it as base64, and send it here. DreamAgent's AI will read the image and redesign the project's frontend to match. CONFIRM BEFORE CALLING — show the user: 1. The project be
| Parameter | Type | Required | Notes |
|---|---|---|---|
| project_id | integer | yes | the website project to redesign. |
| image_base64 | string | yes | base64-encoded design reference image (PNG/JPG/WEBP). Send the actual image bytes verbatim — the image IS the spec. |
| instructions | string | yes | keep this SHORT — e.g. "Match this design image exactly." The image carries the design; do NOT write a long textual design spec duplicating what is visible in the image. Only add brief must-have requi |
| confirm | boolean | no | must be true to execute. |
WRITE ACTION — creates a new DreamAgent project (website, Telegram bot, Discord bot, or AI agent). Use ONLY when the user clearly asks to create/build a new project; not for questions about what to build. CONFIRM BEFORE CALLING — never create on the first mention. In ONE message, present and get the user's explicit go-ahead for: 1. The credential: run dreamagent_list_global_integrations first.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| name | string | yes | project name (max 30 chars; a public subdomain is auto-generated). |
| project_type | string | yes | website / telegrambot / discordbot / agent. |
| description | no | the build request (what + for whom + features/tone). | |
| env_vars | no | optional non-secret environment variables. | |
| bot_token_integration_id | no | REQUIRED for telegrambot & discordbot — saved-credential ID (see dreamagent_list_global_integrations). | |
| global_integration_ids | no | optional saved-key IDs to import as env vars. | |
| confirm | boolean | no | must be true to execute — the call is REJECTED without it. |
Check a project's creation/deployment state. Terminal states are 'ready' (built and live) and 'failed'; while a project is being created it reports progressive phases such as 'creating', 'building', 'deploying', or 'ai_provisioning' — treat any non-terminal status as still building. Use after dreamagent_create_project (poll until ready or failed) and whenever the user asks whether a project is rea
| Parameter | Type | Required | Notes |
|---|---|---|---|
| project_id | integer | yes | the project to check. |
WRITE ACTION — builds, modifies, or fixes an EXISTING project with a natural-language instruction. Use ONLY when the user clearly asks for a change ("add X", "fix Y", "change the theme"). If the user is only asking for advice, analysis, review, or suggestions ("what could be improved?", "review my bot"), do NOT call this — answer from the project's info instead; a review request is not an edit. D
| Parameter | Type | Required | Notes |
|---|---|---|---|
| project_id | integer | yes | the project to modify. |
| message | string | yes | the desired change (what + any behavioral constraints). |
| session_key | no | optional — continue a specific development session. | |
| new_session | boolean | no | optional — start a fresh session for a new topic. |
List a project's development sessions (conversation threads). Returns each session's identifier (session key) and context so you can select, continue, or monitor a specific development session — pass the session key to dreamagent_chat to continue that thread or to dreamagent_get_chat_status to monitor it. The session key is a reference used to address a session; it is not an authentication credent
| Parameter | Type | Required | Notes |
|---|---|---|---|
| project_id | integer | yes | the project. |
Create a new development session for a project — a separate conversation with its own context. Use when the user wants to start a distinct development topic. A new session does NOT replace or affect the existing project — earlier sessions remain available.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| project_id | integer | yes | the project. |
| label | string | no | optional name for the session. |
RECOVERY-ONLY — releases a project's editing lock when a stale or abandoned session blocks new modifications. NOT a normal editing step, and NEVER a way to bypass an actively running edit. The lock state is not machine-readable from here: to judge staleness, check dreamagent_get_edit_progress — if no edit is active but dreamagent_chat still fails with a lock error, the lock is stale. Confirm with
| Parameter | Type | Required | Notes |
|---|---|---|---|
| project_id | integer | yes | the project to unlock. |
Check the progress and final status of a specific AI development session using its session key. Use this to monitor an asynchronous edit until it completes, fails, or is cancelled — keep checking until a terminal state. The session key comes from dreamagent_chat or dreamagent_list_sessions and is an identifier, not a secret. Returns (actual fields): 'active=', 'run_status=', 'next_after=' (cursor
| Parameter | Type | Required | Notes |
|---|---|---|---|
| session_key | string | yes | the session key returned by dreamagent_chat. |
| after | integer | no | cursor from the previous check (0 on the first check). |
Check the latest AI edit progress for a project using its project identifier — no session key needed: the project id retrieves the session holding the latest edit. Use when the user asks whether their edit is finished, when the session key isn't available (e.g. a new conversation), and BEFORE starting any new edit. Returns (actual fields): 'session_key=' (the identifier of the session this progre
| Parameter | Type | Required | Notes |
|---|---|---|---|
| project_id | integer | yes | the project being edited. |
DESTRUCTIVE — stops an AI edit that is currently running. Use ONLY when the user explicitly asks to stop/cancel the active edit. After cancellation, do NOT claim the requested change was completed — report that it was stopped. Returns 'Cancellation requested: <backend message>' — e.g. 'Query cancelled', 'Cancellation requested' (durable run), or 'No active query found'. Afterwards poll dreamagent
| Parameter | Type | Required | Notes |
|---|---|---|---|
| session_key | string | yes | the session key of the running edit. |
WEBSITE PROJECTS ONLY — capture a screenshot of a DreamAgent-hosted page by URL: a deployed project's domain (e.g. my-app.dreamagent.cloud or a connected custom domain) or dreamagent.cloud itself. Best for checking a project's live pages after edits or deploys and reviewing layouts — returns the PNG as an MCP image content block PLUS a public URL. Non-DreamAgent URLs are rejected (this is enforced
| Parameter | Type | Required | Notes |
|---|---|---|---|
| url | string | yes | absolute http(s) URL of the page to capture |
| width | integer | no | viewport width 320-1920 (default 1280) |
| height | integer | no | viewport height 240-2160 (default 800) |
Free
$0 forever
- Every tool — any call limit is its publisher’s, not ours
- No card, and mcprush charges nothing for it
- Runs at its publisher’s own address — this marketplace is not in the path
- Nothing to cap, because mcprush bills nothing
What counts against your monthly calls
| Tool | Unit | Calls used | Out of the allowance |
|---|
Nothing here is billable: mcprush charges nothing to install DreamAgent or to call it, at any volume.
Call allowance · this installenforced at the gateway
Monthly allowance, in calls
—
—
Alert at 80% · then the tool returns a normal MCP error
Used this month: —
—Grade not published
No rule-by-rule report on file for this release
Two independent axes, because powerful and malicious are different questions. The grade is threat only. The capability level is blast radius, and it is never a penalty on the grade — it is priced as one subtract-only term in the score, where you can see it.
This listing is an address its publisher runs, and you connect to it directly — this marketplace is not in the path. The scanner reads packages and public source, and an address is neither: the repository linked on this page is where this record was collected from, not a copy of what the address serves, so it is not graded in its place. So there is no grade — not a withheld one, an unmeasured one.
Release history
This is an address its publisher runs: which release it serves is theirs to choose, so there is nothing here to pin. The history below is for reading; the current release on file is 1.0.0.
1.0.0
undated
latestNo release note was published with this version.
—
no reviews yet
Who can review
One review per account, from a signed-in account that does not publish this listing. Nothing else is asked — you can say what you think before you install it. Publishers can reply once per review, and a review can be edited or deleted by whoever wrote it.
Sign in to write one
Any signed-in account that does not publish DreamAgent can review it, once — before installing it or after. A review from an account that has installed it is marked as one.
No reviews yet
Nobody has reviewed this listing. The rating on the card is the mean of the reviews written here and nothing else, so there is no rating until somebody writes the first — which takes a signed-in account that does not publish it, and nothing else.