· 1 observation
Technical updates · 1
Package or technical metadata updated
View technical comparison →Pine AI v0.1.2
Delegate real-world tasks
From the developer
Not specified in the available declarations: capabilities, limitations, pricing & account requirements.
Take customer leads, answer their questions and book them for an estimate.
Developer declarations; not independently tested. Listing last checked Nov 21, 2026. Package observed Nov 20, 2026.
From the marketplace listing
Pine Assistant helps you delegate real-world tasks to Pine AI, such as calling a business to ask about availability or following up on a request. Connect your Pine account to create a task, provide instructions and requested details, and retrieve progress, conversation history, and results. Pine continues executing tasks in the background. You can also request to end an eligible task. Task execution may use Pine credits. Account connections, verified phone binding, and payment steps are completed on Pine when required.
Language: English · Automatically detected from descriptions.
· 1 observation
Package or technical metadata updated
View technical comparison →· 2 observations
Package or technical metadata updated
View technical comparison →Finding similar plugins… Results will appear here automatically.
Browse plugins →--- name: pine description: Connect to Pine AI to delegate supported real-world tasks and check, continue, or end existing Pine tasks. See the skill instructions for the integration's currently supported scope. --- # Pine Assistant Pine AI is an assistant that carries out real-world tasks. This MCP integration currently supports starting phone tasks only. Pine can search for public business phone numbers and do the preparation needed to complete those phone tasks. This is the integration's current release scope, not a limit on Pine's overall capabilities. When a user's goal can be handled by phone, treat it as a phone task without requiring them to explicitly say “call.” If they explicitly request a new task through email, browser operation, fax, or another non-phone method, explain that this integration does not yet support starting that kind of task; do not silently change it to a phone call. For a new or continuing phone task, read [Phone tasks](references/phone-tasks.md) before composing the task instruction or interpreting call results. Existing Pine tasks can still be queried, answered, or ended using the available tools; do not reject an existing task merely because it used another execution method. Ordinary informational questions can be answered in the user's client without delegating to Pine. A clear task request is authorization: do not ask a separate “start?” question. Gather only information that is necessary to act. Use the currently discovered Pine tools by their semantic purpose; clients can namespace their names differently. The current service provides capabilities to create, list, and get sessions; send a message; read history and outcomes; submit a form response; and end a task (`pine_end_task`). It does not require a separate task-start call. ## Start or continue work 1. When the user is following up, or an existing task may match, list sessions and inspect plausible candidates. Reuse the matching session. If several are plausible, ask the user which one they mean; do not create a replacement session. 2. For a new task, create one session, then send one clear instruction with the objective, constraints, and relevant context. Session creation alone does not begin work; sending the instruction may let Pine continue it automatically. 3. Do not separately launch the same real-world task through another executor. Keep execution of the delegated task with Pine; include any useful research the client has already gathered. Do not claim an external action happened or the task is complete from a session state, timestamp, or a `received`/`delivered` message receipt. A delivered message only confirms dispatch. A `delivery_failed` receipt does not establish that nothing was saved; inspect history before sending again. A session can remain processing after Pine has replied. ## Read updates and respond Read the same session's history for questions, forms, state, task-finished content, connection or payment requests, and Agent replies. Read outcomes as well when they are relevant. Present Pine's actual reply and result facts faithfully; explain them if useful, but do not manufacture a summary, outcome, or terminal status. Fetch bounded history pages. Follow the returned cursor (`next_message_id`) through the history tool's `before` argument only while another page is needed, respect the returned `order`, and retain the latest revision of duplicate events. Do not poll in a tight loop. If the client supports native waiting, use it before another bounded query; do not promise that updates will be delivered after the client exits. A later conversation can recover by listing sessions and reading the chosen session's history/outcomes. For an ordinary Pine question, collect the user's answer in this conversation and send it to the same session. Keep sensitive form values, especially L2/L3 values, out of unnecessary narration. ## Forms and web actions When history contains a form, submit it structurally when possibl
Preview of the first 4,000 characters. Read full instructions →
Referenced files: 1 — file references are metadata, not package contents.
Publisher declarations from the archived package. These are separate from our research and the live service's terms.
Package observed Nov 20, 2026.
plugin_asdk_app_6ab15825a5088191b25e902852c74f27
Download plugin data (JSON)Plugin details: freshly prepared. Prepared . Refreshed when plugin data changes or after 6 hours. Your account and Follow status are live.