A
licenseNot graded
qualityD
maintenanceEnables automated timesheet management including creating entries, listing work activities, managing daily scrum updates, and viewing assigned projects with automatic authentication handling.
11 npm
MIT
Steady MCP
Related Servers
Alternatives to Steady MCP
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityCmaintenanceGenerates timesheets from activity data and automates submission to PSI Project Server (SharePoint-based systems) using browser automation. Works with Activity Collector MCP to fetch data from GitLab, GitHub, and Calendar services.17 npmMIT
- AlicenseAqualityBmaintenanceEnables Microsoft Teams chat automation, message extraction, and unread notification monitoring by automating the Teams web client with Puppeteer, requiring no API keys or Azure setup.511 npmMIT
- FlicenseAqualityDmaintenanceAutomatically collects daily report data from KPI systems using browser automation and Google OAuth login. Generates structured Markdown reports for specified date ranges with persistent session management.6-
- AlicenseNot gradedqualityBmaintenanceEnables building a daily standup from real GitHub activity and spoken notes, exposing tools to fetch a voice-ready summary, capture tasks, bugs and blockers, list and complete items, and file deduplicated GitHub issues. Output is voice-first, returning a short spoken version alongside markdown for the screen.MIT
- AlicenseAqualityDmaintenanceGenerates daily standup drafts from your actual GitHub, Jira, Linear, and Slack activity, grouping work items and detecting blockers.542 npmMIT
TDQS
A3.9/5.0
Scored across 5 tools
Disambiguation5/5
Each tool has a clearly distinct purpose with no overlap: steady_login handles authentication, steady_ping verifies session validity, steady_set_cookies stores authentication data, steady_list_teams retrieves team information, and steady_submit_checkin submits check-in data. The descriptions make it unambiguous which tool to use for each task.
Naming Consistency5/5
All tools follow a perfect consistent naming pattern: 'steady_' prefix followed by a verb_noun combination (e.g., steady_login, steady_list_teams, steady_submit_checkin). This provides excellent predictability and readability across the entire toolset.
Tool Count5/5
With 5 tools, this is well-scoped for a Steady check-in automation server. Each tool earns its place by covering essential authentication, verification, data retrieval, and submission functions without being overly sparse or bloated.
Completeness4/5
The toolset covers the core workflow for Steady check-ins: authentication (login/set_cookies), verification (ping), team selection (list_teams), and submission (submit_checkin). A minor gap exists in not providing tools for viewing past check-ins or managing multiple teams in batch operations, but agents can work effectively with the provided coverage.
Maintenance
ActivityInactive
ResponsivenessNo issues