Sonic MCP Server
Search places using Google Maps, get detailed place information, and address autocomplete functionality.
Search Spotify catalog for tracks and manage music metadata with Spotify integration.
Click on "Deploy Server".
Wait a few minutes for the server to deploy. Once ready, it will show a "Started" state.
In the chat, type
@followed by the MCP server name and your instructions, e.g., "@Sonic MCP Server Search Spotify for tracks by ABBA"
That's it! The server will respond to your query, and you can continue using it as needed.
Here is a step-by-step guide with screenshots.
Sonic MCP Server
A Model Context Protocol (MCP) server that enables AI agents to interact with the Sonic API for managing events, venues, songs, and users.
Overview
This MCP server provides a comprehensive interface for AI agents to:
Manage Events: Create, read, update, delete events with full CRUD operations
Manage Venues: Handle venue information including addresses and capacity
Handle Songs: Music data management with Spotify integration
User Management: Profile operations and authentication
Search Integration: Spotify music search and Google Maps places
Real-time Interaction: Direct API communication with proper authentication
Related MCP server: mcp-spotify
Features
πͺ Event Management
Create events with dates, venues, and attendee limits
Search and filter events by name, owner, or description
Include related data (venues, users, songs) in responses
Support for public/private events
π’ Venue Management
Create venues with detailed address information
Manage venue capacity and descriptions
Link venues to events
Search venues by location or name
π΅ Music Integration
Add songs to your library
Search Spotify for tracks
Link songs to events
Manage music metadata (artist, album, genre)
π₯ User Operations
View user profiles
Update account information
Admin functions for user management
Authentication and authorization
πΊοΈ Location Services
Search places using Google Maps
Get detailed place information
Address autocomplete functionality
Installation & Setup
Prerequisites
Node.js 18+
TypeScript
Access to Sonic API with valid JWT token
Quick Start
Install dependencies:
npm installBuild the project:
npm run buildSet your authentication token:
# Windows (PowerShell) $env:SONIC_API_TOKEN = "your-jwt-token-here" # macOS/Linux export SONIC_API_TOKEN="your-jwt-token-here"Run the server:
npm start
Configuration
Environment Variables
SONIC_API_TOKEN: Your JWT authentication token (required)SONIC_API_BASE_URL: API base URL (default: https://localhost:5001/api)
Getting Your JWT Token
curl -X POST https://localhost:5001/api/auth/login \
-H "Content-Type: application/json" \
-d '{
"email": "your-email@example.com",
"password": "your-password"
}'AI Client Integration (Claude Desktop)
Add to your Claude Desktop configuration:
{
"mcpServers": {
"sonic-api": {
"command": "node",
"args": ["C:\\path\\to\\sonic-mcp-server\\build\\index.js"],
"env": {
"SONIC_API_TOKEN": "your-jwt-token-here"
}
}
}
}Available Tools
Event Tools
get_events- List events with filtering and paginationget_event- Get specific event detailscreate_event- Create new eventupdate_event- Modify existing eventdelete_event- Remove event
Venue Tools
get_venues- List venues with searchget_venue- Get venue detailscreate_venue- Add new venueupdate_venue- Modify venue infodelete_venue- Remove venue
Song Tools
get_songs- List music libraryget_song- Get song detailscreate_song- Add song to libraryupdate_song- Update song infodelete_song- Remove song
User Tools
get_users- List users (admin)get_user- Get user profileget_current_user- Get your profileupdate_user- Update user info
Integration Tools
search_spotify- Search Spotify catalogget_spotify_token- Check Spotify authsearch_places- Find locationsget_place_details- Get place info
Usage Examples
Natural Language Commands
Once configured with an AI assistant, you can use natural language:
"Show me all events happening this week"
"Create a new venue called 'The Blue Note Jazz Club' in New York"
"Search Spotify for Beatles songs"
"Find events at Madison Square Garden"
"Update my user profile with a new email"
Direct Tool Calls
{
"name": "create_event",
"arguments": {
"name": "Summer Music Festival",
"description": "Outdoor music event",
"startDate": "2024-07-15T18:00:00Z",
"maxAttendees": 500,
"isPublic": true
}
}Development
Scripts
npm run build- Compile TypeScriptnpm run dev- Watch mode for developmentnpm run clean- Remove build filesnpm start- Run the compiled server
Project Structure
src/
βββ index.ts # Main MCP server
βββ sonic-client.ts # API client wrapper
βββ types.ts # TypeScript definitions
.vscode/
βββ mcp.json # VS Code MCP configuration
.github/
βββ copilot-instructions.md # AI coding assistanceDebugging in VS Code
The project includes VS Code debugging support. You can now debug this MCP server using VS Code with proper breakpoints and debugging tools.
Security & Authentication
JWT Authentication: All API calls require valid JWT token
Permission System: Cascading ownership with admin overrides
Environment Variables: Secure token storage
Error Handling: Comprehensive error messages without exposing sensitive data
API Compatibility
Compatible with Sonic API endpoints:
/api/events- Event management/api/venues- Venue management/api/songs- Music management/api/users- User operations/api/spotify- Music search/api/maps- Location services
Contributing
Fork the repository
Create a feature branch
Make your changes with proper TypeScript types
Add tests if applicable
Submit a pull request
License
MIT License - See LICENSE file for details
Support
For issues and questions:
Check the troubleshooting section in the code
Review the MCP protocol documentation
Ensure your JWT token is valid and not expired
Available Tools
23 toolscreate_eventC
Create a new event
Inputs: name (required), startDate (required), endDate, venueId, +3 more.
create_songC
Create a new song
Inputs: title (required), artist (required), album, genre, +3 more.
create_venueC
Create a new venue
Inputs: name (required), address, capacity, description.
delete_eventC
Delete an event by ID
Inputs: id (required).
delete_songB
Delete a song by ID
Inputs: id (required).
delete_venueB
Delete a venue by ID
Inputs: id (required).
get_current_userA
Get the current authenticated user profile
Inputs: no named parameters.
get_eventC
Get a specific event by ID
Inputs: id (required), includeSongs, includeUsers, includeVenues.
get_eventsC
Retrieve events with optional filtering by owner, search terms, or include related data
Inputs: page, owner, search, pageSize, +3 more.
get_place_detailsC
Get detailed information about a specific place
Inputs: placeId (required).
get_songA
Get a specific song by ID
Inputs: id (required), includeEvents.
get_songsC
Retrieve songs with optional filtering
Inputs: page, owner, search, pageSize, +1 more.
get_spotify_tokenB
Get current Spotify access token status
Inputs: no named parameters.
get_userB
Get a specific user by ID
Inputs: id (required).
get_usersA
Retrieve users with optional filtering (admin only)
Inputs: page, search, pageSize.
get_venueA
Get a specific venue by ID
Inputs: id (required), includeEvents.
get_venuesC
Retrieve venues with optional filtering
Inputs: page, owner, search, pageSize, +1 more.
search_placesB
Search for places using Google Maps API
Inputs: query (required), radius, location.
search_spotifyB
Search for tracks on Spotify
Inputs: query (required), limit.
update_eventB
Update an existing event
Inputs: id (required), name, endDate, venueId, +4 more.
update_songC
Update an existing song
Inputs: id (required), album, genre, title, +4 more.
update_userC
Update user profile information
Inputs: id (required), email, lastName, username, +1 more.
update_venueC
Update an existing venue
Inputs: id (required), name, address, capacity, +1 more.
Tool Schema Changelog
Recent tool additions, removals, and schema changes observed during successful MCP inspections.
Loading tool schema changelogβ¦
TDQS
Scored across 23 tools
Each tool targets a distinct entity and action (e.g., create_event vs. create_song, get_events vs. get_event). There is no overlap that would confuse an agent.
All tools follow a clear verb_noun pattern (create_, delete_, get_, update_, search_) using lowercase with underscores, ensuring predictability.
With 23 tools, the set is slightly above the ideal 3-15 range but still well-scoped for the server's domains (events, songs, venues, users, places, Spotify). Each tool serves a clear purpose.
CRUD operations are complete for events, songs, and venues. Users lack create and delete endpoints, and places/Spotify are read-only, which is acceptable given external integrations.
Related MCP Connectors
Enables AI assistants to retrieve event data and execute event management operations in Nunify.
Booking gateway for AI agents β discover events, movies & hotels, hand off to partner checkout.
Connect your AI agent to 300+ methods and 100+ live tools
Lets AI agents analyze API metrics, request logs, and traces, and manage apps and alerts.
Related MCP Servers
- FlicenseBqualityDmaintenanceThis server integrates with the Ticketmaster API to provide AI agents with real-time concert and event data, enabling dynamic fetching and formatting for ease of interpretation.12-
- AlicenseNot gradedqualityDmaintenanceEnables AI agents to create, manage, and populate Spotify playlists using the Spotify Web API.3MIT
- AlicenseNot gradedqualityDmaintenanceEnables AI agents to search Spotify, inspect playback state, manage devices, and control music through the official Spotify Web API using OAuth authentication.3MIT
- AlicenseBqualityDmaintenanceEnables AI agents to access public Spotify data (tracks, albums, artists, playlists, podcasts) without an API key, including lyrics and podcast transcripts with optional login.282,216 PyPI327MIT