shrimp-task-manager-lds-http

Shrimp Task Manager guides AI agents through structured task planning, analysis, execution, verification, and persistent project task management via MCP.

От сообществаРаботаетБез входаГлобальныйБесплатноТолько чтение

Что умеет

  • Plan Task: When you need to plan tasks or construct complex features, you can use this tool to receive task planning guidance. You are expected to strictly follow the step-by-step instructions provide
  • Analyze Task: Deeply analyze task requirements and systematically examine the codebase, assess technical feasibility and potential risks, if code needs to be provided use pseudocode format and only pr
  • Reflect Task: Critically review analysis results, assess solution completeness and identify optimization opportunities, ensure solutions conform to best practices, if code needs to be provided use pse

Какие данные видит

Нужен ли аккаунт

Не нужен: сервер работает без входа

Shrimp Task Manager guides AI agents through structured task planning, analysis, execution, verification, and persistent project task management via MCP.

Как подключить

Как подключить shrimp-task-manager-lds-http к Claude

Адрес сервера, который нужно вставить в настройках Claude:

https://shrimp-task-manager-lds-http--ldsphm24.run.tools

  1. Откройте Claude (сайт claude.ai или приложение для компьютера).
  2. Перейдите в Настройки → Коннекторы (в английском интерфейсе: Settings → Connectors).
  3. Нажмите Добавить пользовательский коннектор (Add custom connector).
  4. Вставьте адрес сервера, скопированный ниже, в поле URL удалённого MCP-сервера и нажмите Добавить.
  5. В чате нажмите + → Коннекторы и включите новый коннектор.

Пользовательские коннекторы доступны на тарифах Free, Pro, Max, Team и Enterprise. На Free можно добавить только один. В Team и Enterprise коннектор сначала добавляет владелец организации в Настройки организации → Коннекторы.

Авторизация

После нажатия Добавить откроется окно входа в сервис. Войдите под своим аккаунтом и подтвердите доступ. Пароль Claude не видит.

Как подключить shrimp-task-manager-lds-http к ChatGPT

Адрес сервера, который нужно вставить в настройках ChatGPT:

https://shrimp-task-manager-lds-http--ldsphm24.run.tools

  1. Откройте ChatGPT в браузере (chatgpt.com). Нужен тариф Plus, Pro, Business, Enterprise или Edu.
  2. Один раз включите режим разработчика: Настройки → Приложения → Дополнительные настройки → Режим разработчика (Settings → Apps → Advanced settings → Developer mode).
  3. Откройте Настройки → Коннекторы и нажмите Создать (Create).
  4. Заполните форму: Название (любое), Описание (одна фраза, что делает сервис), URL MCP-сервера (скопируйте ниже).
  5. В поле Аутентификация выберите OAuth, если сервис требует вход, иначе Нет. Нажмите Создать.
  6. В новом чате откройте + → Приложения/Коннекторы и включите коннектор.

Название раздела у OpenAI менялось (Connectors → Apps/Plugins). Если пункт называется иначе, ищите «режим разработчика» в настройках. В рабочих пространствах Business/Enterprise администратор должен разрешить пользовательские коннекторы.

Авторизация

При первом использовании ChatGPT откроет окно входа в сервис. Войдите и подтвердите доступ.

Как подключить shrimp-task-manager-lds-http к Cursor

Адрес сервера, который нужно вставить в настройках Cursor:

https://shrimp-task-manager-lds-http--ldsphm24.run.tools

Быстрый способ: нажмите кнопку Открыть в Cursor ниже, Cursor сам предложит добавить сервер.

Вручную:

  1. В Cursor откройте Settings → Cursor Settings → MCP и нажмите Add new global MCP server.
  2. Вставьте JSON, скопированный ниже, в открывшийся файл ~/.cursor/mcp.json (для одного проекта: .cursor/mcp.json в корне проекта).
  3. Сохраните файл. Сервер появится в списке MCP; при необходимости пройдите авторизацию по кнопке рядом с ним.

Авторизация

Если сервис требует вход, рядом с сервером в списке MCP появится кнопка авторизации.

Список инструментов сервера (15)

Технические названия из tools/list. Нужны только разработчикам.

