Skip to main content
Glama
521,385 tools. Updated 2026-09-06 10:57

"Resources for completing coding tasks" matching MCP tools:

  • Browse tasks on the marketplace. Defaults to open (``posted``) tasks. Filters are plain-column matches — to filter by requirements (capabilities, min_trust), use ``find_agents_for_task`` for ranked, requirement-aware matching; this tool's own filters stay plain-column. Args: access_token: AgentAuth bearer token (requires ``market.read``). status: Task status to filter on. Defaults to ``"posted"`` (open tasks). Pass any valid status to see tasks in other states. task_type: Optional exact-match task type filter. limit: Maximum results, 1-100. Default 20. Returns: ``tasks`` (list, newest first), ``total`` (count returned), and the applied ``filters``. ``{"error_code": "invalid_input", ...}`` listing the valid values if ``status`` is not a real task status.
    ConnectorNo auth
  • Quick scan for a PENDING task. Returns the task directly if one is available, or None if no task is ready within the timeout. Default timeout is 5s (non-blocking). The agent should NOT loop on this — tasks arrive via relay push. This is a fallback for when the agent wants to check for tasks without waiting for a relay. No args needed — the role is auto-detected from posture (.brain/posture/current.json) or NUCLEUS_AGENT_ROLES env var.
    ConnectorNo auth
  • Use this when the user explicitly asks to create or modify multiple Familia tasks, list tasks, plans, or task attachments in one request, or when one prompt contains multiple standalone dated actions that should become separate tasks. When the same task or plan repeats, use repeatRule/rrule on one operation instead of creating duplicate one-time operations. For a main event/trip plus clearly related dated actions, prefer one create_plan operation with relatedTasks. Internally this runs bounded individual write operations one by one; it does not create a backend transaction.
    Connector
    Destructive
    No auth
  • Publish a task to make it visible to operators. Works for both settlementMode='escrow' and 'direct' tasks. The task must be in Draft or Funded status. For escrow Draft tasks: funds are automatically reserved and locked from your wallet (requires sufficient balance). For direct-settlement Draft tasks: no funding happens — the task goes directly from Draft to Published because the client pays the operator on-site (no escrow). This is the intended shortcut for direct-settlement. For Funded tasks (after escrow Quote → Fund flow): the funds are already locked, the task is simply made visible. After publishing, operators can accept the task. Requires authentication. Next: wait for task.accepted via get_task_events or webhook.
    ConnectorNo auth
  • Returns the canonical guide for using TMV from a coding-agent context. Covers the fix-test-retest loop, how to write a good test prompt, how to read the actionTrail / consoleErrors / failedRequests outputs, and common gotchas. Call this first if you're a new agent on a project — it'll save you a debug session. The same content is served at https://testmyvibes.com/docs/coding-agents.
    ConnectorNo auth
  • Abort an unpaid checkout and release its checkout_id. Use if the customer changes their mind after create_checkout but before completing payment. Has no effect on orders already confirmed by webhook. To restart, create a new cart and checkout from scratch.
    ConnectorNo auth

Matching MCP Servers

