Skip to main content
Glama
liveblocks
by liveblocks

update-notification-settings

Manage and customize notification preferences for Liveblocks users by updating user-specific settings to control alert types and frequencies.

Instructions

Update Liveblocks notification settings

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
dataYes
userIdYes

Implementation Reference

  • Handler function for the 'update-notification-settings' tool. Note: It destructures only 'userId', ignores 'data', and calls 'getNotificationSettings' instead of an update method (possible bug).
    async ({ userId }, extra) => { return await callLiveblocksApi( getLiveblocks().getNotificationSettings( { userId }, { signal: extra.signal } ) ); }
  • Input schema for 'update-notification-settings' tool using Zod, defining 'userId' and 'data' as a nested record of notification types to booleans.
    { userId: z.string(), data: z.record( z.string(), z.record( z.union([ z.literal("thread"), z.literal("textMention"), z.string().regex(/^\$/, { message: "String must start with '$'", }), ]), z.boolean() ) ), },
  • src/server.ts:774-801 (registration)
    Full registration of the 'update-notification-settings' tool via McpServer.tool(), including description, inline schema, and handler.
    server.tool( "update-notification-settings", "Update Liveblocks notification settings", { userId: z.string(), data: z.record( z.string(), z.record( z.union([ z.literal("thread"), z.literal("textMention"), z.string().regex(/^\$/, { message: "String must start with '$'", }), ]), z.boolean() ) ), }, async ({ userId }, extra) => { return await callLiveblocksApi( getLiveblocks().getNotificationSettings( { userId }, { signal: extra.signal } ) ); } );

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/liveblocks/liveblocks-mcp-server'

If you have feedback or need assistance with the MCP directory API, please join our Discord server