MCP (Model Context Protocol) is an open standard that lets AI assistants call external services as tools. LineBundle’s MCP server exposes your organisation’s data — events, spaces, bookings, contacts, places, and automation rules — as callable tools.
Server URL
Setup
Available Tools
All tools are scoped to your organisation and subject to the permissions of the token used.Events
List, fetch, and create events. Supports date-range filtering, pagination, and visibility controls.Tools:
events__ListEvents, events__GetEvent, events__CreateEventSpaces
Browse spaces, their members, and linked events.Tools:
spaces__ListSpaces, spaces__GetSpace, spaces__CreateSpace, spaces__ListSpaceMembers, spaces__ListSpaceEventsBookings
List and create bookings for places.Tools:
bookings__ListBookings, bookings__GetBooking, bookings__CreateBookingContacts
Read and create contacts within your organisation.Tools:
contacts__ListContacts, contacts__GetContact, contacts__CreateContactPlaces
List bookable venues and retrieve place details.Tools:
places__ListPlaces, places__GetPlaceAutomation
View automation rules, inspect execution history, and trigger rules on demand.Tools:
automation__ListRules, automation__GetRule, automation__CreateRule, automation__ExecuteRule, automation__ListExecutionsAuthentication
All MCP requests are authenticated with the samesk_lb_… token used by the REST API and TypeScript SDK. The token is sent as a standard Authorization: Bearer header — the MCP client handles this automatically once configured.
Token permissions apply: if a token was created with read-only permissions, write tools like events__CreateEvent will return 403. See Credentials for permission scopes.
Troubleshooting
Further Reading
API Tokens
Create and manage machine credentials
TypeScript SDK
Programmatic access via the auto-generated SDK
REST API Reference
Full OpenAPI-generated endpoint documentation
Automation
Trigger and inspect automation rules via MCP or API