Epiphany MCP Server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| EPIPHANY_API_KEY | Yes | API key for Epiphany booking automation |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| list_vslsA | Get all VSLs to find VSL IDs for other operations |
| get_vslB | Get detailed info about a specific VSL |
| get_available_timesB | Check which time slots are available for booking on a specific date |
| create_bookingC | Create a new booking with optional auto-confirmation for instant Meet link |
| list_bookingsB | Get all bookings across all VSLs |
| get_bookingB | Get details of a specific booking by ID |
| get_waitlistB | Get waitlist entries for a VSL with pagination |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 7 tools
Each tool targets a distinct resource or action: bookings (create, get, list, available times), VSLs (get, list), and waitlist (get). No overlapping purposes.
All tools follow a consistent verb_noun snake_case pattern (e.g., create_booking, get_available_times, list_vsls). Singular vs plural is used appropriately.
Seven tools is a reasonable number for a booking-related server, covering core operations without being excessive or insufficient.
The set covers create, get, list, and availability checks, but lacks update and delete operations for bookings, which are notable omissions in a booking domain.