Intentions MCP Server
Server Details
Personalized timing intelligence for AI agents — ask 'should I do X on this date?'
- Status
- Healthy
- Uptime
- 100.0% over the last 24 hours
- Last Tested
- Transport
- Streamable HTTP · MCP 2025-11-25
- URL
- Repository
- intentions-me/intentions-mcp
- GitHub Stars
- 1
- Server Listing
- Intentions MCP Server
- ChatGPT
- –
- Claude
- –
TDQS
Scored across 7 tools
The four intentions_ask_* tools are cleanly separated by time granularity (day/hour/month/year), and the descriptions explicitly guide cross-tool routing. The main overlap is intentions_energy_chart, which returns visual data at hourly/weekly/yearly resolutions also available through the ask tools, though its 'visual overview' purpose is still distinguishable.
All tools share the intentions_ prefix and snake_case formatting, with a predictable ask_<granularity> family plus get_profile/set_birth_info. The only minor deviation is intentions_energy_chart, which is a noun phrase rather than a verb_noun action name.
Seven tools is well-scoped for this domain: four timing resolution tools, one visualization tool, and two profile-management tools. Each has a clear distinct role and none feels redundant or missing.
The surface covers timing queries across day, hour, month, and year granularities, plus chart visualization and full birth-profile read/write lifecycle. No obvious dead ends for the stated purpose; updates are handled through get-then-set with null semantics.
Available Tools
7 toolsintentions_ask_dayARead-onlyInspect
Call when the user asks about timing a decision for a specific date, or wants to pick the best day from a multi-day window. Covers trip dates, launch days, interview/meeting days, publish/send dates, travel, negotiation windows, relationship moments — any "when to X" question where the answer is a date ("should I X on April 23", "best day this month to Y", "下周四怎么样"). Modes: single date, compare up to 5 dates, or scan a range up to 31 days. On the free tier a range must sit inside the past week and the week ahead; single and compared dates are free anywhere in the window. Returns score (0-100), verdict, per-layer year/month/day breakdown (alerts + dimension signals), element breakdown, adverse alerts. For multi-month windows use intentions_ask_month; for hour precision use intentions_ask_hour.
Inputs: question (required), category, birthInfo, dateRange, +2 more.
intentions_ask_hourARead-onlyInspect
Call when the user asks about timing within a specific day — best hour to act, morning vs afternoon, when during the day ("best time today to X", "morning or afternoon for Y", "几点去见面好"). Use for interview slots, meeting times, send/publish times, departure times, workout windows. Pro subscription required; on the free tier this returns a subscription_required error whose payload suggests intentions_ask_day for day-level analysis or intentions_energy_chart with period weekly / yearly for a visual overview (the caller LLM decides whether to retry). Modes: single (date+hour), compare up to 5 hour-pairs, or scan all 12 two-hour blocks of one day. Accepts any clock hour 0..23; internally mapped to the containing 2-hour block midpoint (0/2/4/…/22). 23:00–23:59 automatically rolls the effective day forward by one. Every output entry includes a window { start, end } local wall-clock span (YYYY-MM-DDTHH:MM, no timezone offset — interpret in the same frame as the input hour). Always cite this when presenting the time. Returns score, verdict, adverse alerts.
Inputs: question (required), category, bestInDay, birthInfo, +3 more.
intentions_ask_monthARead-onlyInspect
Call when the user asks at month granularity or wants the best month from a multi-month window ("how is next month", "best month in 2026 to X", "下个月适合吗"). Use for trip-month selection, launch months, content-calendar planning, quarterly/annual decisions. Modes: single month, compare up to 5 months, or scan up to 12 months (returns top 5). Single and compared months are free; scanning a range is free inside last year and this year, and Pro further out. Returns month score, element breakdown, adverse alerts. For day precision near the 4th–6th of a month use intentions_ask_day; for hour precision use intentions_ask_hour.
Inputs: question (required), category, birthInfo, monthRange, +2 more.
intentions_ask_yearARead-onlyInspect
Call when the user asks about a full calendar year as a whole ("how is 2026", "今年怎么样", "what's next year like overall"). Returns year-level score, verdict, adverse alerts, and element dimensions. For month precision use intentions_ask_month; for day use intentions_ask_day. Window: currentYear-3 to currentYear+3 only.
Inputs: question (required), category, birthInfo, targetYear.
intentions_energy_chartARead-onlyInspect
Call when the user wants a visual overview rather than a narrative answer ("show me this week", "chart for today", "next 12 months", "看一下图"). Returns an ASCII chart: hourly = 12 two-hour blocks of one day, weekly = 7 days, yearly = 12 months. The hourly mode emits the same hour-resolution scores as intentions_ask_hour and is Pro: on the free tier it returns a subscription_required error whose payload suggests alternatives. weekly is free for the past week and the week ahead (omit date for this week), and yearly for the months of last year and this year (omit date for this year); further out both are Pro too.
Inputs: period (required), date, birthInfo.
intentions_get_profileARead-onlyInspect
Fetch the user's currently stored birth info. Use this before intentions_set_birth_info when updating an existing profile so you can send back a complete merged payload. Returns { hasProfile, birthInfo: { year, month, day, hour, minute, gender } | null, profileChanges: { remaining, resetsAt } | null, birthPlace: string | null, next? } where next, when present, says what to ask the user (e.g. their city of birth). Any unknown birth field (e.g. unknown hour) is returned as null. profileChanges is how many changes to the date, gender or a known hour are left this calendar month (UTC) and the ISO instant they come back; if remaining is 0, tell the user before attempting such a change. No quota cost.
Inputs: no named parameters.
intentions_set_birth_infoAIdempotentInspect
Call once to register the user's birth date/time/gender. Each call is a complete replacement — all 6 fields must be supplied. For fields the user does not know or prefers not to share, pass null explicitly (e.g. hour: null for unknown birth time, gender: null for unspecified). To update just one field, first call intentions_get_profile to fetch the current values, merge the user's new input, then call this tool with the full merged payload. Changes to the date, gender or a known hour (including setting a known hour back to null) are limited to 3 per calendar month (UTC); filling in a previously-null hour, or the minute, is always free. intentions_get_profile returns how many are left. Always pass birthPlace (the city of birth, e.g. "Portland, Maine") when the user gives it: readings then use the real moment of birth there, daylight saving included. Omit it only to keep the stored one; changing it is free. If the call fails with birth_time_needs_confirming, the clocks changed over that time at the birthplace: ask the user which it was and call again with birthTimeFold (0 = the earlier, 1 = the later). Returns the element profile.
Inputs: day (required), hour (required), year (required), month (required), +4 more.
Tool Schema Changelog
Recent tool additions, removals, and schema changes observed during successful MCP inspections.
Loading tool schema changelog…
Related MCP Connectors
Astrology transit forecasts, timelines and significant-date feeds for AI agents.
Real astrology for AI agents: cosmic weather, synastry, timing, astrocartography, and divination.
Real-time AI intelligence signals and temporal knowledge graph for agent economy
Scheduling infrastructure for AI agents across Google and Microsoft calendars.
Related MCP Servers
- AlicenseAqualityDmaintenanceProvides AI assistants with rich temporal intelligence including timezone conversions, 9 cultural calendars (Hebrew, Islamic, Chinese, etc.), astronomical events, Islamic prayer times, and context-aware activity appropriateness recommendations.3MIT
- MIT
- AlicenseAqualityCmaintenanceDeterministic temporal reasoning engine for AI agents. LLMs are surprisingly bad at dates, timezones, business days, holidays, and recurring schedules. Taghvim gives agents deterministic temporal primitives they can call instead of guessing.1222 npm1MIT
- AlicenseAqualityDmaintenanceProvides time intelligence, persistent memory and complete traceability for AI coding agents. Enables sophisticated activity tracking, timezone management, smart reminders, and cross-session continuity with support for both per-project and centralized storage modes.97MIT
Glama MCP Gateway
Add one secure layer between your agents and this server.