MCP Server
DreamAgent
io.github.nivethaug/dreamagent
What this MCP does
Creates, edits, monitors, and deploys websites, Telegram bots, Discord bots, and schedulers through the DreamAgent development platform.
Capabilities
Tools
12
tools
dreamagent_cancel_chat
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_get_chat_status /
dreamagent_get_edit_progress until run_status reports 'cancelled'.
Destructive
Input schema
{'type': 'object', 'required': ['session_key'], 'properties': {'session_key': {'type': 'string', 'description': 'the session key of the running edit.'}}, 'additionalProperties': False}
Output schema
{'type': 'object', 'required': ['result'], 'properties': {'result': {'type': 'string'}}, 'x-fastmcp-wrap-result': True}
dreamagent_chat
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.
Describe ONLY the desired change â DreamAgent's AI automatically
handles code, tests, rebuild, and redeployment. Completed changes
are saved and committed automatically.
ASYNCHRONOUS: returns immediately with the session_key; monitor
with dreamagent_get_edit_progress (or dreamagent_get_chat_status
with the returned session key) until a terminal state. Report
success only after run_status reaches 'completed'. Edits consume
the user's AI credits.
ERRORS (actual returns): failures come back as text starting with
'ERROR:'. If the edit was rejected before starting, the text says
'the edit was NOT started' plus the reason â HTTP 402 insufficient
credits, 409 another edit already active, 423 session lock held by
another session, 404 wrong project id, 401 no account connected.
Treat the edit as failed/cancelled only when a status tool says so.
ONE EDIT AT A TIME: never start another modification on the same
project while one is running â check progress first and wait.
Open world
Input schema
{'type': 'object', 'required': ['project_id', 'message'], 'properties': {'message': {'type': 'string', 'description': 'the desired change (what + any behavioral constraints).'}, 'project_id': {'type': 'integer', 'description': 'the project to modify.'}, 'new_session': {'type': 'boolean', 'default': False, 'description': 'optional â\x80\x94 start a fresh session for a new topic.'}, 'session_key': {'anyOf': [{'type': 'string'}, {'type': 'null'}], 'default': None, 'description': 'optional â\x80\x94 continue a specific development session.'}}, 'additionalProperties': False}
Output schema
{'type': 'object', 'required': ['result'], 'properties': {'result': {'type': 'string'}}, 'x-fastmcp-wrap-result': True}
dreamagent_create_project
WRITE ACTION â creates a new DreamAgent project (website, Telegram
bot, Discord bot, or scheduler). 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.
If several telegram/discord credentials are saved, list them
(id + title) and ask which to use. If exactly one is saved,
state which one you will use. Never pick silently.
2. The plan: name, type, and the final description exactly as you
will submit it (this is the Prompt Assistant's recommendation
summary). Call this tool only after the user confirms.
CREATION IS ASYNCHRONOUS: after calling, check
dreamagent_get_project_status repeatedly until the project is
'ready' or 'failed' (bots ~2-5 min, websites longer).
CREDENTIALS: raw bot tokens are never accepted in chat or as inputs.
For Telegram/Discord bots you MUST pass bot_token_integration_id â
the ID of a saved credential from dreamagent_list_global_integrations.
If none is saved, direct the user to dreamagent.cloud â Settings â
Global Integrations. Other saved keys can be imported via
global_integration_ids. Credentials are stored as project secrets
and are never exposed back.
DESCRIPTION = the refined creation brief. Act as a Creative
Director / Product Manager, not an architect.
Create a concise but complete description of WHAT should be built:
- product vision and target audience
- user experience and core functionality
- design/tone direction
- important features and behavior
- final expected result
Do not include implementation details such as:
- technology stack
- architecture
- database/API implementation
- authentication implementation
- deployment
- CI/CD
- testing commands
Infer reasonable defaults when missing details are non-critical.
Ask for clarification only when missing information materially
affects the requested functionality, scope, credentials, or
expected result.
Prefer the following structure and constraints for each project
type, but do not override explicit user requirements:
Website:
- Project Vision
- Design Style
- Pages
- Hero Experience
- Core Features
- UI Components
- Mobile Experience
- Final Expectation
- Prefer up to 4 pages unless the user clearly requires more.
Telegram bot:
- Bot Purpose
- Commands
- User Flow
- Optional AI Features
- Integrations when required
- Final Expectations
- Prefer a compact command set; always include /start and /help
unless the user's explicit requirements conflict.
Discord bot:
- Bot Purpose
- Slash Commands
- Events
- Permissions
- Optional AI Features
- Final Expectations
- Prefer a compact command set; include /help where appropriate.
Scheduler:
- Job Purpose
- Data Sources
- Schedule
- Delivery Channels
- Message Format
- Final Expectations
- Use concrete schedules and specify failure/timeout behavior.
Open world
Input schema
{'type': 'object', 'required': ['name', 'project_type'], 'properties': {'name': {'type': 'string', 'description': 'project name (max 30 chars; a public subdomain is auto-generated).'}, 'env_vars': {'anyOf': [{'type': 'object', 'additionalProperties': True}, {'type': 'null'}], 'default': None, 'description': 'optional non-secret environment variables.'}, 'description': {'anyOf': [{'type': 'string'}, {'type': 'null'}], 'default': None, 'description': 'the build request (what + for whom + features/tone).'}, 'project_type': {'type': 'string', 'description': 'website / telegrambot / discordbot / scheduler.'}, 'global_integration_ids': {'anyOf': [{'type': 'array', 'items': {}}, {'type': 'null'}], 'default': None, 'description': 'optional saved-key IDs to import as env vars.'}, 'bot_token_integration_id': {'anyOf': [{'type': 'integer'}, {'type': 'null'}], 'default': None, 'description': 'REQUIRED for telegrambot & discordbot â\x80\x94\nsaved-credential ID (see dreamagent_list_global_integrations).'}}, 'additionalProperties': False}
Output schema
{'type': 'object', 'required': ['result'], 'properties': {'result': {'type': 'string'}}, 'x-fastmcp-wrap-result': True}
dreamagent_create_session
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.
Input schema
{'type': 'object', 'required': ['project_id'], 'properties': {'label': {'type': 'string', 'default': 'ChatGPT', 'description': 'optional name for the session.'}, 'project_id': {'type': 'integer', 'description': 'the project.'}}, 'additionalProperties': False}
Output schema
{'type': 'object', 'required': ['result'], 'properties': {'result': {'type': 'string'}}, 'x-fastmcp-wrap-result': True}
dreamagent_get_chat_status
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 for the next check), optional 'new_output:' (text produced
since the last check), then either "Still working â poll again" or
a terminal 'done=true' line: finished (with the final output tail),
'the edit was NOT started: <reason>' (rejected early, e.g. HTTP 402
insufficient credits), or 'stream error' (the connection to the run
broke â the server-side run may still have finished; verify with
dreamagent_get_edit_progress).
run_status values: queued | running | cancel_requested | completed |
failed | cancelled | interrupted | unknown.
Read only
Input schema
{'type': 'object', 'required': ['session_key'], 'properties': {'after': {'type': 'integer', 'default': 0, 'description': 'cursor from the previous check (0 on the first check).'}, 'session_key': {'type': 'string', 'description': 'the session key returned by dreamagent_chat.'}}, 'additionalProperties': False}
Output schema
{'type': 'object', 'required': ['result'], 'properties': {'result': {'type': 'string'}}, 'x-fastmcp-wrap-result': True}
dreamagent_get_edit_progress
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 progress comes from), 'edit_active=', 'run_status=',
'chunks=' (output size so far), optional 'recent_output (tail):',
and a terminal 'result:' line: finished (with the final output
tail), 'the edit was NOT started: <reason>' (rejected early,
e.g. HTTP 402 insufficient credits), 'stream error', or 'no run is
currently active'.
run_status values: queued | running | cancel_requested | completed |
failed | cancelled | interrupted | unknown.
Distinct from dreamagent_get_project_status: project status =
creation/deployment state (creating/ready/failed); edit progress =
current AI modification state; chat status (dreamagent_get_chat_status)
monitors one specific session by its session key. If edit_active is
true, do NOT launch another edit for the same project.
Read only
Input schema
{'type': 'object', 'required': ['project_id'], 'properties': {'project_id': {'type': 'integer', 'description': 'the project being edited.'}}, 'additionalProperties': False}
Output schema
{'type': 'object', 'required': ['result'], 'properties': {'result': {'type': 'string'}}, 'x-fastmcp-wrap-result': True}
dreamagent_get_project_status
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 ready or live.
NOTE: this reports the PROJECT's build/deploy state â NOT AI edit
progress. For edits use dreamagent_get_edit_progress.
Read only
Input schema
{'type': 'object', 'required': ['project_id'], 'properties': {'project_id': {'type': 'integer', 'description': 'the project to check.'}}, 'additionalProperties': False}
Output schema
{'type': 'object', 'required': ['result'], 'properties': {'result': {'type': 'string'}}, 'x-fastmcp-wrap-result': True}
dreamagent_list_global_integrations
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 suitable is saved: direct the user to dreamagent.cloud â
Settings â Global Integrations to add it (one-time, verified,
reusable). Never ask the user to paste tokens in chat.
Read only
Input schema
{'type': 'object', 'properties': {}, 'additionalProperties': False}
Output schema
{'type': 'object', 'required': ['result'], 'properties': {'result': {'type': 'string'}}, 'x-fastmcp-wrap-result': True}
dreamagent_list_project_env
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 (dreamagent_list_global_integrations).
Read only
Input schema
{'type': 'object', 'required': ['project_id'], 'properties': {'project_id': {'type': 'integer', 'description': 'the project to inspect.'}}, 'additionalProperties': False}
Output schema
{'type': 'object', 'required': ['result'], 'properties': {'result': {'type': 'string'}}, 'x-fastmcp-wrap-result': True}
dreamagent_list_projects
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).
Read only
Input schema
{'type': 'object', 'properties': {'status': {'anyOf': [{'type': 'string'}, {'type': 'null'}], 'default': None, 'description': "optional exact-match filter (e.g. 'ready', 'failed').\nDuring creation, projects report intermediate phases\n(creating/building/deploying/â\x80¦), so filtering by 'creating'\ndoes not match every in-progress project."}}, 'additionalProperties': False}
Output schema
{'type': 'object', 'required': ['result'], 'properties': {'result': {'type': 'string'}}, 'x-fastmcp-wrap-result': True}
dreamagent_list_sessions
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
credential or a secret.
Read only
Input schema
{'type': 'object', 'required': ['project_id'], 'properties': {'project_id': {'type': 'integer', 'description': 'the project.'}}, 'additionalProperties': False}
Output schema
{'type': 'object', 'required': ['result'], 'properties': {'result': {'type': 'string'}}, 'x-fastmcp-wrap-result': True}
dreamagent_release_project_lock
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 the user before releasing if they may have the project
open elsewhere.
Input schema
{'type': 'object', 'required': ['project_id'], 'properties': {'project_id': {'type': 'integer', 'description': 'the project to unlock.'}}, 'additionalProperties': False}
Output schema
{'type': 'object', 'required': ['result'], 'properties': {'result': {'type': 'string'}}, 'x-fastmcp-wrap-result': True}
History
Recent tool changes
Added
dreamagent_cancel_chat
Sept. 17, 2026, 12:45 p.m.
Added
dreamagent_get_edit_progress
Sept. 17, 2026, 12:45 p.m.
Added
dreamagent_get_chat_status
Sept. 17, 2026, 12:45 p.m.
Added
dreamagent_release_project_lock
Sept. 17, 2026, 12:45 p.m.
Added
dreamagent_create_session
Sept. 17, 2026, 12:45 p.m.
Added
dreamagent_list_sessions
Sept. 17, 2026, 12:45 p.m.
Added
dreamagent_chat
Sept. 17, 2026, 12:45 p.m.
Added
dreamagent_get_project_status
Sept. 17, 2026, 12:45 p.m.
Added
dreamagent_create_project
Sept. 17, 2026, 12:45 p.m.
Added
dreamagent_list_project_env
Sept. 17, 2026, 12:45 p.m.
Added
dreamagent_list_global_integrations
Sept. 17, 2026, 12:45 p.m.
Added
dreamagent_list_projects
Sept. 17, 2026, 12:45 p.m.
Discover
Similar MCP servers
TinyFn
io.tinyfn/tinyfn
Offers deterministic utility functions for mathematics, conversions, validation, hashing, encoding, arrays, dates, colors, and pa…
hyperion
com.thetempleofdoom.hyperion/hyperion
Acts as a paid MCP tool marketplace and utility gateway with server discovery, HTTP and JavaScript tools, research, data conversi…
Andreax
io.github.moralito311-andr/andreax
Offers pay-per-call AI services for inference, agent and workflow design, OCR and transcription, code generation and review, clas…
Vee3
io.github.Vee3io/vee3
Manages Clerk authentication infrastructure, including users, organizations, domains, sessions, tokens, OAuth, SSO, machines, per…
Courier
io.github.trycourier/courier
Provides notification delivery infrastructure for users, tenants, lists, templates, preferences, journeys, automations, brands, a…
GripForge
io.github.gripforgeai/mcp
Generates, rigs, animates, analyzes, and packages game characters, weapons, armor, effects, environments, and engine-ready assets.
IA-QA — 130+ QA & Dev Tools for AI Agents
io.github.JcJamet/ia-qa-toolbox
Provides deterministic QA, evaluation, testing, code analysis, prompt and RAG checks, model comparison, and web security diagnost…
apis-io
io.apis/apis-io
Provides catalog search, comparison, scoring, enrichment, lists, and dataset exports for APIs, providers, specifications, workflo…