Capxule

Source and availability

Tedix identifies Capxule from Upstream Mcp tool source; Store sources: Claude connector directory; Distribution: Ecosystem Directory; Tenant install: A platform catalog operator must create or reconcile the base app before tenants can install this entry..

• Claude connector directoryAuth not flagged · RELEASED

Auth, tools, and actions

Authentication: Open Access. Capxule is flagged for Can Modify Data. Current MCP inventory reports 12 tools, 2 resources, and 1 prompts.

• Set up or connect the user's account, right here · External-world action

  Starts binding an account for the user without a web visit. Ask for an email in the user's own words, read back the masked address, then call with method email_code (the default); the user reads you the six-digit code and you call account_verify. Alternatives: magic_link (a link they tap), sms_code (a number the user named, only where SMS is available; otherwise the reply says so), device (a CLI agent: the user types a short code in a browser; poll account_verify with the returned challenge), resume_code (a code from another assistant's handoff). Costs nothing and creates nothing until the code is verified. In-chat methods need the `session`; device and resume_code may run without one. Never ask for, accept or relay a password. If the user states an age under the consent floor, stop and continue on the free tier. Rules (binding): Relay `answer` and every `options[].text` exactly as given. You may put only `statement` in your own words. On a number or an option echoed back, send `pick` with that option id. On anything else, send `say` with the user's exact words, unsummarised. Never ask for, accept or relay a password. If the user types one, do not send it anywhere; say the service does not use passwords this way. Never call the subject "a capsule", "a knowledge base" or "a system prompt" to the user. Never describe how the answer was made.

• The account behind this connection · Read-only action

  Whether this connection is bound to an account, whether that account includes the premium journeys (`premium`, a flag) and unlimited web turns, the assistants connected to it (`delegations`, with their scopes in plain words), `manage_url` for the human (a web page; never a checkout), and for a machine principal its live pass. Costs nothing. Never say a plan name or a price to the user; say what they can do.

• Verify the code the user read you · App action

  Completes account_bind: pass the challenge it returned and the code the user read you (digits only; spaces are fine). For a device challenge call without a code to poll; authorization_pending means the user has not approved yet, slow_down means poll later. Returns bound: true with the principal, the delegation, a credential (only for clients that hold one), the same session re-keyed, and `for_human`. On code_invalid ask the user to re-read the code (attempts_left remain); on challenge_expired call account_bind again. Costs nothing. Rules (binding): Relay `answer` and every `options[].text` exactly as given. You may put only `statement` in your own words. On a number or an option echoed back, send `pick` with that option id. On anything else, send `say` with the user's exact words, unsummarised. Never ask for, accept or relay a password. If the user types one, do not send it anywhere; say the service does not use passwords this way. Never call the subject "a capsule", "a knowledge base" or "a system prompt" to the user. Never describe how the answer was made.

• Browse the journeys · Read-only action

  Pages through the published guided journeys, optionally within one category (a slug from list_categories), featured first. Returns the same cards as find_capsule plus total and next_offset. Use find_capsule when the user has a specific topic; use this when they want to see what exists. Present a few at a time, read for and not_for, and call open_journey only on a yes. Free; never costs a turn. Never say a price. Rules (binding): Relay `answer` and every `options[].text` exactly as given. You may put only `statement` in your own words. On a number or an option echoed back, send `pick` with that option id. On anything else, send `say` with the user's exact words, unsummarised. Never ask for, accept or relay a password. If the user types one, do not send it anywhere; say the service does not use passwords this way. Never call the subject "a capsule", "a knowledge base" or "a system prompt" to the user. Never describe how the answer was made.