Matching MCP Connectors

  • Recurring agent jobs that run on our servers and ping you only when the result changed.

  • Zoom Tasks server for creating, updating, assigning, and synchronizing task workflows.

  • Submit the result payload for a job the calling agent has claimed, completing the job workflow. Bearer token required. Safe to retry with the same idempotency_key.
    ConnectorNo auth
  • Read tasks from a 'todo' board with server-side filtering — handy for 'what's overdue?' / 'what's assigned to X?' without pulling the whole board. All filters are optional and AND together: `assignee` (exact match), `priority` ('H'|'M'|'L'), `done` (boolean), `overdue` (true → due_date strictly before today, not done), `due_before` / `due_after` (ISO date window on due_date). Returns `{ boardId, mode, tasks }` — tasks ordered by sort, each with the same fields as `list_tasks`.
    ConnectorNo auth
  • Search the TensorFeed Agent Self-Directory for hireable AI agents. Filter by skill (from a controlled vocab including research, data-analysis, coding, content-writing, voice-acting, image-generation, etc), service_area (research/data/coding/writing/voice/image/video/other), language (BCP 47), availability, hourly rate cap, minimum years of experience, or verified-hireable status. Verified-hireable members (operators paying $5 USDC/30 days for top-tier visibility) sort first. Free tier capped at 25 results. Returns wallet, display_name, operator_url, skills, rates, languages, years_experience, composite reputation rank, trust grade. TF publishes self-descriptions; TF takes no fee from off-platform transactions between operators and the agents who contact them.
    ConnectorNo auth
  • Return the prioritized, pillar-tagged (FIND / READ / USE) action plan for a completed audit, deduplicated across sources, with machine-actionable implementation steps included on fixes where available. Use this when you want the to-do list to act on (or hand to a coding agent), rather than the scores or section detail.
    ConnectorNo auth
  • Search detailed documentation for Strudel live coding or ABC/ABCJS notation. Returns relevant code examples and explanations from the official docs. Use this when the curated guides (get-strudel-guide, get-music-guide) don't cover what you need — for specific functions, advanced techniques, or when you're unsure about syntax. Powered by semantic search over strudel.cc and ABCJS docs.
    ConnectorNo auth
  • Create multiple tasks in a project in one action. Use this instead of calling create_task multiple times when the user asks to create several tasks at once. All tasks are created atomically — if validation fails for any item, nothing is created.
    ConnectorOAuth
  • Fetch the full AgentRouting record for a specific vendor, wrapped in a feedback request envelope. vendor_id is the slug form used throughout the catalog, e.g. "booking-com", "delta", "navan". Get valid vendor_ids from lookup_vendors() first. The response has two top-level fields: - data: the complete AgentRouting record with all protocol entries - outpost_dispatch: instructions for filing a field report after interacting with this vendor, including a pre-filled field_report_template ready to pass to report_to_outpost() or POST to the fallback_url If an AgentContext record exists for this vendor, data will also contain a context_advisory field with an advisory_url. Fetch that URL before completing any transaction - it contains verified discrepancies and human handoff guidance based on independent research. In data.protocols, each entry has a status: confirmed_present - checked and found, with endpoints/auth/notes where present not_found - checked and nothing found (not a failure, just absence of evidence) unable_to_verify - check was structurally blocked (e.g. requires live browser) confirmed_absent - vendor-side evidence explicitly confirms non-support After completing your task, close the loop by calling report_to_outpost with the field_report_template from outpost_dispatch.
    ConnectorNo auth
  • List curated loadouts — deliberately-assembled kits of MCP servers + governance + plays for a specific job (GTM, coding, research, support, infra). The agent-facing version of the /loadouts product. Use get_loadout for the full kit with live trust.
    ConnectorNo auth
  • Enter a tournament after completing the eligibility sequence: register_agent → verify_agent → win a practice battle with register_for_battle/get_battle_prompt/submit_output/get_result. Returns confirmation, tournament registration_id, bracket_position, and schedule. Not needed for the instant FREE Gladiator Badge flow.
    ConnectorNo auth
  • Returns the issue trackers connected to a team (Jira, Linear) and what each of them can do: search for tasks, list iterations (sprints, cycles), write estimates back. Call this first — the other poker tools depend on what is connected. An empty list means tasks can only be added manually with poker.game.tasks.add.
    ConnectorNo auth
  • Create a Gantt chart from a task list — no account or API key needed. YOU author the plan: list the tasks in execution order with realistic working-day durations and dependencies (0-based positions of earlier tasks; use { task, type, lag } for start-to-start/finish-to-finish links or lag). Milestones have duration 0. Only add a dependency where a task truly needs another one finished - independent tasks should run in PARALLEL (share a predecessor, or take no dependencies at all and start at the project start). Group tasks into top-level phases for a structured plan/WBS: the phase task gets isPhase: true, its tasks get parent = the position of the phase. LoopGantt schedules it with its critical-path engine and returns a picture of the chart, the dates, the critical path and a link where the user can view, export (PNG/PDF) and save the chart. Always show the user the link. Tasks with a due date take deadline: YYYY-MM-DD (a marker - the reply reports the fit). Use create_gantt when the user wants a chart to open, export or save; use schedule_project instead for what-if date math where nothing should be stored.
    ConnectorNo auth
  • Get a coherent set of sounds for an app or game in one call — one sound per role (click, toggle, swipe, pop, alert, notification, confirm, success, error; or pickup/jump/hit/powerup/laser/explosion/gameover for retro-game), picked by measured acoustics so they sound like one product. Use it when the user wants a whole kit rather than one event; for a single event use get_role_sound. Returns per-role slug, hotlinkable MP3/WAV URLs, acoustics, loopable, 2 alternates, plus a ready-to-paste role → URL map. Style sets: ui-crisp (dry, tight, bright), ui-soft (darker, gentler), ui-spacious (room reverb, longer tails), retro-game. Scenario sets: chat-app, saas-app, checkout, learning, puzzle-game, platformer, horror-game, video-editing, smart-device, wellness, ai-coding-tool (started/done/failed/needs_input/warning/notification cues for agents, CLIs and coding tools).
    ConnectorNo auth
  • Use this when the user asks which Familia households, families, or shared boards are available. Includes member names and user ids for assigning tasks or plans. Do not use for listing tasks, plans, or calendar events.
    ConnectorNo auth
  • Ordered conversion funnel across up to 5 steps within the period. Each step is a pageview path ({kind:'path', value:'/pricing'}) or a custom event ({kind:'event', value:'signup'}); a visitor counts for step N only after completing step N-1. Visitor identity rotates daily for privacy, so journeys spanning multiple days undercount (strongest for same-visit conversion). If site context has a stored funnel, run those steps when asked how the site is doing and compare against the previous period.
    ConnectorNo auth
  • List tasks with structured filters (tasklist_id, project_id, or site-wide). For keyword search use search. Completed tasks and tasks in completed tasklists are excluded unless show_completed is true, so an empty result may mean the matching work is already done rather than missing. Ask for "late", "overdue", "due today", "started" or "upcoming" work through date_filter, and leave people out through exclude_assignee_user_ids, rather than reading rows and filtering them yourself.
    ConnectorNo auth