get_session_details — ContextLayer MCP Tool Read-only
get_session_details
(get session details) is one of 62 tools on the
ContextLayer
MCP server. Connect the server and your client discovers it on the handshake.
by client
How to call get_session_details from your client
- Claude Code ContextLayer get_session_details run in your project directory
- Claude Desktop ContextLayer get_session_details ~/Library/Application Support/Claude/claude_desktop_config.json
- Cursor ContextLayer get_session_details ~/.cursor/mcp.json
- VS Code ContextLayer get_session_details .vscode/mcp.json
- Zed ContextLayer get_session_details ~/.config/zed/settings.json
- Windsurf ContextLayer get_session_details ~/.codeium/windsurf/mcp_config.json
- Cline ContextLayer get_session_details ~/Library/Application Support/Code/User/globalStorage/saoudrizwan.claude-dev/settings/cline_mcp_settings.json
- Gemini CLI ContextLayer get_session_details ~/.gemini/settings.json
- Grok ContextLayer get_session_details .mcp.json (in your project root)
- ChatGPT ContextLayer get_session_details Settings → Connectors → Advanced → Developer mode
- Claude.ai ContextLayer get_session_details Settings → Connectors → Add custom connector
- LangChain ContextLayer get_session_details pip install langchain-mcp-adapters
Fastest route
claude mcp add --transport http context-layer https://api.dotnova.io/mcpOther tools on this server
- accept_org_invite
- add_task_dependency
- add_team_member
- assign_task
- create_position
- create_project
- create_sprint
- create_task
- create_team
- delete_document
- delete_position
- delete_project
- delete_task
- delete_team
- delete_user
- end_session
- find_documents
- get_context
- get_context_routing
- get_document
- get_live_activity
- get_my_stats
- get_org_stats
- get_project_status
- get_team_details
- invite_user
- link_task_session
- link_team_project
- list_colleagues
- list_notifications
- list_pending_invites
- list_positions
- list_project_members
- list_project_teams
- list_projects
- list_sessions
- list_sprints
- list_tasks
- list_teams
- log_activity
- log_trace
- log_traces_batch
- mark_notification_read
- move_task_to_sprint
- remove_task_dependency
- remove_team_member
- remove_user_from_org
- search_entities
- set_context_routing
- setup_organization
- start_session
- unassign_task
- unlink_team_project
- update_org
- update_position
- update_project
- update_task
- update_team
- update_user
- upload_document
- whoami
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.