Skip to main content
Use the Tightknit MCP server to create several events at once from a list, a spreadsheet, or another calendar, and publish them to your community site’s events page.

Prerequisites

  • The Tightknit MCP server connected to your agent.
  • The Admin role, or the MCP User role plus a role that can manage events.
If your agent supports skills (for example, Claude Code, Cursor, or Codex), install the Tightknit plugin and run /tightknit:import-events. The skill collects event details, checks for duplicates, creates the events as drafts, and confirms your events page is published.

When an event appears on the events page

An event is listed on your site’s events page only when all of the following are true:
A draft can have publish_to_site: true. The event still doesn’t appear on the site until its status is published.

Example prompts

Copy a prompt into your agent and replace the details with your own.
Create and publish a list of events
Create drafts first, publish later
After you review the drafts, send:
Publish the reviewed drafts

Create events in bulk

1

Provide the event details

Each event requires a title, start time, and end time. Optional fields include description, location, video call or registration link, cover image, hosts, speakers, and tags.Always include a timezone. The agent sends times as ISO 8601 timestamps with an offset, so a missing timezone can put events at the wrong time.
2

Choose a registration method

If you don’t specify one, the agent asks. The options are:
  • Tightknit registration: Members select Register on the site or in Slack. Tightknit tracks attendance and sends reminders.
  • External registration link: The Register button opens a URL you provide, such as a form in another system. Ask the agent to use the registration button as a link.
  • Luma: Provide the Luma URL that includes the event’s evt- ID so members can register on the event page. See Luma.
  • No registration: No Register button is shown.
3

Decide whether to announce in Slack

The agent can post an announcement to the Slack channels you choose when each event is published. Skip announcements for large batches or past events to avoid flooding channels.
4

Review and publish

Ask the agent to create the events as drafts and share their Studio links, or to confirm the list with you before it creates anything. Publishing is a separate step, so nothing goes live until you approve it.To publish later, give the agent a date and time and it schedules each draft.
5

Verify the events

create_event returns the event’s url on your community site once the event is live, or null if it isn’t. Ask the agent for the list of events and links, and open one to check it.

Notes

  • Reminders: Published events send Slack reminders to hosts, speakers, and registrants by default. Ask the agent to change the reminder times or turn them off. Drafts don’t send reminders.
  • Cover images: The agent can upload a cover image from a file you provide. Its sandbox needs network access to the Tightknit upload domain. See Files.
  • Tags: The agent can add existing tags by label. If a tag doesn’t exist, the call fails and no event is created. Ask the agent to run list_tags first, or create the tags beforehand.
  • Tool approvals: Some clients ask you to approve each tool call. For long lists, allow the Tightknit tools for the conversation.
  • Rate limits: Each event counts as one write, and writes are limited to 60 per minute. The agent may pause partway through a long list. See Rate limits.
  • Unpublishing: To remove an event from the site, ask the agent to set it back to draft. Deleting an event is permanent and also deletes its registrations.
  • Global event settings: Cover image shape, the unregister option, the Add to Calendar button, and the registration button label apply to all events. Change them with edit_event_settings or in global event settings.

Create a new event

Create a single event in Studio or Slack.

Event registration

How registration, reminders, and attendance work.