fastmcp.server.tasks.keys
Task key management for SEP-1686 background tasks.
Task keys encode security scoping and metadata in the Docket key format:
{session_id}:{client_task_id}:{task_type}:{component_identifier}
This format provides:
- Session-based security scoping (prevents cross-session access)
- Task type identification (tool/prompt/resource)
- Component identification (name or URI for result conversion)
Functions
build_task_key
{session_id}:{client_task_id}:{task_type}:{component_identifier}
The component_identifier is URI-encoded to handle special characters (colons, slashes, etc.).
Args:
session_id: Session ID for security scopingclient_task_id: Client-provided task IDtask_type: Type of task (“tool”, “prompt”, “resource”)component_identifier: Tool name, prompt name, or resource URI
- Encoded task key for Docket
build_task_key(“session123”, “task456”, “tool”, “my_tool”) ‘session123:task456:tool:my_tool’ build_task_key(“session123”, “task456”, “resource”, “file://data.txt”) ‘session123:task456:resource:file%3A%2F%2Fdata.txt’
parse_task_key
task_key: Encoded task key from Docket
- Dict with keys: session_id, client_task_id, task_type, component_identifier
parse_task_key(“session123:task456:tool:my_tool”){'session_id': 'session123', 'client_task_id': 'task456', 'task_type': 'tool', 'component_identifier': 'my_tool'}parse_task_key(“session123:task456:resource:file%3A%2F%2Fdata.txt”){'session_id': 'session123', 'client_task_id': 'task456', 'task_type': 'resource', 'component_identifier': 'file://data.txt'}
get_client_task_id_from_key
task_key: Full encoded task key
- Client-provided task ID (second segment)

