record_task_event — Daystruct MCP Tool
record_task_event
(record task event) is one of 23 tools on the
Daystruct
MCP server. Connect the server and your client discovers it on the handshake.
by client
How to call record_task_event from your client
- Claude Code Daystruct record_task_event run in your project directory
- Claude Desktop Daystruct record_task_event ~/Library/Application Support/Claude/claude_desktop_config.json
- Cursor Daystruct record_task_event ~/.cursor/mcp.json
- VS Code Daystruct record_task_event .vscode/mcp.json
- Zed Daystruct record_task_event ~/.config/zed/settings.json
- Windsurf Daystruct record_task_event ~/.codeium/windsurf/mcp_config.json
- Cline Daystruct record_task_event ~/Library/Application Support/Code/User/globalStorage/saoudrizwan.claude-dev/settings/cline_mcp_settings.json
- Gemini CLI Daystruct record_task_event ~/.gemini/settings.json
- Grok Daystruct record_task_event .mcp.json (in your project root)
- ChatGPT Daystruct record_task_event Settings → Connectors → Advanced → Developer mode
- Claude.ai Daystruct record_task_event Settings → Connectors → Add custom connector
- LangChain Daystruct record_task_event pip install langchain-mcp-adapters
Fastest route
claude mcp add --transport http daystruct https://api.daystruct.ai/mcp
Other tools on this server
- daystruct_status
- search_entities
- get_entity_evidence
- get_context_contract
- answer_software_questions
- check_security_exposure
- lookup_vulnerability
- check_release_support
- select_model
- read_recent_evidence_changes
- compat_check
- get_compat_verify_kit
- get_daystruct_validated_guidance
- list_daystruct_guidance_scopes
- resolve_task_capabilities
- create_task_session
- get_task_session
- close_task_session
- search_daystruct_library
- resolve_daystruct_bundle
- discover_daystruct_capabilities
- prepare_daystruct_capabilities
This list was read from the server itself, by connecting to it and calling tools/list on 24 September 2026. It is what
the server actually exposes, not what its listing claims.
Mutating and Read-only are read off each tool's name, not its schema — a hint, not a guarantee. The registry stores tool names only; connect the server for its live schemas.