Productivity
deerdawn.com
Manages DeerDawn projects and subprojects for tracking codebases and initiatives.
ENDPOINT 1
https://api.deerdawn.com/api/v1/mcp
MCP server metadata
- Name
- deerdawn-mcp
- Version
- 1.0.0
DeerDawn is your authoritative session memory — the brief your AI reads before every session. Ground your work in it: load it first, keep it current, and rely on it instead of re-deriving what it already knows. Always call `start_session` before your first response — it is required to load current project context and sync files. Do not answer project questions or run repo search until it has run. Use DeerDawn before repo search for orientation and known paths. Use repo search only when you need file-level or symbol-level resolution DeerDawn does not yet know. When `start_session` returns a "Since last session" catch-up, open with AT MOST two sentences: the most meaningful change anchored in time ("Last session (yesterday) you shipped X"), then the open thread as an offer ("Y is still open — want to pick that up?"). Then stop and let the user steer. Do not recite the full brief or list every field. If nothing changed, confirm readiness in one line. Never invent progress, decisions, or landmines not in the payload; state gaps as fact, never as reproach — no streak language. Call `update_context(project_id, summary)` as soon as a decision is made, a task changes, or a feature ships — do not wait for end of session. Track work on the task board with `manage_todos`: file cards and move them across Backlog → Blocked → In Progress → Integration → Testing → Done (use `action:"move"` with a `phase`) instead of keeping an ad-hoc list. Read the board with `get_context(sections=["board"])`. Repo structure is stored once, not re-derived. Before searching the codebase, read `get_project_map` / `find_known_paths` / `search_context`. Do a full exploration only if the structure has not been logged yet. After exploring, or whenever you discover a durable path or fact, append it: `record_hot_paths` (files/folders), `record_debug_finding` (bugs/handoffs), `upsert_workspace_entities` (services, patterns, decisions). Append nodes incrementally — never re-derive or rewrite the whole map. `get_workspace_entities` — architecture/decisions. `import_local_context` — first open with no context. `cleanup_context(complete_task=true)` — when task is done.
Known tools 23
list_projectsList all your DeerDawn projects with their current task and project ID.
Inferred read-onlycreate_projectCreate a new DeerDawn project to track a codebase, feature, or initiative.
Potential side effectsswitch_subprojectSet which subproject is active for this codebase, so start_session, update_context, and manage_todos target it by default.
Inferred read-onlyarchive_projectArchive a dead or finished project so it stops cluttering list_projects and never auto-resolves as the active project.
Inferred read-onlyset_project_parentRe-parent an existing project: nest it under a top-level umbrella by passing parent_project_id, or promote it back to top-level by omitting parent_project_id.
Inferred read-onlyget_contextGet the current context for a specific project — task, status, decisions, goals, and open questions.
Inferred read-onlymanage_todosManage the active project's task board — a scrum-style board where every task is a card that moves across phase columns: Backlog → Blocked → In Progress → Integration → Testing → Done.
Inferred read-onlyget_workspace_overviewGet a full overview of your workspace — all projects, durable knowledge, and capabilities.
Inferred read-onlyget_project_mapReturn the durable project map: hot paths, entrypoints, named surfaces, and recent debugging notes.
Inferred read-onlyfind_known_pathsSearch durable path memory (hot paths, surfaces, debugging notes) before doing a repo-wide search.
Inferred read-onlyget_workspace_entitiesQuery typed workspace knowledge — services, capabilities, patterns, environments, and workflows — for architecture-level orientation.
Inferred read-onlyrecord_hot_pathsRecord durable file/folder hot paths AFTER you discover them, so future sessions find them before searching.
Inferred read-onlyupsert_workspace_entitiesCreate or update typed workspace entities (services, capabilities, patterns) and relationships.
Potential side effectsrecord_debug_findingRecord a durable debugging finding, optionally tied to file paths and a commit/diff ref, after diagnosing a bug or tracing a non-obvious handoff.
Inferred read-onlymark_resolvedMark a knowledge or decision entity as resolved so it stops appearing in normal context loads.
Inferred read-onlyget_next_best_contextReturn the most relevant next context to fetch or use for the current task/session, including open questions and pending decisions ranked for relevance and token efficiency.
Inferred read-onlyCONNECT WITH APPROVAL
Client installation
Review this server and its permissions before adding it. Secret placeholders must be set locally.
Codex
~/.codex/config.toml
[mcp_servers.deerdawn-mcp]
url = "https://api.deerdawn.com/api/v1/mcp"
enabled = true
Claude Code
.mcp.json
{
"mcpServers": {
"deerdawn-mcp": {
"type": "http",
"url": "https://api.deerdawn.com/api/v1/mcp"
}
}
}
Claude Desktop
Settings → Connectors → Add custom connector
Name: deerdawn-mcp
Remote MCP URL: https://api.deerdawn.com/api/v1/mcp
Add this remote URL as a custom connector in Claude Desktop. Availability depends on the user plan and workspace policy.
Cursor
.cursor/mcp.json
{
"mcpServers": {
"deerdawn-mcp": {
"url": "https://api.deerdawn.com/api/v1/mcp"
}
}
}
Visual Studio Code
.vscode/mcp.json
Add to Visual Studio Code{
"servers": {
"deerdawn-mcp": {
"type": "http",
"url": "https://api.deerdawn.com/api/v1/mcp"
}
}
}
Generic MCP
Client-specific MCP configuration
{
"name": "deerdawn-mcp",
"transport": "streamable-http",
"url": "https://api.deerdawn.com/api/v1/mcp"
}
MCP Inspector
Run the official MCP Inspector locally and enter the indexed Streamable HTTP endpoint.
ENDPOINT 2
https://api.deerdawn.com/mcp
Known tools 0
No tool metadata was available in the registry cache.
CONNECT WITH APPROVAL
Client installation
Review this server and its permissions before adding it. Secret placeholders must be set locally.
Codex
~/.codex/config.toml
[mcp_servers.deerdawn-com]
url = "https://api.deerdawn.com/mcp"
enabled = true
bearer_token_env_var = "MCP_BEARER_TOKEN"
Authentication is required. Replace the placeholder locally and never commit a secret.
Claude Code
.mcp.json
{
"mcpServers": {
"deerdawn-com": {
"type": "http",
"url": "https://api.deerdawn.com/mcp",
"headers": {
"Authorization": "Bearer YOUR_BEARER_TOKEN"
}
}
}
}
Authentication is required. Replace the placeholder locally and never commit a secret.
Claude Desktop
Settings → Connectors → Add custom connector
Name: deerdawn-com
Remote MCP URL: https://api.deerdawn.com/mcp
Add the URL as a custom connector, then complete its supported authorization flow. Claude Desktop remote connectors are configured in the UI.
Cursor
.cursor/mcp.json
{
"mcpServers": {
"deerdawn-com": {
"url": "https://api.deerdawn.com/mcp",
"headers": {
"Authorization": "Bearer YOUR_BEARER_TOKEN"
}
}
}
}
Authentication is required. Replace the placeholder locally and never commit a secret.
Visual Studio Code
.vscode/mcp.json
{
"servers": {
"deerdawn-com": {
"type": "http",
"url": "https://api.deerdawn.com/mcp",
"headers": {
"Authorization": "Bearer ${input:mcp-token}"
}
}
},
"inputs": [
{
"type": "promptString",
"id": "mcp-token",
"description": "deerdawn-com bearer token",
"password": true
}
]
}
Authentication is required. Replace the placeholder locally and never commit a secret.
Generic MCP
Client-specific MCP configuration
{
"name": "deerdawn-com",
"transport": "streamable-http",
"url": "https://api.deerdawn.com/mcp",
"headers": {
"Authorization": "Bearer YOUR_BEARER_TOKEN"
}
}
Authentication is required. Replace the placeholder locally and never commit a secret.
MCP Inspector
Run the official MCP Inspector locally and enter the indexed Streamable HTTP endpoint.
TRUST AND VERIFICATION EVIDENCE
Trust Data Available
BuiltWith Trust API v2 evidence for deerdawn.com was fetched 2026-08-11T10:02:07.623Z.
deerdawn.com is assessed as Trusted: Domain has an established technology history spanning over a year.
Evidence is source-attributed and does not guarantee that a third-party server is safe. Risk labels are conservative metadata heuristics.