MCP tools
The tools every connected app can call, and what each one does.
Alwen is an MCP server. Tools connect over HTTP and sign in with your Alwen account: the tool opens an Alwen page, you click Allow, and that's it. Disconnect any tool from Tools in Alwen at any time.
A few tools can't sign in through the browser and only take a fixed key. For those, open the tool in Tools and click Create a key: it's shown once, and the tool sends it as Authorization: Bearer alwen_…. A key opens your memory and nothing else, and Disconnect cancels it at once.
https://api.alwen.ai/mcpMemory
In a team, the user may also have shared vaults. search looks in every vault the tool may read and says which one each note is in. The other tools take an optional vault: a shared vault's name, or personal, the default. On Business, the user and the team choose which tools can read each vault.
| Tool | Use it to |
|---|---|
search(query, limit?) | Find notes before answering anything about the user's work. |
read_note(path) | Read a search hit in full. |
get_rules() | Get the user's compiled rules and profile, once per session. |
remember(text, title?, tags?) | Save something learned. Goes to the tool's inbox. |
log_decision(decision, reason?, alternatives?) | Record a decision and why, in the journal. |
propose_rule(rule, scope?) | Suggest a standing rule. Applies only after the user confirms. |
Work from @alwen
For agents that take research from @alwen by checking in, such as Grok Bot's routine. Builders don't use them: they get their work on GitHub.
| Tool | Use it to |
|---|---|
next_task() | Pick up the next task waiting for the user, with its task id: research, or building for a tool of the user's own that builds. |
task_done(task_id, findings, sources?) | Hand in the findings, or for a build the pull request link. They're saved to the memory, the job moves on, and the chat it came from hears back. |
Who wrote it
Alwen knows which tool signed in, so a tool never has to say who it is. Every write is signed with that tool (claude, cursor, grok-bot and so on): it decides which inbox folder a note lands in and appears in the commit message.