No user-submitted related servers found.
Scored across 28 tools
The prefixes (theta_, wave_) and resource names help separate most tools, but several pairs are easy to confuse: wave vs wave_send_message both send messages to Wave OS, wave_connect vs theta_configure both configure Theta compute credentials, and read_records vs aggregate_records both query records. The descriptions clarify the differences, but selection is not always obvious from names alone.
Most tools use snake_case and a verb_noun structure, but conventions are mixed: Base44 tools have no prefix (create_records, call_function), some wave_* tools use noun phrases (wave_morning_briefing, wave_triage, wave_meeting_prep), and the standalone 'wave' tool breaks the pattern entirely. The prefixes make the set readable, but the naming is not uniform.
Twenty-eight tools is on the high side and heavier than most MCP servers, but the server spans multiple distinct domains: Base44 data operations, Theta EdgeCloud compute/blockchain, and Wave OS assistant/messaging. Most tools have a distinct purpose, so the count feels borderline rather than severely bloated.
Base44 record CRUD and Theta read/credential operations are well covered, and the Wave OS assistant surface includes briefing, triage, memory recall, delegation, and messaging. However, there are notable gaps: no entity schema update/delete, no memory write tool, and no direct Theta GPU job execution or inference tool despite status and cost-estimation capabilities.