Build solutions, not workarounds.
What do you want Wachete and Mem0 to do together?
Ask the assistant
Connect your AI client
Give your AI client this address.
https://mcp.apiant.aiAny client that takes a remote MCP server. Nothing to install. Create your free account, then sign in once in your browser.
Set it up in your client
Claude Code
Run this in the directory you want to work in.
claude mcp add --transport http -s project apiant-ai https://mcp.apiant.aiStart Claude Code there, approve the server, and sign in in the browser page it opens.
Claude Code guide (opens in a new tab)Claude, web and desktop
Open Customize, then Connectors, then Add custom connector, and paste the address. On Team and Enterprise an owner adds it first.
Setup guide (opens in a new tab)Cursor
Add the address to your MCP configuration as a server URL. Cursor signs you in in your browser.
Setup guide (opens in a new tab)Zed
Open Settings, then AI, then MCP Servers, then Add Server, then Add Remote Server.
Setup guide (opens in a new tab)Codex and the ChatGPT desktop app
Open Settings, then MCP servers, then Add server, and choose Streamable HTTP. From the terminal, Codex takes the address with its own add command and then signs you in.
Setup guide (opens in a new tab)Any other MCP client
Paste the address where the client asks for a remote MCP server URL, and name the server apiant-ai where it lets you. APIANT's skills reach the client over the same connection.
Setup guide (opens in a new tab)Example flows
What Wachete can start in Mem0
When New notification for monitor in Wachete
then Update Memory in Mem0
When Any new notification in Wachete
then Find Memories by query in Mem0
Starting points drawn from the triggers and actions in the catalog today. Describe the flow you need, at any depth, and your agent builds it and tests every scenario before it ships.
Everything your agent can do with Wachete and Mem0
Triggers and actions 2 triggers · 14 actions
Trigger
Any new notificationFires when there is a new change notification from any monitor in your Wachete account.
Trigger
New notification for monitorFires when there is a new change notification from the specified Wachete monitor (taskId).
Action
Create monitorCreate a new Wachete monitor (wachet) that watches a web page or part of a page for changes.
Action
Delete monitorDelete a Wachete monitor by its ID.
Action
Get monitorGet information about a specific Wachete monitor by its ID.
Action
Get monitor dataGet the captured data/history for a Wachete monitor, optionally as a diff and within a date range.
Action
List foldersList folder contents, optionally under a parent folder.
Action
List notificationsList change notifications, optionally filtered by monitor (taskId) and date range.
Action
Update monitorChange the settings of an existing Wachete monitor — name, URL, watched/excluded XPath, regex, note, job type, check frequency and location, crawl options, folder, alerts, notification endpoints, headers and proxies. A partial update: the op first reads the monitor's current record, overlays only the fields you filled in, then writes the merged record back, so anything you leave blank keeps its current value — including settings this op does not expose. Identify the monitor by its id. Check frequency is in seconds (86400 = daily) and is ignored if not positive; the true/false options take the words true or false; alerts, notification endpoints, headers and proxies take JSON. Returns the monitor id, name and URL after the update plus the full monitor record.
Action
Delete MemoryDeletes a single memory by its ID, optionally also deleting memories linked to it.
Action
Delete UserDeletes a Mem0 user and its memories. Deletion is queued and completes in the background.
Action
Find Memories by queryReturns up to top_k memories ranked by relevance to a natural-language query, scoped to a user, agent, app or run.
Action
Get MemoryRetrieve a single Mem0 memory by its ID.
Action
List MemoriesLists memories matching the given filters (at least one user, agent, app or run id). Returns the first page of up to 100 memories plus the total count.
Action
List UsersLists the users (user entities) in your Mem0 organization/project.
Action
Update MemoryUpdate an existing Mem0 memory's text, metadata, or expiration date.
No trigger or action matches that. Ask your agent to add it: it reads the API documentation and builds what you describe.
Each app on its own
Reviews
What our customers say
More from Wachete
Wachete to SalesforceSalesforce is a leading enterprise customer relationship management (CRM) platform.
Wachete to ActiveCampaignActiveCampaign is a marketing automation, email marketing, and CRM platform.
Wachete to JIRAAtlassian JIRA Cloud — issue tracking and project management.
Wachete to ZoomZoom unifies cloud video conferencing, simple online meetings, group messaging, and a software-based...
Wachete to WebflowWebflow is a professional website builder and CMS for designing, building, and launching responsive...
Wachete to AnthropicAnthropic builds Claude, a family of large language models.
More into Mem0
HubSpot to Mem0HubSpot is your all-in-one stop for all of your marketing software needs.
Salesforce to Mem0Salesforce is a leading enterprise customer relationship management (CRM) platform.
Slack to Mem0Slack is a messaging platform for teams. Post messages, manage channels, users, reminders, and react to...
Google Sheets to Mem0Google Sheets
Gmail to Mem0Gmail is Google’s email service, featuring spam protection, search functions, and seamless integration with...
Google Calendar to Mem0Google Calendar is a time management tool providing scheduling features, event reminders, and integration...
Questions
Wachete and Mem0, answered
What can start an automation from Wachete?
Any of Wachete's 2 triggers in the catalog, including New notification for monitor and Any new notification. Describe the moment in plain language and your agent picks the right one.
What can your agent do in Mem0 when something happens in Wachete?
Any of Mem0's 7 actions, including Update Memory, Find Memories by query, Get Memory and List Memories. Your agent maps the data both ways and tests every scenario before it ships.
Can it also run from Mem0 to Wachete?
Mem0 has no triggers in the catalog today, so automations start in Wachete. If you need the other direction, ask: your agent reads Mem0's API documentation and adds it.
Do I have to build a connector for Wachete or Mem0?
No. Both are in the catalog with their triggers and actions. You describe the automation; your agent builds it, tests every scenario and keeps it running.
What happens when something fails?
Your agent works that out for you. It plans the failure paths along with the happy path, then tests every scenario before it ships.
Is there a free plan?
Yes. Every plan includes the agent, including free, and building from your own AI client spends no assistant credits.