SSyncDev

Slotlock MCP Server

Calendars for AI agents: free/busy, next free slot, and bookings PostgreSQL never double-books.

Local serverstreamable-http

What is the Slotlock MCP Server?

Slotlock is an MCP integration. Calendars for AI agents: free/busy, next free slot, and bookings PostgreSQL never double-books.

Packages and local setup

The published oci package is ghcr.io/pilotaai/slotlock:0.12.3. Its declared MCP transport is streamable-http.

The package declares DATABASE_URL (required): postgres:// URL of a PostgreSQL 16 or newer database the container can reach, as a role that is not a superuser and has no BYPASSRLS: serve refuses one, since row-level security would not confine it. Without SLOTLOCK_MIGRATE_DATABASE_URL this role also applies the schema, so it must be able to create it.; SLOTLOCK_AUTH_TOKEN: Optional bearer token for SLOTLOCK_TENANT, with read and write (never admin): at least 32 random characters (openssl rand -hex 32). Leave it unset to accept only API keys (slotlock key create).; SLOTLOCK_CONFIRMATION_SECRET: Signs pending write confirmations: at least 32 random characters, different from the token. Required unless SLOTLOCK_CONFIRM_WRITES is none.; SLOTLOCK_METRICS_TOKEN: Serves Prometheus metrics at /metrics to this bearer token: at least 32 random characters, different from every other secret. Off without it.; PORT: Port the server listens on inside the container.; SLOTLOCK_MIGRATE_DATABASE_URL: postgres:// URL of the schema owner. When set, migration runs as this role and grants the DATABASE_URL role only what it needs at runtime.; SLOTLOCK_CONFIRM_WRITES: Writes that wait for a person to confirm them: none, all, or a comma-separated list of slotlock_create_event, slotlock_book_together, slotlock_book_pool, slotlock_update_event, slotlock_delete_event, slotlock_confirm_slot, slotlock_reschedule, slotlock_cancel. Listing one also guards the tool that makes the same write (slotlock_cancel with slotlock_delete_event, slotlock_reschedule with slotlock_update_event, slotlock_confirm_slot with slotlock_create_event). Clients without MCP 2026-07-28 form elicitation have guarded writes refused.; SLOTLOCK_AVAILABILITY: JSON array of weekly bookable-hours rules, e.g. [{"rrule":"FREQ=WEEKLY;BYDAY=MO,TU,WE,TH,FR","startMinutes":540,"durationMinutes":480}]. Without rules no slot is ever offered.; SLOTLOCK_REST_API: on: also serve the tools as a REST API under /v1, and the application API (resources, bookable hours, holds, reservations, coverage, maintenance) for admin keys, described by an OpenAPI 3.1 document at /openapi.json. Writes that wait for confirmation answer 428 there. off: MCP and A2A only.; SLOTLOCK_RETENTION_DAYS: Days of history kept: the change feed (who made each change included) and how far back a cursor reaches, and ended waitlist entries; retried writes are answered for at least 30 days whatever it is. 1-3650; default 30.; SLOTLOCK_SHARED_LIMITS: on: tenant request budgets (SLOTLOCK_LIMITS' tenant_ and app_) are shared by every server of a deployment through PostgreSQL, so N servers allow a tenant its rate once, not N times. off: each server keeps its own.; SLOTLOCK_WEBHOOKS: on: deliver each tenant's changes to its webhooks (POST /v1/webhooks), signed as Standard Webhooks; never to a private network address. private: those too, for testing. off: keep the change feed (GET /v1/changes), send nothing.; SLOTLOCK_TENANT: The tenant SLOTLOCK_AUTH_TOKEN acts in; API keys act in their own tenant..

This package has launch arguments in its registry record. Use the maintainer’s configuration for those arguments rather than launching it with only the package name.

Before connecting

Check the maintainer’s instructions for account access, authentication and the supported client configuration. Once connected, inspect the tools your client receives and try a small task that matches the server’s stated purpose. The registry description does not include a verified, complete tool list.

Project and source

View the publisher’s registry entry · Project repository · Project website. This profile uses version 0.12.3 from the registry. Registration identifies the publisher namespace; it does not establish that this is a first-party integration for every service it connects.

Browse related databases MCP servers for tools that cover the same kind of work.

Configuration

VariableDescriptionRequired
DATABASE_URLpostgres:// URL of a PostgreSQL 16 or newer database the container can reach, as a role that is not a superuser and has no BYPASSRLS: serve refuses one, since row-level security would not confine it. Without SLOTLOCK_MIGRATE_DATABASE_URL this role also applies the schema, so it must be able to create it.Yes
SLOTLOCK_AUTH_TOKENOptional bearer token for SLOTLOCK_TENANT, with read and write (never admin): at least 32 random characters (openssl rand -hex 32). Leave it unset to accept only API keys (slotlock key create).Check documentation
SLOTLOCK_CONFIRMATION_SECRETSigns pending write confirmations: at least 32 random characters, different from the token. Required unless SLOTLOCK_CONFIRM_WRITES is none.Check documentation
SLOTLOCK_METRICS_TOKENServes Prometheus metrics at /metrics to this bearer token: at least 32 random characters, different from every other secret. Off without it.Check documentation
PORTPort the server listens on inside the container.Check documentation
SLOTLOCK_MIGRATE_DATABASE_URLpostgres:// URL of the schema owner. When set, migration runs as this role and grants the DATABASE_URL role only what it needs at runtime.Check documentation
SLOTLOCK_CONFIRM_WRITESWrites that wait for a person to confirm them: none, all, or a comma-separated list of slotlock_create_event, slotlock_book_together, slotlock_book_pool, slotlock_update_event, slotlock_delete_event, slotlock_confirm_slot, slotlock_reschedule, slotlock_cancel. Listing one also guards the tool that makes the same write (slotlock_cancel with slotlock_delete_event, slotlock_reschedule with slotlock_update_event, slotlock_confirm_slot with slotlock_create_event). Clients without MCP 2026-07-28 form elicitation have guarded writes refused.Check documentation
SLOTLOCK_AVAILABILITYJSON array of weekly bookable-hours rules, e.g. [{"rrule":"FREQ=WEEKLY;BYDAY=MO,TU,WE,TH,FR","startMinutes":540,"durationMinutes":480}]. Without rules no slot is ever offered.Check documentation
SLOTLOCK_REST_APIon: also serve the tools as a REST API under /v1, and the application API (resources, bookable hours, holds, reservations, coverage, maintenance) for admin keys, described by an OpenAPI 3.1 document at /openapi.json. Writes that wait for confirmation answer 428 there. off: MCP and A2A only.Check documentation
SLOTLOCK_RETENTION_DAYSDays of history kept: the change feed (who made each change included) and how far back a cursor reaches, and ended waitlist entries; retried writes are answered for at least 30 days whatever it is. 1-3650; default 30.Check documentation
SLOTLOCK_SHARED_LIMITSon: tenant request budgets (SLOTLOCK_LIMITS' tenant_ and app_) are shared by every server of a deployment through PostgreSQL, so N servers allow a tenant its rate once, not N times. off: each server keeps its own.Check documentation
SLOTLOCK_WEBHOOKSon: deliver each tenant's changes to its webhooks (POST /v1/webhooks), signed as Standard Webhooks; never to a private network address. private: those too, for testing. off: keep the change feed (GET /v1/changes), send nothing.Check documentation
SLOTLOCK_TENANTThe tenant SLOTLOCK_AUTH_TOKEN acts in; API keys act in their own tenant.Check documentation