> ## Documentation Index
> Fetch the complete documentation index at: https://docs.tightknit.ai/llms.txt
> Use this file to discover all available pages before exploring further.

# Add events with the MCP

> Use an AI agent connected to the Tightknit MCP server to create events in bulk and publish them to your community events page.

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](https://docs.tightknit.ai/integrations/mcp.md).
* The Admin role, or the **MCP User** role plus a role that can manage events.

> [!TIP]
>
> If your agent supports skills (for example, Claude Code, Cursor, or Codex), install the [Tightknit plugin](https://github.com/TightknitAI/tightknit-mcp-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](https://docs.tightknit.ai/community-site/pages.md#events-list) only when all of the following are true:

| Requirement | Tool and field |
| - | - |
| The event status is **published**. New events are drafts by default. | `status: published` on `create_event` or `edit_event` |
| The event is published to the site. On by default for events that aren't unlisted. | `publish_to_site` |
| The event isn't unlisted. Off by default. | `is_unlisted` |
| The events page is published on your site. You only need to set this once. | `route_events_enabled` on `edit_site_pages`. Check the current value with `get_site`. |

> [!NOTE]
>
> 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.

```text Create and publish a list of events theme={null}
Add these events to my Tightknit community and publish them to the community
site's events page. All times are in America/New_York.

1. Product AMA, Nov 12 2026, 1:00 to 2:00 PM, Zoom link https://zoom.us/j/123456789
2. Customer Roundtable, Nov 19 2026, 11:00 AM to 12:00 PM, online
3. NYC Meetup, Dec 3 2026, 6:00 to 8:30 PM, 123 Main St, New York

Use Tightknit registration for all of them, and don't announce them in Slack.
Before creating anything, show me the list of events you're about to create
so I can confirm. Afterwards, give me the link to each event on the site.
```

```text Create drafts first, publish later theme={null}
Read the attached spreadsheet of events and create each one in Tightknit as a
draft. Use the "Timezone" column for start and end times and the "Register" column
as the registration link. When you're done, list the drafts with their Studio links
so I can review them. Don't publish anything until I say so.
```

After you review the drafts, send:

```text Publish the reviewed drafts theme={null}
Publish all of the draft events you just created to the community site.
```

## 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](https://docs.tightknit.ai/integrations/luma.md).
* **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](https://docs.tightknit.ai/integrations/mcp.md#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](https://docs.tightknit.ai/tags/getting-started.md) 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](https://docs.tightknit.ai/integrations/mcp.md#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](https://docs.tightknit.ai/events/global-event-settings.md).

## Related

> [card] [Create a new event](https://docs.tightknit.ai/events/create-event.md)
>
> Create a single event in Studio or Slack.

> [card] [Event registration](https://docs.tightknit.ai/events/event-registration.md)
>
> How registration, reminders, and attendance work.


## Related topics

- [MCP Server](https://docs.tightknit.ai/integrations/mcp.md)
- [Event Registration](https://docs.tightknit.ai/events/event-registration.md)
- [Getting Started with Content Resource Libraries](https://docs.tightknit.ai/content-resource-library/getting-started.md)
- [Event Recaps & Recordings](https://docs.tightknit.ai/events/event-recap.md)
- [Global Event Settings](https://docs.tightknit.ai/events/global-event-settings.md)


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.