Create an MCP server with task support pre-configured.
Sets up the server with a taskStore (defaults to InMemoryTaskStore) and
declares tasks capability. Publishers can then use registerAdcpTaskTool()
or server.experimental.tasks.registerToolTask() directly.
This uses the higher-level McpServer API. Publishers with complex dispatch
patterns (e.g., custom request routing) can use the lower-level Server class
directly by passing taskStore in ServerOptions and using setRequestHandler
for task lifecycle methods. See the MCP SDK docs for that approach.
Create an MCP server with task support pre-configured.
Sets up the server with a
taskStore(defaults toInMemoryTaskStore) and declares tasks capability. Publishers can then useregisterAdcpTaskTool()orserver.experimental.tasks.registerToolTask()directly.This uses the higher-level
McpServerAPI. Publishers with complex dispatch patterns (e.g., custom request routing) can use the lower-levelServerclass directly by passingtaskStoreinServerOptionsand usingsetRequestHandlerfor task lifecycle methods. See the MCP SDK docs for that approach.