Armbrain

io.github.benfinkleaPublished by GitHub account benfinkleav1.0.0Updated Oct 24, 2026

AI memory layer for fractional CMOs -- client-partitioned minds, meeting prep, and EOS.

VerifiedStreamable HTTPWeb executableProductivity & WorkflowKnowledge & Memory

Overview

AI-generated overview

Armbrain is a remote MCP memory layer for fractional CMOs, giving an assistant client-partitioned memory, meeting prep and EOS support.

What you can do
Provides an AI memory layer aimed at fractional CMO work, with memory kept separate per client (client-partitioned minds). Supports meeting preparation and EOS (Entrepreneurial Operating System) workflows. No individual tools are listed, so specific actions are not documented in the supplied material.
When to use it
Worth considering if you are a fractional CMO or similar consultant who wants an assistant to retain client-specific context, prepare meetings and support EOS-style operating routines.
Requirements
A remote endpoint at api.armbrain.io over streamable HTTP. OAuth authentication is required; no environment variables or headers are declared.
Before you install
Requires OAuth sign-in to a third-party service, so client-related data you store or discuss is held by that provider. Memory is described as partitioned per client, but verify how separation and access are enforced before putting sensitive client information in it.

Installation

In SourceWeft

  1. Open Armbrain 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.benfinklea%2Farmbrain/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": {
    "armbrain": {
      "type": "http",
      "url": "https://api.armbrain.io/mcp"
    }
  }
}

README

This repository has no README.

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

60% 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.

  • License10 pts

    Declare a license in the repository or the registry entry.