Muse
Prepare your MindWiki vault for Muse: recall project context, work from source notes, and save the useful results of a conversation.
Availability
Directory launch pending. MindWiki’s Muse connector is in development. It has not been approved or listed in Muse’s reviewed connector directory yet, and live Muse verification is pending. These instructions describe the intended connection journey. If you cannot find MindWiki in Muse, it is not a problem with your vault.
You can prepare a free vault now. Wait for availability before upgrading specifically for Muse. See MindWiki + Muse for the current status and planned workflows.
Before you connect
- Use your existing MindWiki account, or create one and add a few notes.
- Confirm those notes have synced to MindWiki Cloud. The connector works with your cloud vault, not unsynced files on a device.
- MindWiki MCP access requires Pro or Power. Your Muse account must also be eligible for connectors under Muse’s current availability rules.
- Muse and MindWiki are separate services. Connecting an account does not buy a Muse subscription or include Muse usage in your MindWiki plan.
Connect when the listing becomes available
- Open MindWiki’s listing in Muse’s connector directory and start the connection.
- Muse should open a MindWiki sign-in and approval page. Verify that you are signing in on mindwiki.io and using the account that owns your vault.
- Review the requested permissions. Choose the least access needed for your task, then approve.
- Return to Muse and run the first-search check below.
The connection uses OAuth with PKCE. Do not paste your password, API key, or an authorization code into a Muse conversation. The hosted MCP endpoint is https://api.mindwiki.io/mcp; directory users should follow the listing’s connection flow rather than enter technical settings.
Choose your permissions
The updated MindWiki approval flow offers these access levels when the client requests compatible scopes:
| Access | What it enables |
|---|---|
| Read | Search and read pages, list vault context, inspect proposals and context packs |
| Read and capture | Read access plus saving new captures |
| Read and write | Read, capture, and editing or maintenance tools, subject to vault agent permissions |
Scope restrictions and vault agent permissions both apply. A tool may be visible to the client but reject an operation your connection cannot perform. Connecting does not automatically run MindWiki’s scheduled automations.
Verify your first search
Create a small note with a distinctive title, let it sync, then ask:
“Search MindWiki for my note titled Project North Star. Read the matching note and cite the source. If you cannot find it, say so.”
Check that the answer matches the note and that its source reference identifies the correct page. Muse should use MindWiki tools rather than guess from conversation history. Source links may require MindWiki authentication.
Verify your first save
If you granted capture or write access, ask:
“Save a new MindWiki capture titled Muse connection check. Include today’s date and the sentence: This is my connection test. Confirm the saved page.”
Open MindWiki and verify the new capture. A timeout does not prove that a write failed. The connector supports a stable operation key for safe retries; clients must reuse the same key and arguments. If you are unsure whether Muse used one, search for the capture before asking for another save.
Workflows to build on
- Project recall: “Find our launch decisions, read the source pages, and explain what remains unresolved.”
- Research brief: “Compare the evidence across these notes. Cite each source and distinguish my notes from your inference.”
- Context pack: “Find a relevant context pack for this project, or propose one from my notes for review.”
- Decision capture: “Save the decision, rationale, alternatives, sources, and owner from this conversation.”
- Organizing notes: “Propose changes, validate them, and show a dry run before asking me to approve.”
Tool availability in Muse depends on what its connector client exposes. MindWiki’s tool catalog describes server capabilities; it is not a guarantee that every client presents every tool. Connecting does not automatically import past Muse conversations.
Troubleshooting
| What you see | What to do |
|---|---|
| MindWiki is absent from the directory | Check availability. The reviewed listing is not live yet. |
| Sign-in uses the wrong vault | Cancel, sign into the correct MindWiki account, and restart the connection. |
| Approval was canceled | Start again from Muse when ready. Canceling should return you without granting new access. |
| Connection succeeds but access is denied | Check your MindWiki plan, granted scopes, and vault agent permissions. Reconnect if you need a different grant. |
| Search finds nothing | Confirm the note has synced, check the account, and try its exact title before a broad question. |
| Reading works but saving fails | Check capture/write access and the relevant agent permission. Do not repeatedly retry an uncertain write. |
| Muse says the connection expired or was revoked | Reconnect from Muse and complete a fresh approval. Never send tokens to support. |
| A result appears incomplete | Ask Muse to fetch the source page and distinguish retrieved facts from its own inference. |
For help, use Support or email support@mindwiki.io. Include the failing step, approximate time and timezone, error text, and client name. Remove passwords, tokens, authorization codes, and private note content.
Disconnect or change access
Open Account → Connections, find the Muse connection, and revoke it. You can also disconnect in Muse. To grant a different access level, reconnect and review the new approval. Revocation prevents future use of those credentials; it does not remove content already retrieved into a Muse conversation.
Muse Code is a separate setup
For the Muse coding CLI, use the Muse Code guide. CLI configuration is separate from the reviewed consumer connector directory and does not establish directory approval.