Sonic MCP Server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| SONIC_API_TOKEN | Yes | Your JWT authentication token | |
| SONIC_API_BASE_URL | No | API base URL | https://localhost:5001/api |
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 |
|---|---|
| get_eventsC | Retrieve events with optional filtering by owner, search terms, or include related data |
| get_eventC | Get a specific event by ID |
| create_eventC | Create a new event |
| update_eventB | Update an existing event |
| delete_eventC | Delete an event by ID |
| get_venuesC | Retrieve venues with optional filtering |
| get_venueA | Get a specific venue by ID |
| create_venueC | Create a new venue |
| update_venueC | Update an existing venue |
| delete_venueB | Delete a venue by ID |
| get_songsC | Retrieve songs with optional filtering |
| get_songA | Get a specific song by ID |
| create_songC | Create a new song |
| update_songC | Update an existing song |
| delete_songB | Delete a song by ID |
| get_usersA | Retrieve users with optional filtering (admin only) |
| get_userB | Get a specific user by ID |
| get_current_userA | Get the current authenticated user profile |
| update_userC | Update user profile information |
| search_spotifyB | Search for tracks on Spotify |
| get_spotify_tokenB | Get current Spotify access token status |
| search_placesB | Search for places using Google Maps API |
| get_place_detailsC | Get detailed information about a specific place |
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 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.