Sessionize
MCP server for accessing Sessionize event data. Query speakers, sessions, and schedules from any Sessionize-powered conference using natural language.
README
Sessionize MCP Server
<a href="https://glama.ai/mcp/servers/@jeanlopezxyz/Sessionize"> <img width="380" height="200" src="https://glama.ai/mcp/servers/@jeanlopezxyz/Sessionize/badge" alt="Sessionize MCP server" /> </a>
A Model Context Protocol (MCP) server for accessing Sessionize event data - speakers, sessions, and schedules from any Sessionize-powered conference.
Built with Quarkus MCP Server.
Quick Start
npx mcp-sessionize@latest
Table of Contents
Sessionize API Setup
Before using this MCP server, you need to enable the public API for your Sessionize event.
Step 1: Access Your Event Dashboard
- Log in to Sessionize
- Select your event from the dashboard
- Navigate to API / Embed in the left sidebar
Step 2: Enable the API
- In the API section, toggle Enable API to ON
- Choose the data visibility options:
- Speakers - Enable to expose speaker information
- Sessions - Enable to expose session details
- Schedule - Enable to expose the event schedule
Step 3: Get Your Event ID
Your Event ID is displayed in the API endpoint URLs. It looks like this:
https://sessionize.com/api/v2/{EVENT_ID}/view/All
The {EVENT_ID} is an alphanumeric string (e.g., abc123xy).
Step 4: Test the API
Verify your API is working by opening these URLs in your browser:
- All data:
https://sessionize.com/api/v2/{EVENT_ID}/view/All - Speakers:
https://sessionize.com/api/v2/{EVENT_ID}/view/Speakers - Sessions:
https://sessionize.com/api/v2/{EVENT_ID}/view/Sessions - Schedule:
https://sessionize.com/api/v2/{EVENT_ID}/view/GridSmart
If you see JSON data, your API is ready to use.
Important Notes
- The API only exposes accepted sessions and their speakers
- Draft or rejected sessions are not included
- Schedule data is only available if you've configured time slots in Sessionize
- The API is read-only and does not require authentication
Installation
Claude Code
Option 1: CLI (Recommended)
claude mcp add sessionize -e SESSIONIZE_EVENT_ID="your-event-id" -- npx -y mcp-sessionize@latest
Option 2: Global Settings
Add to ~/.claude/settings.json:
{
"mcpServers": {
"sessionize": {
"command": "npx",
"args": ["-y", "mcp-sessionize@latest"],
"env": {
"SESSIONIZE_EVENT_ID": "your-event-id"
}
}
}
}
Option 3: Project Settings
Add to .claude/settings.local.json in your project:
{
"mcpServers": {
"sessionize": {
"command": "npx",
"args": ["-y", "mcp-sessionize@latest"],
"env": {
"SESSIONIZE_EVENT_ID": "your-event-id"
}
}
}
}
After adding, restart Claude Code to load the MCP server.
Claude Desktop
Add to your Claude Desktop configuration file:
macOS: ~/Library/Application Support/Claude/claude_desktop_config.json
Windows: %APPDATA%\Claude\claude_desktop_config.json
{
"mcpServers": {
"sessionize": {
"command": "npx",
"args": ["-y", "mcp-sessionize@latest"],
"env": {
"SESSIONIZE_EVENT_ID": "your-event-id"
}
}
}
}
Restart Claude Desktop after saving.
VS Code
Run this command in your terminal:
code --add-mcp '{"name":"sessionize","command":"npx","args":["-y","mcp-sessionize@latest"],"env":{"SESSIONIZE_EVENT_ID":"your-event-id"}}'
Or add manually to your VS Code MCP settings.
Cursor
Add to your Cursor MCP configuration (mcp.json):
{
"mcpServers": {
"sessionize": {
"command": "npx",
"args": ["-y", "mcp-sessionize@latest"],
"env": {
"SESSIONIZE_EVENT_ID": "your-event-id"
}
}
}
}
Windsurf
Add to your Windsurf MCP configuration:
{
"mcpServers": {
"sessionize": {
"command": "npx",
"args": ["-y", "mcp-sessionize@latest"],
"env": {
"SESSIONIZE_EVENT_ID": "your-event-id"
}
}
}
}
Goose CLI
Add to config.yaml:
extensions:
sessionize:
command: npx
args:
- -y
- mcp-sessionize@latest
env:
SESSIONIZE_EVENT_ID: your-event-id
SSE Mode
Run as a standalone HTTP server for web integrations or multiple clients:
npx mcp-sessionize@latest --port 9080 --event-id your-event-id
Endpoints:
- SSE:
http://localhost:9080/mcp/sse - Streamable HTTP:
http://localhost:9080/mcp
Docker
docker run -p 9080:9080 -e SESSIONIZE_EVENT_ID=your-event-id ghcr.io/jeanlopezxyz/mcp-sessionize:latest
Configuration
Command Line Options
| Option | Description |
|---|---|
--port <PORT> |
Start in SSE mode on specified port |
--event-id <ID> |
Default Sessionize event ID |
--help |
Show help message |
--version |
Show version |
Environment Variables
| Variable | Description | Required |
|---|---|---|
SESSIONIZE_EVENT_ID |
Default event ID (can be overridden per tool call) | No |
Event ID Priority
- Tool parameter: Pass
eventIddirectly in tool calls (highest priority) - CLI argument:
--event-id your-event-id - Environment variable:
SESSIONIZE_EVENT_ID=your-event-id
Tools
This server provides 6 tools:
Speakers
| Tool | Description | Parameters |
|---|---|---|
getSpeakers |
List all speakers | eventId (optional) |
findSpeaker |
Search speaker by name | name (required), eventId (optional) |
getSessionsBySpeaker |
Get sessions by speaker | speakerName (required), eventId (optional) |
Sessions
| Tool | Description | Parameters |
|---|---|---|
getSessions |
List all sessions | eventId (optional) |
findSession |
Search sessions | query (required), eventId (optional) |
Schedule
| Tool | Description | Parameters |
|---|---|---|
getSchedule |
Get event schedule | eventId (optional) |
Example Prompts
"Show me all speakers"
"Find speaker John Doe"
"What sessions does Jane Smith have?"
"List all sessions about Kubernetes"
"What's the schedule for the conference?"
"Show speakers for event abc123"
Development
Requirements
- Java 21+ - Download
Run in dev mode
./mvnw quarkus:dev
Build
./mvnw package -DskipTests -Dquarkus.package.jar.type=uber-jar
Test with MCP Inspector
# STDIO mode
npx @modelcontextprotocol/inspector npx mcp-sessionize
# SSE mode
npx mcp-sessionize --port 9080 --event-id your-event-id
# Connect inspector to http://localhost:9080/mcp/sse
Technology Stack
- Quarkus 3.30 - Supersonic Subatomic Java
- Quarkus MCP Server 1.8.1 - MCP transport (HTTP/SSE/STDIO)
- MicroProfile REST Client - Sessionize API
License
Recommended Servers
playwright-mcp
A Model Context Protocol server that enables LLMs to interact with web pages through structured accessibility snapshots without requiring vision models or screenshots.
Audiense Insights MCP Server
Enables interaction with Audiense Insights accounts via the Model Context Protocol, facilitating the extraction and analysis of marketing insights and audience data including demographics, behavior, and influencer engagement.
Magic Component Platform (MCP)
An AI-powered tool that generates modern UI components from natural language descriptions, integrating with popular IDEs to streamline UI development workflow.
VeyraX MCP
Single MCP tool to connect all your favorite tools: Gmail, Calendar and 40 more.
Kagi MCP Server
An MCP server that integrates Kagi search capabilities with Claude AI, enabling Claude to perform real-time web searches when answering questions that require up-to-date information.
graphlit-mcp-server
The Model Context Protocol (MCP) Server enables integration between MCP clients and the Graphlit service. Ingest anything from Slack to Gmail to podcast feeds, in addition to web crawling, into a Graphlit project - and then retrieve relevant contents from the MCP client.
Qdrant Server
This repository is an example of how to create a MCP server for Qdrant, a vector search engine.
Neon Database
MCP server for interacting with Neon Management API and databases
Exa Search
A Model Context Protocol (MCP) server lets AI assistants like Claude use the Exa AI Search API for web searches. This setup allows AI models to get real-time web information in a safe and controlled way.
E2B
Using MCP to run code via e2b.