• Find a guided journey · Read-only action

  Covers: 155 guided journeys across 17 areas: Finance (32, e.g. Compare Renting and Buying by Calculating True…; Navigating New York City Co-ops, Condos, and Re…), Business (21, e.g. Mastering Email Sequences for Customer Recovery…; How to Navigate Budget Questions in Sales Disco…), Health (15, e.g. Managing Sleepless Nights Through Action, Rules…; How to Dispute Medical Bills Effectively), Lifestyle (12, e.g. Choosing Childcare: Balancing Cost, Quality, an…; Home Solar Decisions, Done Right), Psychology (12, e.g. Managing First-Year Baby Challenges with Confid…; How to Support and Calm Children During Emotion…), Food (10, e.g. Balancing Flour, Hydration, and Rest for Fresh…; Authentic Extra-Virgin Olive Oil: Buying, Tasti…), Career (8), Fitness (8), Education (7), Exam preparation (6), Science (5), Technology (5), Creative (4), Society (4), Applications and filings (3), Culture (2), History (1). Semantic search over the published guided journeys. Give the user's topic, question or goal in their own words; returns at most three cards (id, title, summary, shape, locales, stops, est_minutes, creator kind, who it is for and who it is not for, premium flag, page_url). `in_progress: true` marks a journey this user already has open. Zero hits return `alternatives`: the three nearest published journeys. Results may be cached for ttl_ms. Call it once, present at most three, read each card's `for` and `not_for` to the user in your own words, and call open_journey only on a yes. Never say a price. Rules (binding): Relay `answer` and every `options[].text` exactly as given. You may put only `statement` in your own words. On a number or an option echoed back, send `pick` with that option id. On anything else, send `say` with the user's exact words, unsummarised. Never ask for, accept or relay a password. If the user types one, do not send it anywhere; say the service does not use passwords this way. Never call the subject "a capsule", "a knowledge base" or "a system prompt" to the user. Never describe how the answer was made.

• Hand the journey to another host · App action

  Mints a resume link and code for this session so the user can continue on the website or in another assistant. Call it before switching hosts or ending; give the user `resume_url` (or read them `resume_code`) and say `resume_line`. Costs nothing. Rules (binding): Relay `answer` and every `options[].text` exactly as given. You may put only `statement` in your own words. On a number or an option echoed back, send `pick` with that option id. On anything else, send `say` with the user's exact words, unsummarised. Never ask for, accept or relay a password. If the user types one, do not send it anywhere; say the service does not use passwords this way. Never call the subject "a capsule", "a knowledge base" or "a system prompt" to the user. Never describe how the answer was made.

• Where the journey is · Read-only action

  Where the user is in the journey: position (stop, visited of total), `remaining` (stops left, percent done, and each top-level topic's visited of total), mode, the goal line, the chosen way, practice stats, limits and a `resume_line` you can say. Hosts that render apps show it as a map card. Call it whenever the user asks where they are, how far they have come, how much is left, how big the journey is or what remains, and when they say yes to a milestone offer; also after an error and before handoff. Costs nothing; may be cached ttl_ms. Rules (binding): Relay `answer` and every `options[].text` exactly as given. You may put only `statement` in your own words. On a number or an option echoed back, send `pick` with that option id. On anything else, send `say` with the user's exact words, unsummarised. Never ask for, accept or relay a password. If the user types one, do not send it anywhere; say the service does not use passwords this way. Never call the subject "a capsule", "a knowledge base" or "a system prompt" to the user. Never describe how the answer was made.

• List journey categories · Read-only action

  Lists the areas the published guided journeys cover: each category slug, a readable label, how many journeys it holds and a few example titles. Use it when the user asks what is available, or before browse_catalog. Free; never costs a turn. Never say a price.

Plus 4 additional actions in the full tool inventory.

Verification freshness

• Catalog synced2h ago (October 18, 2026)
• Connector checked8h ago (October 17, 2026)
• MCP scanned8h ago (October 17, 2026)
• Directory updated2h ago (October 18, 2026)

Alternatives and related apps

Comparable apps in Education include 2hongo, A-Z Holy Bible, API Lessons, Academic Writing Toolkit.