aiponge MCP server

Browse / search / discover / find books in the shared aiponge library catalog (not just the user's own — for those use list_books). "Find me a book about gratitude", "what books are there on sleep?", "browse the library". Optionally filter by `search` text or `typeId`. Searches all languages by default. Returns matching books with their ids — then use read_book to read one, or play_audiobook to listen.

THE DEFAULT WAY TO SAVE A REFLECTION OR JOURNAL ENTRY. Use this — NOT create_entry — for any request like "save this as a journal entry", "journal this", "add a journal entry", "save my reflection", "put this in my diary", "write this down". It opens an in-chat journal composer PRE-FILLED with a draft you write from the conversation, for the user to edit and save. It does NOT persist on its own; the user reviews and saves from the panel (Save then calls create_entry). Pass `draft` as your best draft of their entry (or "" for a blank composer). Only fall back to create_entry for silent saves or bulk imports.

Create / make / write / generate a SONG, a TRACK, or a piece of MUSIC for the user from a topic (e.g. "a calm morning walk", "write me a song about my mom", "make me some music about the sea"). This is THE tool for any "create/make/write a song|track|music" request. Provide EITHER a `topic` OR an `entryId` — do NOT ask the user for, or invent, a genre / mood / vocal style / language. The user's saved audio preferences are applied automatically, so the optional style fields are advanced overrides best left unset. • FROM A JOURNAL ENTRY: to "turn my last entry into a song" / "make a track for this entry", pass `entryId` (from create_entry's result, or resolved via list_entries / search_entries). This links the track to that entry and uses its content for the lyrics — `topic` is then optional. • BEYOND SONGS: this also makes spoken / non-song audio — set `audioContentType`: a guided meditation, visualization, or breathwork ("guided"); a spoken reflection, story, or audio essay ("reflection"); an instrumental / ambient / focus / sleep soundscape with no lyrics ("atmosphere"). Affirmations and a plain song are "song" (the default). So "make me a meditation about letting go" or "an ambient track for focus" route HERE. • PROGRESS: takes ~1–3 minutes. By DEFAULT it returns immediately and a live progress panel shows the track filling in, then turns into the player — so leave `wait` unset and just tell the user it is composing (no need to poll; the panel does it). If the user asks later, get_generation_status checks progress and play_track plays a finished track. Only pass `wait:true` for scripted/non-interactive callers that must block ~1–3 minutes and get the finished play link back in one call.

Return the canonical aiponge MCP tool map, workflow order, account/role requirements, and UI panel capabilities. Use this when unsure which tool to call.

Check on a song/track/music that is still being generated — "is my song ready?", "how is it coming along?". Takes the requestId returned by generate_track. Returns progress while generating, a play link when complete, or the failure reason. When complete, you can also call play_track with the returned trackId. When polling, wait at least 30 seconds between calls — generation takes 1–3 minutes, so checking more often than every 30 seconds just wastes calls and never returns sooner.

Surface what aiponge has NOTICED about the user — the observations, recurring patterns, and wellness signal drawn from their self-model, inferred from their reflections. Read-only. Use it when the user asks "what has aiponge learned about me?", "what patterns do you see in me?", "what are my themes?", "how am I doing?", or to understand the user before suggesting actions. This is the INFERRED picture, not a diagnosis; for the user's explicitly-set settings (audio preferences, language, account) use get_profile instead. Returns empty sections for a new user with little history.

Show the user's profile and saved settings — "what's on my profile?", "what are my music/audio preferences?", "what language am I set to?", "my account settings". Returns their wellness profile, including the saved audio preferences (genre, vocals, language, instruments) that generate_track applies automatically. Read-only. (To learn what aiponge has NOTICED about the user from their reflections — themes, patterns, their story — use get_insights instead.)

List the user's saved song sound profiles, including each profile ID and label. Use this before generate_track when the user asks to create a song with a named saved sound. Read-only.

Show / list the user's OWN books — "what books do I have?", "my library", "my books". Returns only the books they own or created, NOT the shared aiponge catalog. To discover or search the wider aiponge book catalog, use browse_books instead.

Show / list / browse the user's songs — "what songs do I have?", "show me my music", "my tracks", "my library", "my playlist of songs". Returns the user's private music tracks. Each item includes its `title`, `themes` (canonical topic tags the track was generated around, e.g. ["travel", "solitude"]), and `inspiration` (a short hint about what the song is ABOUT, derived from the original generation prompt). Also use this to RESOLVE a play request to a specific track: for "play something about Berlin" or "play the song about my mom", match against ALL THREE fields — not just `title` — and pick the row whose themes / inspiration / title best fits the request, then hand its id to play_track. If several rows plausibly match, list them and ask the user which one rather than guessing. The tracks render as an interactive player panel the user can see and play from directly (the per-track fields are in structuredContent) — after calling this, reply with at most a one-line intro and do NOT re-list the tracks in text; the panel already shows them.

Play / listen to a book as an audiobook — its chapters narrated as TTS audio, in order, with clickable stream links. "Read this book aloud", "play the audiobook", "I want to listen to a book". Resolve the bookId via browse_books or list_books first. Many catalog books are narrated; if a book isn't, this says so (read its text with read_book instead).

Play / listen to / put on ONE specific song the user already has — returns a fresh, clickable stream link for that track by its id. The user normally refers to a track by NAME, not id: when the requested title is approximate, partial, or possibly misspelled, FIRST call list_tracks (request the full library, e.g. limit 100), pick the closest matching title, then call this tool with its id. If several tracks plausibly match, list them and ask the user which one rather than guessing. Never invent a track id. (To browse or show the whole library, use list_tracks; to create a new song, use generate_track.)

Read / open a book's text content — its chapters and the prose of each — so you can summarize, quote, or discuss it. "Read me that book", "what does the book say?", "summarize this book". Resolve the bookId via browse_books or list_books first. To LISTEN to it as narrated audio instead, use play_audiobook.

Find / search / look up journal entries by a keyword, tag, date range, location, sourceMemoryId, sourceType, or sensitivity — "did I write anything about my trip?", "entries from last June", "show entries tagged work". Use this (not list_entries) whenever the user wants entries matching a query rather than just the most recent. Ranks bounded candidates before returning results; structuredContent.truncated is true if the newest 5000 candidates may not cover every entry. Pass sourceMemoryId before importing inventory memories to avoid duplicates.

Change / set / update the user's saved AUDIO (music) preferences — the defaults generate_track applies automatically to every new song (genre, vocal gender, language, instruments, default audio content type). Only the fields you pass are changed; the rest of their preferences are preserved. Use this when the user wants to change their music style GOING FORWARD (e.g. "from now on make my songs jazz with female vocals", "always use Spanish for my songs"), NOT for a one-off — for a single song, pass the style to generate_track instead.