# Intentions MCP Server [Health: Active]

**Category:** 🔮 Spirituality & Esoterica  
**Repository:** https://github.com/intentions-me/intentions-mcp  
**GitHub Stars:** 1  
**Views:** 1  
**Installs:** 0  
**Upvotes:** 0  
**Directory Page:** https://allmcps.com/mcp/intentions-mcp-server

## Description
Personalized timing intelligence for AI agents — ask 'should I do X on this date?'

## Tools
Capabilities this server exposes over MCP:

- **intentions_ask_day** — 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`.
- **intentions_ask_hour** — 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.
- **intentions_ask_year** — 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.
- **intentions_ask_month** — 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`.
- **intentions_energy_chart** — 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.
- **intentions_set_birth_info** — 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.
- **intentions_get_profile** — 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.

## Claude Desktop Quick Installation
Remote MCP endpoint (confidence: high). Install path detected from listing signals. Add as a URL/SSE server in your client:

```json
"mcpServers": {
  "intentions-mcp-server": {
    "url": "https://mcp.intentions.me/mcp"
  }
}
```

## Documentation

## What Intentions MCP Server does

Intentions MCP Server gives an AI agent structured timing readings for a decision and a date window. Results can include a 0–100 alignment score, a verdict such as favorable or proceed with caution, friction indicating execution resistance, element dimensions, and adverse alerts with behavioral guidance.

The service supports several levels of planning. Agents can assess a complete calendar year, compare or scan months, compare dates or search a day range, and select a time within a day. This makes it possible to narrow a decision from year to month, day, and hour. Typical applications include trip planning, product or content launches, interview and meeting scheduling, negotiation preparation, and relationship or family timing.

## How it works

The hosted endpoint accepts MCP requests over Streamable HTTP. Each request uses a Bearer API key issued through an Intentions account. The key is associated with the account quota and its stored energy profile.

Before requesting personalized readings, an agent can register birth date, time, gender, and optionally birth city. The city allows the service to account for the actual local birth moment, including daylight-saving changes. Unknown values can be stored as null. Profile updates replace the complete profile, so an agent should retrieve the existing profile first, merge the requested change, and submit all fields again.

Timing inputs are limited to the current year plus or minus three years. Free access includes daily quotas and restrictions on some scans and charts; Pro access expands those limits and enables hour-level analysis.

## Setup and configuration

No local installation or self-hosting is required. Create an account at `https://intentions.me`, generate an API key from the account page, and configure an MCP client with the following remote endpoint:

```text
https://mcp.intentions.me/mcp
```

Send the key in the request header:

```text
Authorization: Bearer itm_your_api_key_here
```

Claude Desktop can use an HTTP MCP entry with the endpoint and authorization header. The service can also be added to claude.ai as a custom connector using the same URL and Bearer token. Treat the key as a password because it carries account quota and access to the stored profile.

## Tools and capabilities

- `intentions_ask_year` evaluates a whole calendar year and returns a year score, verdict, element dimensions, and adverse alerts.
- `intentions_ask_month` handles one month, comparisons of up to five months, or scans of up to twelve months, returning scores, element details, and alerts.
- `intentions_ask_day` evaluates one date, compares up to five dates, or scans a range of up to 31 days. Free range scans cover the previous week and following week.
- `intentions_ask_hour` compares or scans time windows within one day. It uses two-hour blocks, requires Pro, and returns a local wall-clock window for each result.
- `intentions_energy_chart` produces ASCII hourly, weekly, or yearly views. Weekly charts cover the previous and coming week on the free tier; hourly and expanded chart ranges require Pro.
- `intentions_set_birth_info` creates or replaces the complete birth profile, while `intentions_get_profile` retrieves stored values and remaining profile-change allowance.

## Limitations and notes

The free plan provides five day, month, or year readings per day, resetting at midnight UTC. Pro removes that reading limit and expands scanning access. Changes to birth date, gender, or a known birth hour are limited to three per UTC calendar month; filling in a previously unknown hour or changing the minute is free.

Hour analysis is only available to Pro subscribers. A daylight-saving ambiguity at the birth location can require the caller to specify whether the earlier or later clock occurrence should be used. Late-night inputs from 23:00 through 23:59 roll the effective day forward, and returned time windows should be presented with their supplied local-time interpretation.

Intentions MCP Server is a hosted proprietary service rather than a package to run locally. Current pricing and account management are available at `https://intentions.me`.

_Full upstream README: https://allmcps.com/mcp/intentions-mcp-server/readme_