DOCUMENTATION · ORGANIZER TOOLS

Your community.
Connected to your AI assistant.

Kommunity Organizer MCP lets an AI assistant work with your community’s events, registrations and program. Connect once, choose the permissions, and stay in control.

Connect with Claude

01 / GET STARTED

Connect your community

Available in the Claude directory.Open Kommunity Organizer in Claude to connect without entering a custom server URL. Sign in to Kommunity, select the community you organize, and approve the permissions you need.

You need a Kommunity account with an organizer role in at least one community, and an AI assistant that supports remote MCP servers with OAuth. The hosted connection requires no local installation or API secret.

REMOTE MCP SERVER · HTTPShttps://api.kommunity.com/api/mcp/organizer

Choose your connection. In Claude, open the Kommunity Organizer directory listing and connect. For a custom MCP connection, use the server URL above. In ChatGPT, use the custom MCP connection option available to your account.
Use OAuth sign-in. If your host asks how to register the OAuth client, choose automatic registration (Dynamic Client Registration). Sign in to Kommunity when prompted.
Choose one community and its permissions. Select the community you organize and explicitly approve the scopes your assistant needs. Start with read permissions for an exploratory connection.
Start with a small task. Ask the assistant to discover its capabilities and list your upcoming events. It can only use the tools allowed by your connection.

One connection, one community. To work with another community, create a separate connection. Each connection creates its own community credential; your existing integrations keep their credentials.

Configuration for hosts that accept JSON

Use this with an OAuth-capable remote MCP host. Follow its sign-in flow after adding the configuration.

{
  "mcpServers": {
    "kommunity-organizer": {
      "url": "https://api.kommunity.com/api/mcp/organizer"
    }
  }
}

FOR MCP HOSTS & AGENTS

Discover and connect

Kommunity Organizer is published in the Claude connector directory. Other OAuth-capable MCP hosts can discover the endpoint and sign-in flow using these public files.

MCP server card — transport and server capabilities.
Agent skills index — connection instructions and verified file digest.
AI capability catalog — MCP, skills and Developer API references.
Authentication guide — client registration, organizer consent and revocation.

Browsers that support WebMCP expose public search, navigation and connection information. Managing community data still requires an approved Organizer MCP connection.

02 / ORGANIZER TOOLS

What you can do

The connector uses Kommunity’s community-scoped Developer API. Available tools reflect your granted permissions; community plans and feature settings are checked when an operation runs.

Events

Read events, create drafts, update details, and publish or cancel with the required permissions.

Event program

Manage speakers, tracks, sessions, sponsors, talks, photos and call-for-papers submissions.

Registrations

Review applications, manage RSVPs and waiting lists, and configure registration questions.

Tickets & check-in

Manage ticket types and discount codes, issue tickets, and record or undo check-ins.

Reports & exports

Read event statistics, export permitted event data, and track background operations.

Capabilities & audit

Discover the connection’s permissions and constraints, and inspect its mutation audit records.

Payments, checkout, orders, refunds, community products and end-user actions are excluded. Ticket cancellation through MCP cannot initiate a refund. Zoom account connection and KLive feature activation require a human organizer.

03 / YOUR CONTROL

Permissions & privacy

Signing in does not give the assistant unrestricted access. You choose the community and permissions on the consent screen. Reading events, changing registrations, publishing and exporting data have separate scopes.

Community boundary: the connection only accesses its selected community. The approving user must retain an organizer role for OAuth access to continue.
Explicit write access: viewing events does not grant permission to edit or publish them. Tool availability is not a substitute for your authorization of a task.
Private event data: attendee details, registration answers and exports may contain personal information. Grant those scopes only to an assistant you intend to use with that data; results are returned to the connected AI host.
Revoke at any time: open your community’s Developer → Clients panel in the organizer console and revoke the credential created for the MCP connection. Revocation immediately stops access.
Reduce access: reducing the credential’s permissions immediately reduces MCP access. Adding permissions later cannot exceed the scopes originally approved during OAuth consent; reconnect to approve broader access.

Read our Privacy Policy and Terms of Service for how Kommunity handles platform data. Your AI host’s policies also apply to data it receives.

04 / PUT IT TO WORK

Example workflows

READ EVENTS

“List my community’s upcoming events, then show the speakers and agenda for the next one.”

The assistant discovers its permissions, reads your community’s events, and uses the returned event ID to retrieve its program.

CREATE A DRAFT

“Help me create a draft workshop. Ask for the details you need, and leave it unpublished.”

With event write permission, the assistant can create a draft and read it back to verify the result. Publishing requires a separate permission and your intent.

REVIEW REGISTRATIONS

“Show the registration and waiting-list counts for my next event, then summarize its check-in status.”

The assistant reads only the registration, waiting-list and check-in information allowed by your connection.

For changes and larger tasks

The normal workflow is discover → read → preview where required → execute → verify. Before writing, the assistant should read the kommunity://organizer/guide resource. Destructive lifecycle actions and certain bulk changes require previews. Background operations must be polled until they finish, and partial outcomes need to be checked individually.

Some actions send the same notifications as the organizer panel. Preview and review side effects before a change. For supported writes, retry the same intended operation with the same idempotency key; a new key means a new operation.

05 / INTEGRATION DETAILS

For developers

Transport: Streamable HTTP over HTTPS
Authentication: OAuth authorization code with PKCE S256 and Dynamic Client Registration
Access tokens: One hour; bound to the Organizer MCP resource
Refresh tokens: Rotating; valid for up to 30 days
Workflow resource: kommunity://organizer/guide

OAuth discovery endpoints

An unauthenticated MCP request returns HTTP 401 with a discovery challenge. Hosts discover the registration, authorization and token endpoints from the metadata. MCP OAuth tokens cannot be used as general Developer API tokens.

Local adapter and existing API clients

For hosts that require a local stdio adapter, download the Organizer MCP bundle. Extract it, install dependencies in tools/organizer-mcp with Node.js 22 or later, and follow its included setup guide. Keep the bundled docs/ and tools/ directories together.

Hosts supporting custom HTTP headers can also use an existing community client via X-Kommunity-Client-Id and X-Kommunity-Client-Secret. Store credentials in your host’s secret storage. Never put secrets in a URL, prompt or shared configuration file.

For endpoint parameters and the full API contract, open your community’s Developer → API tab in the organizer console. It includes request examples, an OpenAPI download and a guide for AI agents.

06 / GET UNSTUCK

Troubleshooting

I cannot select my community

Sign in with an account that has an organizer role in that community. If your role was removed after connecting, ask a community administrator to restore the appropriate access or revoke the connection.

A tool is missing or permission is denied

Ask the assistant to discover its current capabilities. Check the connection’s approved scopes and the client’s current grants in Developer → Clients. Reconnect to approve scopes beyond the original consent. Community plan and feature constraints may still prevent an operation.

A request is rate limited or a write times out

For HTTP 429, wait for the indicated Retry-After interval. If a write supports idempotency, retry with the same key and unchanged payload. For file uploads and other writes without replay support, read the resulting state before retrying to avoid duplicates.

An export or report is incomplete

Poll background operations until completion and check each result. Paginate list responses and narrow filters when a result is truncated. Private export downloads expire 24 hours after completion.

Need a hand?

Contact [email protected] with the operation, error and request ID if available. Keep access tokens, client secrets and attendee data out of your message.