async-sheet-mcp
Related Servers
Alternatives to async-sheet-mcp
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityCmaintenanceAn MCP server that enables AI agents to read, create, and modify Google Spreadsheets through actions like editing cells and managing sheets. It features a specialized handoff protocol to synchronize tasks and state between different LLMs using a shared spreadsheet log.599 npmMIT
- AlicenseAqualityBmaintenanceSelf-hosted task tracker and MCP server for AI coding agents. Append-only case files preserve decisions, failed attempts, questions, and check results across sessions. A live web board lets people track progress and answer agents. Runs locally in Docker and connects to Claude Code, Codex, Cursor, and other Streamable HTTP MCP clients. MIT licensed.306MIT
- AlicenseBqualityBmaintenanceEnables AI coding agents on different machines and accounts to work one repository as a team by declaring file and symbol claims before editing, so collisions are refused up front rather than discovered at merge. It also supports delegating tasks between teammates' agents, which do the work with their own tokens and commit, with replies, commit shas, claims and messages landing on one shared board.202MIT
- FlicenseAqualityBmaintenanceOne shared project for your team's Claude Code, Codex, Cursor and OpenCode agents: a task board, decisions and handoffs. Everyone keeps their own plan.1358-
- AlicenseNot gradedqualityBmaintenanceEnables AI agents to create, format, and verify Google Sheets with native tables, themes, validation, linting, rendering, and safeguards for human-edited spreadsheets.MIT
- AlicenseNot gradedqualityBmaintenanceEnables AI tools to seamlessly hand off work by creating, accepting, and completing standardized Markdown handoff documents, so a task can move between different AI assistants without repeating context.MIT
TDQS
Scored across 7 tools
Each tool targets a distinct resource+action: tabs (list_tabs/read_tab), issues (list_issues/get_issue), and three distinct write targets (append_comment, set_status, add_issue). The only mild overlap is read_tab, which can also dump the issues tab and thus partially duplicate list_issues, and get_issue returns linked-tab text that read_tab could also fetch; descriptions resolve this but do not eliminate it.
All seven names use snake_case verb_noun form (list_tabs, get_issue, append_comment, set_status, add_issue), which is highly predictable. Minor deviation: retrieval verbs are mixed (list/get/read), so an agent cannot guess whether a fetch is called get_* or read_* without looking.
Seven tools is well inside the ideal 3-15 range and each maps to a real workflow step (navigate tabs, browse/filter issues, inspect one issue, append a comment, change status, register a new issue). Nothing looks redundant or padded.
The issue lifecycle is largely covered: create (add_issue), read at summary and full detail level, status transition (set_status), and comment append — a sensible surface for a shared sheet tracker. Gaps remain: no way to edit existing 問題點/모드/모델 fields or delete/reopen a row other than via set_status, and no search beyond a status filter, though append_comment partially compensates.