← Registry

General Tools

asterajournal.com

Provides general-purpose tools through the Model Context Protocol.

1 endpoint5 known toolsFirst detected October 7, 2026Last detected October 7, 2026

ENDPOINT 1

https://asterajournal.com/mcp

No auth detected

MCP server metadata

Name
astera
Version
3.0.0
Capabilities
tools
Server instructions

Astera prints any journal a person asks for, built from scratch. Leave journal.template out and describe every page in journal.sets, each page in parts in the order it prints. Build it from the real thing: a page they share, a journal they name, or their own words. Use one of Astera's templates only when they ask for it by name, and never because it sounds close. When contents lists the pages of a template they did not ask for, save again with journal.template set to blank. When they share a photo, a drawing or a screenshot of a page, that picture is the design. Read it top to bottom and build every part on it, in its order and at its share of the page: its heading, the hours, each question, each list, each box beside another, and the fill. A photo of an open journal is two pages: build both, the facing page as drawn too, even a page of plain dots. Use paper for dots or squares behind the whole page, and a title part for a large title with the date beside it. Keep their words as written, ask only about a part you cannot read, and tell them anything on it the page could not hold. When they name a journal, such as BestSelf, Full Focus or the Five Minute Journal, search the web for its inside pages before the first save: the maker's own pages and photos of the journal in use. Build its pages as you found them and tell them where you looked. Then make their changes and keep every part they did not ask to change. Never build a named journal from memory or from one of Astera's templates. Unless what they share or name shows otherwise, a planner's day is a spread of two pages with the hours taking about half of it. After every save, check the contents it returns against what they asked, part by part and in order, and fix any difference before you tell them the journal is ready. Never tell the person what kind of journal theirs is or is not, or which template it uses. Tell them what is in it, from the contents astera_save returns, and never claim a page the contents do not list. When contents says a part will not print, move it to another page or take a part off, and save again. When they want a poem, a prayer or song words printed and you cannot give them the text, build the rest of the journal anyway and ask them in one line to paste the words into the chat. Put what they paste in a poem part, word for word with its line breaks, and the writer in by. When they name writers for quotes, put every name in journal.quote_authors. Astera adds the sourced quotes it holds, and for each name in quotes_to_find you pull that writer's own words, with the source of each, into journal.quotes. Never tell them which writers Astera holds. The Astera Edit is Astera's own journal: the vision questions and a vision board, then months, weeks and a day over two pages. Make it, with journal.template set to edit, when they ask for it, and set journal.opening to leave out the vision pages they don't want. The vision board, the twelve questions, daily_prompts, morning_question and the phone app's reminders belong to the Astera Edit. Offer them for another journal only when the person asks. Changes the person makes in the browser stay in their browser, and astera_read cannot see them. A page this save changes replaces their version of that page when they open the link, and Undo in the editor brings theirs back. A page left as it was keeps their changes. journal.sets is the whole list of sets: send every set the journal keeps, with only what they asked for changed. Give the read link for a preview early, and the setup link when they want it in their account. New journals default to blank answers for handwriting. Print personal answers only when requested, and never write imaginary answers on their behalf. Astera makes physical journals that people write in with a pen. Respect requests to leave headings and blank answer space. Keep revising with the latest draft id. For the Astera Edit, prepare the journal, the editable vision board and the phone app together. Use the twelve questions to help them think as the conversation continues, and never require all twelve before creating the book. Turn their goal into short daily_prompts for them to edit; these print on every day page. Use companion.answer_keys independently of print mode, and companion.daily_reminders for the vision and how they want to live. Offer vision-board imagery using astera_vision_board. Create imagery with your image tools only when wanted, then supply it or help them upload it, and never call an image brief a finished board. Only original audio can be played back; offer recording or upload on the setup page if the host cannot export it. Ask about missing training-plan details rather than inventing a schedule. Use mixed mode and per-question answer_modes when only some of their own words should print. Explain what is suggested, what is still blank, and the weeks the draft covers.

Known tools 5

astera_questions

Read the twelve prompts that guide the conversation.

Inferred read-only
astera_vision_board

Read the approach to choosing and composing vision-board images, generating them with the host assistant when available, and linking them to daily prompts.

Inferred read-only
astera_exercises

The exercises in Astera's free workspace that you can fill for somebody, including their vision board.

Inferred read-only
astera_save

Build an editable physical journal from what the person has asked for and return its preview link, its setup link and its contents.

Inferred read-only
astera_read

What a draft holds now, so a conversation a week later can pick it up.

Inferred read-only

CONNECT WITH APPROVAL

Client installation

Review this server and its permissions before adding it. Secret placeholders must be set locally.

Codex

~/.codex/config.toml

[mcp_servers.astera]
url = "https://asterajournal.com/mcp"
enabled = true
Claude Code

.mcp.json

{
  "mcpServers": {
    "astera": {
      "type": "http",
      "url": "https://asterajournal.com/mcp"
    }
  }
}
Claude Desktop

Settings → Connectors → Add custom connector

Name: astera
Remote MCP URL: https://asterajournal.com/mcp

Add this remote URL as a custom connector in Claude Desktop. Availability depends on the user plan and workspace policy.

Cursor

.cursor/mcp.json

{
  "mcpServers": {
    "astera": {
      "url": "https://asterajournal.com/mcp"
    }
  }
}
Visual Studio Code

.vscode/mcp.json

Add to Visual Studio Code
{
  "servers": {
    "astera": {
      "type": "http",
      "url": "https://asterajournal.com/mcp"
    }
  }
}
Generic MCP

Client-specific MCP configuration

{
  "name": "astera",
  "transport": "streamable-http",
  "url": "https://asterajournal.com/mcp"
}
MCP Inspector

Run the official MCP Inspector locally and enter the indexed Streamable HTTP endpoint.

TRUST AND VERIFICATION EVIDENCE

Trust Data Available

BuiltWith Trust API v2 evidence for asterajournal.com was fetched 2026-10-13T14:22:03.136Z.

Trust status Trusted

asterajournal.com is assessed as Trusted: Domain runs a meaningful technology spend, consistent with a real business.

Indexed

Evidence is source-attributed and does not guarantee that a third-party server is safe. Risk labels are conservative metadata heuristics.