Shrimp Task Manager

Created By
cjo4m06a year ago
Shrimp Task Manager 透過結構化的工作流程引導,協助 Agent 系統性規劃程式開發步驟,強化任務記憶管理機制,有效避免冗餘與重複的編程工作。
Overview

What is Shrimp Task Manager?

Shrimp Task Manager is an intelligent task management system based on the Model Context Protocol (MCP) that assists AI agents in efficiently planning programming workflows.

How to use Shrimp Task Manager?

To use Shrimp Task Manager, install it via Smithery or manually set it up in a compatible client like Cursor IDE, and configure it according to your project needs.

Key features of Shrimp Task Manager?

  • Task planning and analysis to understand complex requirements
  • Intelligent task splitting into manageable sub-tasks
  • Dependency management to ensure correct execution order
  • Real-time tracking of task execution status
  • Verification of task completeness against expected outcomes
  • Automatic updates of task summaries upon completion

Use cases of Shrimp Task Manager?

  1. Planning and executing software development tasks
  2. Managing dependencies in programming projects
  3. Automating task summaries for better memory management

FAQ from Shrimp Task Manager?

  • Can Shrimp Task Manager be used with any programming language?

Yes! It can be integrated with any client that supports the Model Context Protocol.

  • Is there a specific environment required to run Shrimp Task Manager?

It is recommended to use Node.js and TypeScript for optimal performance.

Project Info
Created At
a year ago
Updated At
a year ago
Author Name
cjo4m06
Star
-
Language
-
License
-

Recommend Servers

View All
Bring your real authenticated browser session to AI coding agents. Local-first MCP server + Chrome MV3 extension. No cloud. No telemetry.
@Cubenest

peek records the user's actual logged-in browser (DOM via rrweb, console events, network metadata, optional response bodies via opt-in Deep capture) through a Chrome MV3 extension. The extension ships events through a native-messaging stdio bridge to a local MCP server (peek-mcp), which persists them to a SQLite database at ~/.peek/sessions.db. AI coding agents (Claude Code, Cursor, Cline, Windsurf) read sessions from the database via 10 MCP tools: Tool What it does list_recent_sessions List recently recorded sessions (id, origin, ts, event count). get_session_summary LLM-readable narrative summary of a session. get_session_console_errors Console errors recorded in a session. get_session_network_errors Failed/notable network requests in a session. get_user_action_before_error Last N user actions before a console error. generate_playwright_repro Generate a runnable Playwright test from a session. get_dom_snapshot Reconstruct the DOM at a given timestamp. query_dom_history Timeline of attribute/text changes for a selector. request_authorization Side-panel consent for write actions (Level 3). execute_action Dispatch a UI action (gated by permission level + destructive blocklist). Why local-first matters Every other "browser session for AI" tool ships to a vendor cloud. peek's SQLite + extension live on the user's machine — no remote endpoints, no telemetry. The privacy policy (docs/peek/PRIVACY_POLICY.md) is the source of truth. Install # 1. Add the MCP server to Claude Code claude mcp add peek -- npx -y @peekdev/mcp # 2. Install the Chrome extension from the Chrome Web Store # (link added once the CWS listing is approved)

a day ago