Steady

Local MCP server to submit Steady check-ins by driving Steady’s web form (no official Steady API)

javascript

GitHub Stars

javascript

Language

6 months ago

First Indexed

3 months ago

Catalog Refreshed

Documentation & install

Readme and setup notes from the catalogue, plus a client-ready config you can copy for your MCP host.

Installation

Add the following to your MCP client configuration file.

Configuration

View docs

{
  "mcpServers": {
    "sarthak-ignite-steady-mcp": {
      "command": "node",
      "args": [
        "<ABS_PATH_TO_REPO>/tools/steady-mcp/src/index.js"
      ],
      "env": {
        "STEADY_EMAIL": "you@company.com",
        "STEADY_BASE_URL": "https://app.steady.space",
        "STEADY_PASSWORD": "<YOUR_PASSWORD>",
        "STEADY_MCP_DEBUG": "0"
      }
    }
  }
}

You run a local MCP server that automates Steady check-ins by driving Steady’s web form. You use an MCP client to log in, discover your team, and submit today’s check-in with your chosen fields. This setup lets you delegate the check-in workflow to an AI helper while keeping your Steady login and session secure on your machine.

How to use

Authenticate and operate the local Steady MCP server from your MCP client to submit daily check-ins for your teams. You will log in once to obtain session cookies, then routinely generate and send check-in data for the target team.

Typical usage flow from your MCP client:

1. Run steady_login to authenticate and save cookies locally
1. Run steady_ping to verify authentication works
1. Run steady_list_teams to retrieve your team names
1. Run steady_submit_checkin to submit today’s check-in for a selected team

Example submission

{
  "team": "Everest AI",
  "previous": "Wrapped up CI fixes and reviewed PRs.",
  "text": "Next: finalize the MCP schema changes and update docs.",
  "blockers": "No blockers.",
  "mood": "calm"
}

Available tools

steady_login

Logs in to Steady and saves cookies locally (cookies.txt) and the curl cookie jar (cookiejar.txt) for session handling.

steady_set_cookies

Saves browser-provided cookies when automatic login isn’t possible, enabling fallback authentication.

steady_ping

Validates that authentication is active and the MCP can reach Steady.

steady_list_teams

Retrieves the list of team names/ids from Steady’s daily page for selection when submitting a check-in.

steady_submit_checkin

Submits a check-in for a specified team with fields like previous, text, blockers, and mood.

Built by

VeilStrat

AI signals for GTM teams