Alwen

ai.alwenPublished by alwen.aiOfficial publisherv0.4.0Updated Oct 26, 2026

One memory for every AI you work with: your rules, notes and decisions in your own Git repo.

VerifiedStreamable HTTPWeb executableKnowledge & Memory

Overview

AI-generated overview

Alwen is a remote MCP server that gives AI assistants one shared memory of your rules, notes and decisions, stored in your own Git repository.

What you can do
  • No tool list is published, so capabilities are described only at a high level.
  • Keeps a single memory of your rules, notes and decisions that every AI you work with can draw on.
  • Stores that memory in a Git repository you own, rather than in a vendor-side store.
When to use it
Worth considering if you use several AI assistants and want them to share the same persistent context, rules and past decisions, and you prefer that context to live in a Git repo you control.
Requirements
A remote MCP endpoint at api.alwen.ai over streamable HTTP. OAuth authentication is required, so you need an Alwen account and must complete the OAuth sign-in flow. No environment variables or headers are declared.
Before you install
The server is hosted by a third party and requires OAuth access to your account; review what scopes it requests. Your rules, notes and decisions are sent to that service and written into a Git repository, so avoid storing secrets or sensitive material there. No tool list is published, so what it can read or change cannot be verified in advance.

Installation

In SourceWeft

  1. Open Alwen in the dashboard and add it to a workspace.
  2. Connect the required credentials. They are stored privately and never shown on public pages.
  3. Enable the server for the chats that should use its tools.

Web executable via Streamable HTTP. Remote servers run from the web runtime once configured in a workspace.

Use with an agent

Paste this prompt into Claude Code, Codex, Cursor or another agent — or into SourceWeft chat. The agent reads this server's install guide, shows you its publisher, endpoint and sign-in, and adds it to your client once you agree. Keys never go into a command.

Read https://sourceweft.com/mcp/ai.alwen%2Falwen/install.md and connect the MCP server it describes to my client. Before changing any config, show me its publisher, endpoint and sign-in method and wait for my OK. Never put an API key in a command or in a file I would commit; ask me where it should come from.

Read the install guide the agent follows

Other MCP clients

Add this to your client's mcpServers config. The client completes OAuth sign-in on first connect.

{
  "mcpServers": {
    "alwen": {
      "type": "http",
      "url": "https://api.alwen.ai/mcp"
    }
  }
}

Tools

0
This server asks you to sign in, so SourceWeft could not read its tools without an account and has not indexed them. What a connected account sees can depend on that account and its permissions.

Version history

1
  1. v0.4.0LatestOct 22, 2026

Score

67% of the applicable checks met

How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.

  • Reached in the last 30 daysRequired25 pts
  • Auth declaredRequired10 pts
  • Tools listed15 pts

    Answer tools/list without a credential, or ship a package that starts in a sandbox without one.

  • DescriptionRequired15 pts
  • Logo10 pts
  • Documentation15 pts

    Declare a GitHub repository with a README, or serve resource_documentation in the OAuth protected-resource metadata.

  • LicenseNot applicable

    A hosted service is used under its provider's terms, so no license is expected here. This check is left out of the percentage.