wapp.

wapp

Create an on-demand WhatsApp assistant from an MCP client. Give it instructions, optionally attach remote MCP servers, and share the returned pairing code or WhatsApp link. A person sends the code to the service number to start chatting.

Operations

• create_agent: create an assistant template and expiring pairing code.
• list_agents: list active templates, optionally including inactive codes.
• get_agent_activity: inspect paired chats, messages, tool activity, and errors.
• update_agent: change instructions, servers, welcome text, model, chat limit, or expiry.
• revoke_agent: close a code; paired chats stop on their next message.

Legacy operator codes last 24 hours by default. Creation supports up to 90 days, up to 10 remote MCP servers, and an optional positive chat limit (1 makes a code single-use). Users can send stop to disconnect, reset to clear conversation memory, or a new code to switch assistants. Expired and revoked codes stop their paired chats.

Access and data

MCP management supports Jetski Auth with email verification and password signup. Every caller can only manage their own agents. Jetski trials allow 50 agents per UTC day, 30-day lifetimes, 100 connected chats and 10,000 AI turns per agent, with a fixed model, external MCP connections and messaging paired chats. WhatsApp users pair using a code.

Create a WhatsApp assistant named Workshop helper. Have it ask one short question at a time to help clarify workshop ideas. Make the code last one hour, allow one chat, and return the WhatsApp pairing link.