Arez

authoring-mcp-servers

Use when creating or extending a headless Noodle Seed MCP server, tool, resource, prompt, or typed model-facing capability.

building-mcp-apps

Use when a Noodle Seed MCP App, widget, interactive card, visual interaction, or host-visible UI is the primary requested outcome.

connecting-apis-to-mcp

Use when all four API-evidence inputs exist—and only then: API base URL, authentication scheme, representative safe read, and observed response.

debugging-mcp-delivery

Use when an existing Noodle Seed MCP project has a concrete validation, runtime, connector, App, host, deployment, or production failure.

deploying-mcp-services

Use when the user explicitly requests a Noodle Seed hosted link, configuration write, deployment, access change, rollback, or connection write.

designing-mcp-products

Use when a Noodle Seed MCP product idea needs conversational fit, user benefit, scope, interaction, or evidence design before implementation.

embedding-mcp-assistants

Use when embedding a Noodle assistant into an existing SaaS or web application with browser, identity, session, and credential boundaries.

executing-noodle-plans

Use when the user asks to execute an approved, decision-complete implementation plan for a Noodle Seed project task by task with test-first changes, review, recovery, and final verification.

publishing-mcp-integrations

Use when preparing, reviewing, or submitting a Noodle Seed MCP integration to a host or app directory.

reporting-noodle-feedback

Use when a Noodle Seed bug, misleading instruction, missing capability, or concrete product improvement should be proposed to the user.

verifying-mcp-delivery

Use when proving a Noodle Seed MCP project works at a named compile, local, connector, App, host, deployment, or production evidence level.

wrapping-existing-applications

Use when an existing application has no stable usable API and needs a read-only, identity-first Noodle Seed integration plan before implementation.