Heart

me.heart-ofPublished by heart-of.meOfficial publisherv1.0.0Updated Nov 7, 2026

Your Heart workout log: workouts, records, templates, programs. Holds no health data.

VerifiedStreamable HTTPWeb executableLocation & LifestyleProductivity & Workflow

Overview

AI-generated overview

Remote MCP endpoint for the Heart of Yours fitness app, giving an assistant access to a user's workout log: workouts, records, templates and programs.

What you can do
  • Work with the user's workout log: workouts, personal records, templates and programs, per the registry description.
  • The manifest lists no individual tools, so the exact operations are not documented here.
  • The backend behind it also serves an exercise library and app content, but the README does not say which of these the MCP endpoint exposes.
When to use it
When you want an assistant to read or work with a Heart of Yours training log — reviewing workouts, records, saved templates or programs — without leaving the chat.
Requirements
A remote streamable HTTP endpoint at mcp.heart-of.me; OAuth authentication is required. No environment variables or headers are declared. The README describes a Firebase-authenticated backend, but the MCP endpoint's own auth flow is not detailed.
Before you install
OAuth sign-in grants the assistant access to your account's workout data; check what scopes are requested. The registry description states the server holds no health data, so do not assume medical or health metrics are available. The README documents deployment and database workflows (migrations, CI deploys) that are not described as MCP tools.

Installation

In SourceWeft

  1. Open Heart 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/me.heart-of%2Fheart/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": {
    "heart": {
      "type": "http",
      "url": "https://mcp.heart-of.me/"
    }
  }
}

README

Heart of Yours

Backend for the Heart of Yours fitness app. Dart server on AWS Lambda behind API Gateway, Postgres via Supabase, all CDN/storage on AWS.

Repository layout

heart-go/├── api/                       # Dart server (Lambda entrypoint)├── shared/│   ├── heart_models/          # Data classes + service interfaces (used by api + the Flutter client)│   └── heart_aws/             # Boto3-shaped AWS clients (S3, SQS, SNS, Scheduler) on aws_signature_v4├── database/│   ├── migrations/            # Forward-only SQL migrations│   ├── tests/                 # pgtap suite — public/{tables,functions}, archive/...│   └── test_utils/            # Test helpers (builders + JSON validators)├── firebase/                  # Python Lambda: FCM push + Firebase auth cleanup (uv workspace member)├── assets/                    # Python Lambda: exercise media processing pipeline (uv workspace member)├── infrastructure/            # Terraform stacks (api, assets, cdn, content, firebase, monitoring)│                              # + environments/{dev,prod} — see infrastructure/README.md├── content/                   # Exercise library YAML + schema + sample templates JSON, synced to CDN├── scripts/                   # Migration runner, db test runner, library sync/validation├── site/                      # Static marketing/legal pages├── docs/                      # Dated design docs; handoff.md is the definition of done, style.md the house style├── agents/                    # Autonomous agent launchers + guard hook (see agents/README.md)└── .github/workflows/         # CI: deploy-api, deploy-assets, deploy-firebase, exercise-library                               # (each split into a reusable workflow + dev/prod wrappers)

Per-component docs:

Stack

LayerTech
Server runtimeDart 3.10 + relic, compiled to native + Lambda Web Adapter
StoragePostgres (Supabase), no ORM — raw SQL
Object storage / CDNS3 + CloudFront
AuthFirebase OIDC token verification
AsyncEventBridge S3-rules → SQS → /events (Lambda routes events back to itself)
Scheduled jobsEventBridge Scheduler → SQS → /events
Side servicesPython 3.13 Lambdas in a uv workspace: firebase/ (push, auth cleanup), assets/ (media)
IaCTerraform (with Supabase provider)
CI/CDGitHub Actions, OIDC role for AWS
TestsDart test + mockito for app code, pgtap for the database, pytest for the Python services

Local development

bash
make bootstrap   # dart pub get + mocks for all packages, uv sync, git hooksmake db-up       # containerized Postgres 17 + pgtap (skip if you run a native one)make test        # the full matrix: Dart x3, migrations + pgtap, pytest x3make lint        # dart analyze x3 + ruff

Each suite can also run individually — make test-dart / test-db / test-python, or the underlying commands directly (see the Makefile and per-component READMEs).

The api package can be run locally against any Postgres + AWS profile — see api/README.md.

Deployment

Every workflow family is a reusable workflow plus thin -dev / -prod wrappers. Dev ships from main pushes. Prod: api and exercise-library ship from v* tags; assets and firebase prod deploys are currently manual (workflow_dispatch). Pull requests run the test jobs only — the deploy jobs are gated on the event type.

deploy-api.yml (api/shared/database changes):

  1. Lint, format check, analyze
  2. Dart tests across all three packages
  3. Database tests: ephemeral Postgres + pgtap via scripts/db_tests.sh, then the full api suite (including db-tagged integration tests) with a coverage floor
  4. Apply unapplied migrations to Supabase
  5. Build Lambda binary, update function, smoke-test /version

deploy-firebase.yml / deploy-assets.yml (Python changes): pytest, then package and update the function code.

exercise-library.yml (content changes): validate the library YAML against its JSON schema plus the sync parser, then sync exercises + translations to Postgres (guarded against mass-archiving).

Conventions

  • Migrations are forward-only. No down migrations. Wrong schema → write a new migration that fixes it.
  • No comments unless the WHY is non-obvious — naming carries the WHAT.
  • Single source of truth for shapes. Anything the client sees lives in heart_models; server-only types stay in api/lib/models.
  • Boto3-shaped AWS package — generic, no domain knowledge in heart_aws.

Licence

The server and everything else in this repository is under the GNU AGPL v3.0. The shared packages (shared/heart_models, shared/heart_aws, shared/heart_design) are under the Apache License 2.0, and the exercise library and other content in content/ under CC BY 4.0. The name and logo aren't covered by any of them. NOTICE has the full map, including what in the repository isn't ours. The reasons are in docs/2026-10-24.licence.md.

Contributing

Contributions come in under the licence of the directory they change (inbound = outbound): AGPL for the server, Apache-2.0 for the shared packages, CC BY 4.0 for content/. Opening a pull request means you agree to that and that the work is yours to give. There is no CLA.

Source: README.md at commit 5edff5e

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.0LatestOct 31, 2026

Score

85% 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
  • License10 pts