plan_taskWhen you need to plan tasks or construct complex features, you can use this tool to receive task planning guidance. You are expected to strictly follow the step-by-step instructions provided by the tool when organizing your tasks. You may optionally choose to reference existing tasks for extended planning. **Critical Warning**: All forms of `assumptions`, `guesses`, and `imagination` are strictly prohibited. You must use every `available tool` at your disposal to `gather real information`.
analyze_taskDeeply analyze task requirements and systematically examine the codebase, assess technical feasibility and potential risks, if code needs to be provided use pseudocode format and only provide high-level logic flow and key steps avoiding complete code
reflect_taskCritically review analysis results, assess solution completeness and identify optimization opportunities, ensure solutions conform to best practices, if code needs to be provided use pseudocode format and only provide high-level logic flow and key steps avoiding complete code
split_tasksBreak down complex tasks into independent subtasks, establishing dependencies and priorities. ## 1. **Granularity Control (Required Reading)** - ### **Minimum Viable Task** Each subtask should be completable and verifiable by a single developer within **1–2 working days** (approximately 8–16 hours). - ### **Maximum Complexity Limitation** A single subtask should not span multiple technical domains such as **frontend**, **backend**, and **database**. If cross-domain work is required, split it into multiple subtasks. - ### **Recommended Number of Tasks** Avoid splitting into more than **10 subtasks** at once. If more are needed, submit them in prioritized batches (6–8 tasks per batch). - ### **Recommended Task Length** Each split should not exceed **5,000 characters**. If it does, divide and submit in multiple batches. - ### **Depth Limitation** The task tree should not exceed **3 levels**: - **Level 1**: Functional Modules - **Level 2**: Main Processes - **Level 3**: Key Steps ## 2. **Task Splitting Example** - Identify **core functionality points**, and create a subtask for each. - Annotate each subtask with: - **Input/Output** - **Acceptance Criteria** - If needed, provide **pseudocode**: - Only outline high-level logic and key steps. - Avoid providing complete source code. - Check **dependencies** between subtasks and specify them in the `dependencies` field. - If the task involves interface design, always provide a complete and consistent definition, including: - Function/class/schema definitions (including names, parameters, return values) - Data types, usage descriptions, and optional/required status for each item - Error handling methods and expected exception scenarios - Dependency and naming conventions (if any) - Sample data and usage examples This ensures consistency, readability, and development precision between tasks. ## 3. **Dependencies and
list_tasksGenerate structured task lists, including complete status tracking, priorities, and dependencies
execute_taskRetrieve the instructional guidance for a specific task. You will complete the programming task based on this guidance. You must strictly follow the feedback and instructions provided by the tool — it is designed to **guide you toward perfect task completion, not to execute the task for you**. Severe Warning: Calling the executeTask tool does not mean you have completed the task. You must follow the step-by-step guidance returned by the tool to complete the task properly.
verify_task## Verify Task Please comprehensively check and score according to the requirements in verificationCriteria, If you are missing or have forgotten the verificationCriteria content, please use `get_task_detail` to obtain it. Please score according to the following rules: ### Verification Standards 1. **Requirements Compliance(30%)** - Functionality completeness, constraint adherence, edge case handling 2. **Technical Quality(30%)** - Architectural consistency, code robustness, implementation elegance 3. **Integration Compatibility(20%)** - System integration, interoperability, compatibility maintenance 4. **Performance Scalability(20%)** - Performance optimization, load adaptability, resource management ### score Parameter Guidelines Provide overall score and rating, assessment of each standard, issues and suggestions, and final conclusion. **Must use the following format to provide scoring results (for system parsing):** ```Scoring score: [number from 0-100] ``` ### summary Parameter Guidelines If the score is equal to or greater than 80 points, please provide a task summary ``` summary: 'Task completion summary, concise description of implementation results and important decisions' ``` If the score is less than 80 points, please provide correction suggestions ``` summary: 'List task issues and correction suggestions' ```
delete_taskDelete incomplete tasks, but does not allow deleting completed tasks, ensuring the integrity of system records
clear_all_tasksClear incomplete tasks and reset the task list. This is a destructive operation that requires confirmation. Completed tasks will be backed up before clearing.
update_taskUpdate task content, including name, description and notes, dependent tasks, related files, implementation guide, and verification criteria, completed tasks only allow updating summary and related files
query_taskSearch for tasks based on keywords or ID, display abbreviated task information
get_task_detailRetrieve complete detailed information of a task based on task ID, including untruncated implementation guides and verification criteria
process_thoughtConduct flexible and evolvable thinking processes, progressively deepen understanding and generate effective solutions through establishing, questioning, verifying, and correcting ideas. When encountering situations requiring data collection, analysis, or research, prioritize reviewing project-related code; if relevant code does not exist, query the web rather than speculate. Set nextThoughtNeeded to false when thinking is sufficient, otherwise adjust total_thoughts to extend the process
init_project_rulesInitialize project standards, call this tool when the user requests to generate or initialize a project standards document, also call this tool if the user requests to change or update project standards
research_modeWhen you need to conduct in-depth research on programming-related topics, you can use this tool to enter a specialized research mode. This tool will guide you on how to use web search and code search tools to systematically research technical topics, ensuring research depth and breadth while avoiding topic deviation. Suitable for technical research, best practice exploration, solution comparison, and other scenarios.