MCP Shrimp Task Manager

Created By
cjo4m06a year ago
Shrimp Task Manager is a task tool built for AI Agents, emphasizing chain-of-thought, reflection, and style consistency. It converts natural language into structured dev tasks with dependency tracking and iterative refinement, enabling agent-like developer behavior in reasoning AI systems.
Overview

What is MCP Shrimp Task Manager?

MCP Shrimp Task Manager is an intelligent task management system designed for AI Agents, focusing on structured workflows, chain-of-thought reasoning, and style consistency in programming tasks.

How to use MCP Shrimp Task Manager?

To use the Shrimp Task Manager, install it via Smithery or manually set it up in your development environment. You can then interact with the system using natural language commands to plan, execute, and manage tasks.

Key features of MCP Shrimp Task Manager?

  • Intelligent task decomposition and planning
  • Dependency management for task execution
  • Real-time execution status tracking
  • Automatic task summary updates and memory function
  • Thought chain process for systematic problem analysis

Use cases of MCP Shrimp Task Manager?

  1. Managing complex programming tasks for AI development.
  2. Enhancing team collaboration through structured task management.
  3. Automating repetitive coding tasks to improve efficiency.

FAQ from MCP Shrimp Task Manager?

  • Can I use it for any programming language?

Yes! It is designed to work with any language supported by MCP-compatible clients.

  • Is there a user guide available?

Yes! Comprehensive documentation is provided to help users navigate the system.

  • How does the memory function work?

The memory function automatically saves task history, allowing for reference and learning from past tasks.

Project Info
Created At
a year ago
Updated At
a year ago
Author Name
cjo4m06
Star
383
Language
TypeScript
License
MIT 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)

9 hours ago
Alloy

2 days ago