AI assistantsDocumentation
Talk to your journey.
Connect an AI assistant you already use, such as Meta Muse or Claude, to your Manifestory journey. Ask what today’s action is, check in by voice, or log evidence the moment it happens, without opening the app.
MCP server and REST API
Before you start
- You need the Manifestory app on iPhone and an account (you must be 18 or older).
- Creating a connection requires an active free trial or subscription. If your membership lapses, a connected assistant can still read your journey but can no longer check you in or add evidence.
- You need an assistant that can connect to an MCP server or call a web API with an API key. Manifestory offers both, an MCP server and a REST API described by an OpenAPI specification, so it isn’t tied to one assistant.
Connect an assistant
- In Manifestory, open Settings › AI assistants and tap Connect an assistant.
- Read exactly what your assistant will be able to see, choose Read only or Read & check-in, and confirm that you agree to share it.
-
Create the connection and copy your token. It starts with
mfy_and is shown only once. Manifestory stores only a one-way hash of it. - Add it to your assistant as shown below. The app shows the same steps for Meta Muse, Claude and other assistants.
- Try it out: ask “What’s my action today?”
Assistant setup
Meta Muse
Add the Manifestory connector in Muse, or ask Muse to connect a custom service called
Manifestory. When it asks for a key, paste your token. If it also asks for a URL, use
https://api.manifestory.app.
Claude
- In Claude, open Settings › Connectors, then Add › Add custom connector.
-
Name it Manifestory, enter
https://api.manifestory.app/mcpas the MCP server URL, and continue. -
Under Authentication, choose No sign‑in. Under
Request headers, add
x-api-keyand paste your token as its value. Claude may say the server asked for sign-in; the header is how this connection signs in. - Click Add, then Connect.
In Claude Code:
claude mcp add --transport http manifestory https://api.manifestory.app/mcp \
--header "x-api-key: mfy_your_token_here"
Other assistants
-
MCP: connect to
https://api.manifestory.app/mcpand send your token in anx-api-keyheader or asAuthorization: Bearer mfy_…. -
Web API: point the assistant at
https://api.manifestory.app(it can read the OpenAPI specification) and use your token as the API key.
What your assistant can see and do
An assistant you connect can look up parts of your journey whenever you ask it to. This is exactly what it gets.
It can read
- Your goal, and which day of 30 you’re on
- Today’s action, affirmation and quote
- Whether you checked in and did your action, today and over the past week, and the feelings you chose
- Your streak, progress, and the mix of feelings you’ve logged
- Your evidence entries for this journey
- Your coaching insights (days 7, 14, 21 and 30) that you have already revealed in the app
- Your Arcana card and its reflection, once you have turned it over
- The moon phases across your journey
- The name you give this connection
It can never read your journal notes or your answers to coaching questions. Coaching insights are written from your check-ins, notes and evidence, so an insight may mention something you wrote.
With “Read & check-in”, it can also
- Check you in for today: mark your action done, choose a feeling and save a journal note you dictate
- Add a new evidence entry
| Access level | What it allows |
|---|---|
| Read only | Answers questions about your journey. Doesn’t check you in or add evidence. |
| Read & check-in | Can also check you in for today and add evidence when you ask. |
The company behind your assistant processes this data under its own privacy policy, not Manifestory’s.
Connection details
- MCP server
https://api.manifestory.app/mcp(Streamable HTTP; MCP 2026-07-28, and 2025-11-25 and earlier)- Base URL
https://api.manifestory.app(REST)- Specification
- OpenAPI 3.1 · llms.txt
- Authentication
- Your personal token, sent as
Authorization: Bearer mfy_…orX-API-Key: mfy_… - Health check
GET https://api.manifestory.app/health(no token needed)- Format
- JSON over HTTPS. Every response includes
speech, a short plain-text summary an assistant can read aloud as-is.
curl https://api.manifestory.app/v1/today \
-H "Authorization: Bearer mfy_your_token_here"
Endpoints
Over MCP, each endpoint is a tool with the name shown under it, taking the same parameters as arguments.
| Request | What it does | Access |
|---|---|---|
GET /v1/meMCP: getConnection |
Checks the connection: confirms the token, its access level, and whether there’s an active journey. Use it to test a new connection. | Read |
GET /v1/todayMCP: getToday |
Today’s day number, affirmation, quote and action, whether it’s done, check-in status, moon phase and streak. Call it before checking in. | Read |
GET /v1/journeyMCP: getJourney |
Progress on the current 30-day journey, including each of the last seven days. | Read |
GET /v1/evidenceMCP: listEvidence |
Recent evidence on the current journey. limit from 1 to 50, default 10. |
Read |
GET /v1/coachingMCP: getCoachingInsight |
A coaching insight from day 7, 14, 21 or 30 (milestone; omit for the latest), with the status of all four. Insights are revealed in the app, not here. |
Read |
GET /v1/cardMCP: getArcanaCard |
This journey’s Arcana card: what it gives and costs, its daily practice and the reflection written for the user. Hidden until it’s turned over in the app. | Read |
GET /v1/moonMCP: getMoonCalendar |
Today’s moon phase and the new, quarter and full moons still ahead in the journey, with dates and day numbers. | Read |
POST /v1/today/check-inMCP: checkIn |
Today’s check-in: date (from /v1/today), action_completed, feeling (positive, negative, neutral or not_sure) and an optional note of up to 1,000 characters. A day can be checked in once. |
Read & check-in |
POST /v1/evidenceMCP: addEvidence |
Adds evidence: text up to 200 characters and a type of win, synchronicity, sign or other. Send an Idempotency-Key header so retries aren’t logged twice; near-identical text already logged today is also never added twice. |
Read & check-in |
Limits and errors
- Connections
- Up to 5 active connections per account.
- Idle expiry
- A connection that goes unused for 60 days stops working on its own.
- Rate limit
- 30 operations per minute per connection: each API request, or each MCP tool call (MCP housekeeping such as
initializeandtools/listdoesn’t count). Over that, the API returns429with aRetry-Afterheader, and an MCP tool call returns an error withretry_after_seconds. - Request size
- API request bodies up to 8 KB; MCP messages up to 32 KB.
Errors return a machine-readable error code and a speech
explanation to read to the user: 400 for an invalid request;
401 for a missing, revoked or expired token; 403 when a write needs an active membership or the connection is
read-only; 409 when there’s no active journey, today is already checked
in, or the day has rolled over. Over MCP, the same failures come back as tool results
marked isError, with the same error code and speech.
Disconnecting
Open Settings › AI assistants in Manifestory and revoke the connection. Access stops right away. Your assistant may still remember what it has already learned; you can clear that in the assistant itself. Revoked connections stay listed for 30 days so you can see what you disconnected, and deleting your Manifestory account removes every connection.
Privacy and support
Connecting an assistant is a disclosure you direct. We never sell your data. Section 15 of the Privacy Policy covers AI assistants you connect in full, and Section 9.1 of the Terms of Service covers using them.
Questions or problems
Message support