get_task_session — Daystruct MCP Tool Read-only
get_task_session
(get task session) 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 get_task_session from your client
- Claude Code Daystruct get_task_session run in your project directory
- Claude Desktop Daystruct get_task_session ~/Library/Application Support/Claude/claude_desktop_config.json
- Cursor Daystruct get_task_session ~/.cursor/mcp.json
- VS Code Daystruct get_task_session .vscode/mcp.json
- Zed Daystruct get_task_session ~/.config/zed/settings.json
- Windsurf Daystruct get_task_session ~/.codeium/windsurf/mcp_config.json
- Cline Daystruct get_task_session ~/Library/Application Support/Code/User/globalStorage/saoudrizwan.claude-dev/settings/cline_mcp_settings.json
- Gemini CLI Daystruct get_task_session ~/.gemini/settings.json
- Grok Daystruct get_task_session .mcp.json (in your project root)
- ChatGPT Daystruct get_task_session Settings → Connectors → Advanced → Developer mode
- Claude.ai Daystruct get_task_session Settings → Connectors → Add custom connector
- LangChain Daystruct get_task_session pip install langchain-mcp-adapters
Fastest route
claude mcp add --transport http daystruct https://api.daystruct.ai/mcpOther 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
- record_task_event
- 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.