Build solutions, not workarounds.
What do you want Letta and Svix to do together?
Ask the assistant
Connect your AI client
Give your AI client this address.
https://mcp.apiant.aiOne connection does both: ask your client to act in an app once, or have it build an automation that keeps running. Any 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)Grok
Open grok.com/connectors, choose New Connector, then Custom, and paste the address. Grok signs you in in your browser.
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 Letta can start in Svix
When New Agent in Letta
then Add message in Svix
When New Message in Letta
then Resend message in Svix
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 Letta and Svix
Triggers and actions 3 triggers · 32 actions
Trigger
New AgentTriggers when a new agent is created in your Letta account.
Trigger
New MessageTriggers when a new message is added to the chosen Letta agent's conversation.
Trigger
New ProjectTriggers when a new project is created in your Letta account.
Action
Add agentCreates a new Letta agent with the model, memory blocks, tools and system prompt you choose.
Action
Add archival passageAdds a passage of text to an agent's archival memory, with optional tags and timestamp.
Action
Add memory blockCreates a new memory block that can be attached to Letta agents, with a label and its contents.
Action
Create Agent From a TemplateCreates one or more Letta agents from a saved agent template and returns the new agent IDs.
Action
Create IdentityCreates an identity (a user, organization or other entity) in Letta that agents and memory blocks can be attached to.
Action
Find archival passages by querySearches an agent's archival memory by semantic similarity and returns the matching passages.
Action
Get agentReturns a Letta agent's details, including its system prompt, model and optionally its memory blocks, tools and tags.
Action
Get IdentitiesReturns the identities in your Letta project, optionally filtered by name, identifier key or type.
Action
List agentsReturns the agents in your Letta account, optionally filtered by name, tags, project, template, identity or last stop reason.
Action
List memory blocksReturns the core memory blocks attached to a Letta agent.
Action
List toolsReturns the tools available to agents in your Letta organization, optionally filtered by name, type or ID.
Action
Update agentUpdates an existing Letta agent's name, system prompt, model, tools, memory blocks, tags and other settings. Only the fields you fill in are changed.
Action
Update memory blockUpdates a memory block's value, label, character limit, description, tags or other settings.
Action
Add applicationCreates a new Svix application, the destination your webhook messages are sent to (usually one per customer).
Action
Add endpointCreates a new webhook endpoint (a destination URL) on a Svix application.
Action
Add event typeCreates a new event type in Svix, or unarchives an existing one with the same name.
Action
Add messageCreates a new message (webhook) in a Svix application and dispatches it to all of the application's subscribed endpoints.
Action
Delete applicationDeletes a Svix application and its endpoints.
Action
Delete endpointDeletes an endpoint from a Svix application so it no longer receives messages.
Action
Get applicationReturns a Svix application by its id or your own UID.
Action
Get endpointReturns a webhook endpoint of a Svix application, including its URL, subscribed event types, channels and status.
Action
Get endpoint secretReturns the signing secret of a webhook endpoint, used to verify that incoming webhooks were sent by Svix.
Action
Get messageReturns a single message (webhook) sent to an application, by its message ID or event ID, including its payload.
Action
List applicationsReturns the applications in your Svix organization, optionally excluding those without active endpoints.
Action
List endpointsReturns the endpoints (webhook destination URLs) configured on a Svix application.
Action
List event typesReturns the event types defined in your Svix environment.
Action
List message attemptsReturns the delivery attempts made for a message, with each attempt's endpoint, URL, status and response.
Action
List messagesReturns the messages (webhooks) sent to a Svix application, optionally filtered by channel, tag, event type or date range.
Action
Resend messageResends an existing webhook message to one of the application's endpoints.
Action
Rotate endpoint secretRotates an endpoint's webhook signing secret. The previous secret stays valid for a grace period (24 hours by default).
Action
Update applicationUpdates an existing Svix application's name, UID, throttle rate or metadata. Only the values you fill in are changed.
Action
Update endpointUpdates selected settings of a webhook endpoint in a Svix application, such as its URL, description, subscribed event types or channels. Fields left blank are unchanged.
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 Letta
Letta to SalesforceSalesforce is a leading enterprise customer relationship management (CRM) platform.
Letta to SlackSlack is a messaging platform for teams. Post messages, manage channels, users, reminders, and react to...
Letta to MailchimpMailchimp marketing automation and email platform.
Letta to StripeStripe is a payment processing platform for online businesses.
Letta to ShopifyShopify is a commerce platform for online stores and retail point-of-sale.
Letta to QuickBooks OnlineQuickBooks Online accounting — manage customers, invoices, bills, payments, vendors, expenses, and more via...
More into Svix
HubSpot to SvixHubSpot is your all-in-one stop for all of your marketing software needs.
Salesforce to SvixSalesforce is a leading enterprise customer relationship management (CRM) platform.
Slack to SvixSlack is a messaging platform for teams. Post messages, manage channels, users, reminders, and react to...
Google Sheets to SvixGoogle Sheets is Google's online spreadsheet app for creating, editing and sharing spreadsheets.
Gmail to SvixGmail is Google’s email service, featuring spam protection, search functions, and seamless integration with...
Google Calendar to SvixGoogle Calendar is a time management tool providing scheduling features, event reminders, and integration...
Questions
Letta and Svix, answered
What can start an automation from Letta?
Any of Letta's 3 triggers in the catalog, including New Agent, New Message and New Project. Describe the moment in plain language and your agent picks the right one.
What can your agent do in Svix when something happens in Letta?
Any of Svix's 19 actions, including Update application, Update endpoint, Add application and Add endpoint. Your agent maps the data both ways and tests every scenario before it ships.
Can it also run from Svix to Letta?
Svix has no triggers in the catalog today, so automations start in Letta. If you need the other direction, ask: your agent reads Svix's API documentation and adds it.
Do I have to build a connector for Letta or Svix?
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.
Can my AI client use Letta and Svix without building an automation?
Yes. With your AI client connected to APIANT, ask it to do something in either app once and it runs that action on the spot. Ask for an automation and your agent builds it, tests every scenario and keeps it running. One connection covers both.
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.