Dawn is most useful when it shows up where work is already happening. For some teams that means Slack, Teams, or Telegram. For others it means the editor — Codex while pairing with a CLI agent, Cursor while navigating a codebase, or GitHub Copilot while reviewing a pull request.
Dawn now works as an MCP server. Connect your editor, and it can list your workspaces, discover the agents available in each one, start threads, send messages, and ask agents questions — all backed by the same connected sources, memory pages, and skills you have already configured. Nothing to rebuild.
Get Your API Credential
Open Dawn Web, go to your account menu, and select API credentials. Create a token and name it after the tool you are connecting — Codex, Cursor, or Copilot.
Dawn shows the raw token only once. It starts with dmcp_ and is tied to your personal account. Copy it immediately and store it the way you would store any other access credential. If you need to rotate it later, revoke and recreate from the same screen.
The MCP endpoint is your Dawn API origin followed by /mcp. In production that is https://api.dawnhq.ai/mcp.
What You Can Do Through MCP
Once connected, your editor can do everything you would normally do in a Dawn conversation:
List your workspaces. The MCP server returns all workspaces your account can access, with workspace names and IDs.
Discover agents. For any workspace, list the enabled agents along with their names and configuration. Pick the right agent for the question you have in mind.
Start a thread. Create a new conversation thread with a specific agent, optionally giving it a title. MCP threads are private to your account and tagged as MCP conversations in Dawn.
Send messages and read replies. Send a question to an existing thread and read the agent’s response, including any source citations. The agent uses the same connected repositories, tickets, documents, and memory pages it uses everywhere else.
Ask in one step. If you do not need to manage threads explicitly, the ask_agent action creates a thread and sends a message in a single call. That is usually the fastest way to get an answer from your editor.
The access is scoped to your account. Your editor sees the same workspaces and agents you see in Dawn Web. If you lose access to a workspace, the editor loses it too. If you revoke the token, the connection stops working immediately.
Connect Codex
Add this to ~/.codex/config.toml:
[mcp_servers.dawn]
url = "https://api.dawnhq.ai/mcp"
bearer_token_env_var = "DAWN_MCP_TOKEN"Set DAWN_MCP_TOKEN in your shell environment, restart Codex, and try:
Use the Dawn MCP server to list my workspaces, find the Platform agent, and ask it what changed in billing this week.
Codex is a strong fit because it lets you combine local code work with Dawn’s workspace-grounded knowledge. You can ask about how a service works while you are reading the code, check ticket status while planning a change, or ask the agent to explain a pattern you are looking at — without switching tools.
Connect Cursor
Add this to your mcp.json:
{
"mcpServers": {
"dawn": {
"url": "https://api.dawnhq.ai/mcp",
"headers": {
"Authorization": "Bearer ${env:DAWN_MCP_TOKEN}"
}
}
}
}Once configured, Cursor’s agent can use Dawn tools directly from chat. A practical prompt:
Use Dawn to find the right workspace and ask the Support agent which connected source explains the current escalation workflow.
That works well when the answer lives in Dawn’s connected sources rather than in the local repository alone.
Connect GitHub Copilot
Add this to .vscode/mcp.json:
{
"servers": {
"dawn": {
"type": "http",
"url": "https://api.dawnhq.ai/mcp",
"headers": {
"Authorization": "Bearer ${input:dawn-mcp-token}"
}
}
},
"inputs": [
{
"id": "dawn-mcp-token",
"type": "promptString",
"description": "Dawn MCP token",
"password": true
}
]
}Open Copilot Chat in Agent mode, enable the Dawn server, and try:
Use Dawn to list my workspaces, inspect the available agents in the product workspace, and ask the docs agent how scheduled tasks work.
Copilot will prompt for your token on first use. After that, it can reach your Dawn workspaces directly from VS Code.
MCP Threads Are Private
Conversations started through MCP are private to your account, following the same model as private channel conversations. They appear in Dawn under the MCP channel and do not show up in shared workspace conversation views. This means you can use your editor to ask quick questions without adding noise to your team’s shared channels.
If you want to continue an MCP conversation later, you can list your threads and send follow-up messages to the same thread ID. The agent retains the full conversation context.
When to Use MCP vs Other Channels
MCP is best for quick, targeted questions while you are already working in the editor. Ask about how something works while reading the code. Check the status of a ticket while planning a change. Ask the agent to explain a pattern or decision you are looking at.
For longer conversations, Slack or Dawn Web are still the better surface. For team-visible discussions, use a shared channel. MCP fills the gap between “I want to ask Dawn something” and “I do not want to leave my editor to do it.”