Skip to main content
Glama
134,818 tools. Last updated 2026-05-25 20:12

"Task management software alternatives to MCP Shrimp" matching MCP tools:

  • [STATE] Claim a Shillbot task. Returns an unsigned base64 Solana transaction the agent must sign locally with its wallet, then submit via shillbot_submit_tx with action="claim". Non-custodial — the MCP server never sees your private key. Requires a registered wallet (call register_wallet first). Optional `network`: 'mainnet' (default) or 'devnet'.
    Connector
  • Given a product ID, find similar products across the entire catalog. Useful for "more like this" recommendations or finding alternatives. Returns compact product cards, not full variant detail; call get_product for SKU-level variants, exact variant prices, merchant description, store info, and all images. Returns page and hasNextPage. Returns up to 20 results per page, paginated (max 3 pages).
    Connector
  • Check submissions for a task you published. Use this to see if a human has submitted evidence for your task. You can then use em_approve_submission to accept or reject. Args: params (CheckSubmissionInput): Validated input parameters containing: - task_id (str): UUID of the task - agent_id (str): Your agent ID (for authorization) - response_format (ResponseFormat): markdown or json Returns: str: Submission details or "No submissions yet".
    Connector
  • Browse and compare Licium's agents and tools. Use this when you want to SEE what's available before executing. WHAT YOU CAN DO: - Search tools: "email sending MCP servers" → finds matching tools with reputation scores - Search agents: "FDA analysis agents" → finds specialist agents with success rates - Compare: "agents for code review" → ranked by reputation, shows pricing - Check status: "is resend-mcp working?" → health check on specific tool/agent - Find alternatives: "alternatives to X that failed" → backup options WHEN TO USE: When you want to browse, compare, or check before executing. If you just want results, use licium instead.
    Connector
  • Submit completed work with evidence for an assigned task. After completing a task, use this to submit your evidence for review. The agent will verify your submission and release payment if approved. Requirements: - You must be assigned to this task - Task must be in 'accepted' or 'in_progress' status - Evidence must match the task's evidence_schema - All required evidence fields must be provided Args: params (SubmitWorkInput): Validated input parameters containing: - task_id (str): UUID of the task - executor_id (str): Your executor ID - evidence (dict): Evidence matching the task's requirements - notes (str): Optional notes about the submission Returns: str: Confirmation of submission or error message. Status Flow: accepted/in_progress -> submitted -> verifying -> completed Evidence Format Examples: Photo task: {"photo": "ipfs://Qm...", "gps": {"lat": 25.76, "lng": -80.19}} Document task: {"document": "https://storage.../doc.pdf", "timestamp": "2026-01-25T10:30:00Z"} Observation task: {"text_response": "Store is open, 5 people in line", "photo": "ipfs://..."}
    Connector

Matching MCP Servers

  • A
    license
    -
    quality
    D
    maintenance
    MCP 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.
    Last updated
    15
    537
    2,103
    TypeScript
    MIT
  • A
    license
    -
    quality
    C
    maintenance
    An intelligent task management system that provides structured workflows for AI Agents to plan, decompose, and execute complex programming tasks. It features a dedicated research mode for technical investigations and a task memory function to optimize workflows and avoid redundant coding work.
    Last updated
    1
    MIT

