Moveat

app.wemoveatPublished by wemoveat.appOfficial publisherv1.1.0Updated Nov 1, 2026

Coaching app for fitness coaches: read client check-ins and diets, write drafts the coach sends.

VerifiedStreamable HTTPWeb executableLocation & LifestyleCommunication & Collaboration

Overview

AI-generated overview

Remote MCP server for a fitness-coaching app that lets an assistant read client check-ins and diets and write drafts the coach sends.

What you can do
  • Read client check-ins and diet records from the coaching app
  • Write draft messages or responses for the coach to send
  • Support a coach's day-to-day client review workflow
When to use it
Useful for fitness coaches who already run their client check-ins and diets in this coaching app and want an assistant to review that data and prepare draft replies.
Requirements
A remote endpoint at the provider's site; OAuth sign-in is required. No environment variables or headers are declared.
Before you install
It handles clients' health and diet data, so check what the assistant can read and who can see it. It can write drafts that the coach sends, so review drafts before sending. Access is granted through OAuth to the coach's account.

Installation

In SourceWeft

  1. Open Moveat 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/app.wemoveat%2Fmoveat/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": {
    "moveat": {
      "type": "http",
      "url": "https://wemoveat.app/api/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

2
  1. v1.1.0LatestNov 1, 2026
  2. v1.0.0Sep 23, 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.