Lyricmood Agent Server
v1.0.0A powerful MCP server built with NitroStack
Add via Cursor Settings UI (Settings > Features > MCP > Add New MCP Server):
{
"mcpServers": {
// your other mcp servers
"lyricmood-agent-server": {
"url": "https://lyricmood-agent-6a-cipherix-amrita-university-amritapuri-campus.app.nitrocloud.ai/mcp"
}
}
}
Connect remote tools directly via Claude's Web UI:
Configure custom tools directly via ChatGPT's Web UI:
Add the following configuration block under mcpServers in your Antigravity configuration file (~/.gemini/config/mcp_config.json):
{
"mcpServers": {
// your other mcp servers
"lyricmood-agent-server": {
"serverUrl": "https://lyricmood-agent-6a-cipherix-amrita-university-amritapuri-campus.app.nitrocloud.ai/mcp"
}
}
}
Add the following configuration block to your Codex configuration file (~/.codex/config.toml):
[mcp_servers.lyricmood-agent-server] url = "https://lyricmood-agent-6a-cipherix-amrita-university-amritapuri-campus.app.nitrocloud.ai/mcp"
Connect directly using the Server-Sent Events endpoint:
https://lyricmood-agent-6a-cipherix-amrita-university-amritapuri-campus.app.nitrocloud.ai/mcp
Analyze song lyrics for syllable rhythm, word density, rhyme scheme (exact and slant), and stress-pattern regularity. Input should include [Section] tags (e.g. [Verse 1], [Chorus]) on their own lines. IMPORTANT: Whenever the user asks to check, analyze, or review their song lyrics — even if they have not yet included any actual lyrics text in their message — always call this tool right away, passing an empty string for lyricsText if none was given. Do NOT simply ask the user for their lyrics conversationally without calling the tool first; the tool itself will return a clear, structured warning guiding the user on what to provide. The report includes a top-level "warnings" array flagging missing lyrics, malformed [Section] tags, empty sections, long unbroken syllable runs (15+, no breath point), and irregular stress patterns — always call these out clearly to the user if present. After a successful analysis, always propose a rewritten alternative for any line in a NEEDS_REVISION section, any line whose density noticeably breaks the pattern of its section, or any line flagged in warnings. When writing a rewrite: (1) prioritize vivid, specific, sensory imagery over generic or clichéd phrasing (e.g. prefer a concrete image over an abstract statement of feeling); (2) preserve the original line's core meaning while keeping word choice consistent with the emotional tone and any recurring metaphor or theme already present in that section or song; (3) still ground every rewrite in the verified data above — match the section's syllable range, prefer an exact rhyme where possible and fall back to a slant rhyme only when a strong exact option is not available, and favor a stress pattern consistent with the section's other lines. After suggesting a rewrite, invite the user to re-run check_rhythm on the revised line to confirm it actually satisfies the syllable, rhyme, and stress checks — creative suggestions should be verifiable, not just plausible-sounding. Present all rewrites as optional creative suggestions, never as forced replacements.