Matching MCP Connectors

  • Returns VoiceFlip MCP server health and version metadata. No authentication required. Use this first to verify the server is reachable from your MCP client.
    Connector
  • Apply to work on a published task. Workers can browse available tasks and apply to work on them. The agent who published the task will review applications and assign the task to a chosen worker. Requirements: - Worker must be registered in the system - Task must be in 'published' status - Worker must meet minimum reputation requirements - Worker cannot have already applied to this task Args: params (ApplyToTaskInput): Validated input parameters containing: - task_id (str): UUID of the task to apply for - executor_id (str): Your executor ID - message (str): Optional message to the agent explaining qualifications Returns: str: Confirmation of application or error message. Status Flow: Task remains 'published' until agent assigns it. Worker's application goes into 'pending' status.
    Connector
  • Apply to work on a published task. Workers can browse available tasks and apply to work on them. The agent who published the task will review applications and assign the task to a chosen worker. Requirements: - Worker must be registered in the system - Task must be in 'published' status - Worker must meet minimum reputation requirements - Worker cannot have already applied to this task Args: params (ApplyToTaskInput): Validated input parameters containing: - task_id (str): UUID of the task to apply for - executor_id (str): Your executor ID - message (str): Optional message to the agent explaining qualifications Returns: str: Confirmation of application or error message. Status Flow: Task remains 'published' until agent assigns it. Worker's application goes into 'pending' status.
    Connector
  • Browse and compare Licium's agents and tools. Use this when you want to SEE what's available before executing. WHAT YOU CAN DO: - Search tools: "email sending MCP servers" → finds matching tools with reputation scores - Search agents: "FDA analysis agents" → finds specialist agents with success rates - Compare: "agents for code review" → ranked by reputation, shows pricing - Check status: "is resend-mcp working?" → health check on specific tool/agent - Find alternatives: "alternatives to X that failed" → backup options WHEN TO USE: When you want to browse, compare, or check before executing. If you just want results, use licium instead.
    Connector
  • PRIMARY TOOL - Call this at the START of every conversation to load comprehensive user context. Returns: - current_datetime: Current date and time in the user's timezone (ISO 8601 with offset) - All active facts about the user (preferences, personal info, relationships) - tasks_overdue: Tasks with scheduled_date OR deadline in the past - tasks_today: Tasks scheduled OR due today (time >= now), plus unscheduled tasks (no date set) - tasks_tomorrow: Tasks scheduled OR due tomorrow (includes projected recurring tasks) - Active goals - Recent moments from the last 5 days - Latest 15 user-facing notes (id + description). Use get_note to retrieve full content. - ai_memory: Latest 15 AI memory notes from your previous sessions (id + description). Use get_note to retrieve full content. SELF-LEARNING: Review the ai_memory array — these are notes you saved in previous sessions about how to best assist this user. Load relevant ones with get_note. Throughout the conversation, save new learnings anytime via save_note with scope="ai_client" whenever you discover something worth remembering. - tasks_recently_completed: Tasks completed or skipped in the last 7 days Each task includes: - category_reason: 'scheduled' | 'deadline' | 'both' - explains why it's in that array - has_scheduled_time: true if task has a specific scheduled time, false if all-day - has_deadline_time: true if deadline has a specific time, false if all-day Task placement uses scheduled_date when present, otherwise deadline. Each task appears in exactly one category. For calendar events, the user should connect a calendar MCP (Google Calendar MCP, Outlook MCP) in their AI client. Query those MCPs alongside Anamnese for a complete daily view. This provides essential grounding for personalized, context-aware conversations.
    Connector
  • Sign out of your RealOpen MCP session. Use this when the user wants to switch accounts or disconnect.
    Connector
  • Rank LLMs for a stated purpose. Returns a shortlist with weights, scores, and plain-English rationale per pick. Use when the user wants to see and compare alternatives, not just one answer.
    Connector
  • Connectivity check — returns server version and current timestamp. Use to verify MCP server is reachable before calling other tools.
    Connector
  • Scores the current spelling of a personal name against the birth-date Life Path, suggests alternate spellings with harmony metrics, and echoes recommendation stub fields. SECTION: WHAT THIS TOOL COVERS Returns data.current_name metrics (expression, soul urge, personality, master and karmic flags, compatibility band, harmony_score 1..5) plus data.alternatives[] with identical shape per suggestion. data.recommendation is currently null (stub). Empty alternatives[] means no better spelling was found — still success. Not for business entities (asterwise_get_business_name_analysis) or mobile/vehicle checks. SECTION: WORKFLOW BEFORE: RECOMMENDED — asterwise_get_numerology_profile — baseline numbers before renaming advice. AFTER: None. SECTION: INPUT CONTRACT name and date strings only; upstream validates. SECTION: OUTPUT CONTRACT data.full_name (string) data.birth_date (string) data.life_path (int) data.current_name: name (string) expression (int) soul_urge (int) personality (int) is_master (bool) karmic_debt (int or null) compatibility (string — 'harmonious', 'neutral', or 'challenging') harmony_score (int — 1 through 5) data.alternatives[] — objects matching data.current_name shape data.recommendation (currently null — stub) SECTION: RESPONSE FORMAT response_format=json serialises the complete response as indented JSON — use this for programmatic parsing, typed clients, and downstream tool chaining. response_format=markdown renders the same data as a human-readable report. Both modes return identical underlying data — no fields are added, removed, or filtered by either mode. SECTION: COMPUTE CLASS MEDIUM_COMPUTE SECTION: ERROR CONTRACT INVALID_PARAMS (local — caught before upstream call): None — all validation is upstream. INVALID_PARAMS (upstream): — None — upstream rejection surfaces as MCP INTERNAL_ERROR at the tool layer. INTERNAL_ERROR: — Any upstream API failure or timeout → MCP INTERNAL_ERROR Edge cases: — Empty alternatives[] is valid when no improvement exists. SECTION: DO NOT CONFUSE WITH asterwise_get_business_name_analysis — entity Expression scan, not personal spelling alternatives. asterwise_get_chaldean_numerology — Chaldean compounds, not harmony-scored spelling list.
    Connector
  • Receipted write-through to PlanCrux's log endpoint. Appends a structured log entry to a task with optional evidence references and stage binding. Cannot change task or stage status (human-only), but records work done, findings, and blockers encountered.
    Connector