Vilix AI

io.github.AppfairlyPublished by GitHub account Appfairlyv1.0.0Updated Oct 24, 2026

Shared memory for connected AI tools. Projects, rules and skills over MCP. OAuth or API key.

VerifiedStreamable HTTPWeb executableProductivity & WorkflowKnowledge & Memory

Overview

AI-generated overview

Vilix AI is a remote MCP server that gives connected AI tools shared memory, along with projects, rules and skills.

What you can do
Share memory across connected AI tools so context carries between them and sessions. Organize work into projects. Apply rules and skills defined in the service. Connect over MCP using OAuth or an API key.
When to use it
Useful when you want several AI tools or assistants to draw on the same stored context, projects and rules instead of starting from scratch each time.
Requirements
A remote MCP endpoint at api.vilix.ai over streamable HTTP. Authentication is required, by OAuth or an API key. No local runtime, environment variables or headers are declared.
Before you install
Connecting requires OAuth authorization or an API key, so treat the credential as a secret. Memory and project content you store is held by the third-party service, so avoid putting sensitive material into shared memory.

Installation

In SourceWeft

  1. Open Vilix AI 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/io.github.Appfairly%2Fvilix/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": {
    "vilix-ai": {
      "type": "http",
      "url": "https://api.vilix.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. v1.0.0LatestSep 16, 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.