Integration
Connect Diagrams.so and TestLocally
When something happens in Diagrams.so or TestLocally, your agent does the next thing in the other. Describe it and it is built, tested on every scenario and kept running.
What the catalog holds today. Ask for anything missing and your agent reads the API documentation and adds it.
Build solutions, not workarounds.
What do you want Diagrams.so and TestLocally 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 Diagrams.so and TestLocally can do together
From Diagrams.so to TestLocally
When New diagram in Diagrams.so
then Request New Test in TestLocally
When New diagram in Diagrams.so
then Find Tests in TestLocally
From TestLocally to Diagrams.so
When New Test in TestLocally
then Update diagram in Diagrams.so
When New Test in TestLocally
then Edit diagram in Diagrams.so
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 Diagrams.so and TestLocally
Triggers and actions 2 triggers · 18 actions
Trigger
New diagramFires when a new diagram is created in the account.
Action
Delete diagramDelete a diagram.
Action
Edit diagramEdit an existing diagram with a follow-up natural-language prompt.
Action
Export diagramExport a diagram as draw.io XML or SVG.
Action
Find gallery templatesSearch public community-shared architecture diagram templates in the gallery.
Action
Fix diagram warningApply an automated fix to a flagged Well-Architected warning on a diagram.
Action
Fork gallery templateFork a public gallery template into the account's own diagrams.
Action
Get diagramRetrieve a single diagram by id.
Action
Get diagram versionRetrieve a specific saved version of a diagram.
Action
Get diagram warningsRetrieve the Well-Architected findings and score for a diagram.
Action
Import diagramImport an existing draw.io file as a new diagram.
Action
List diagramsList the diagrams in the account.
Action
List diagram versionsList the saved versions of a diagram.
Action
Relayout diagramStart an automatic re-layout job on a diagram to clean up its arrangement.
Action
Update diagramUpdate a diagram's metadata (name, visibility, tags, etc).
Trigger
New TestTriggers when a new test has been requested.
Action
Find TestsFinds recent Test Results
Action
Get Random LocationsReturns a set of 1-9 random Location names
Action
Get Test ResultsGets the Test Result details
Action
Request New TestRequest a new screenshot from a set of locations
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 Diagrams.so
Diagrams.so to PagerDutyPagerDuty is an incident management and on-call alerting platform.
Diagrams.so to DocuSealDocuSeal is an open-source platform for electronic document signing and management, offering secure, legally...
Diagrams.so to HubSpotHubSpot is your all-in-one stop for all of your marketing software needs.
Diagrams.so to SalesforceSalesforce is a leading enterprise customer relationship management (CRM) platform.
Diagrams.so to SlackSlack is a messaging platform for teams. Post messages, manage channels, users, reminders, and react to...
Diagrams.so to Google SheetsGoogle Sheets
More into TestLocally
HubSpot to TestLocallyHubSpot is your all-in-one stop for all of your marketing software needs.
Salesforce to TestLocallySalesforce is a leading enterprise customer relationship management (CRM) platform.
Slack to TestLocallySlack is a messaging platform for teams. Post messages, manage channels, users, reminders, and react to...
Google Sheets to TestLocallyGoogle Sheets
Gmail to TestLocallyGmail is Google’s email service, featuring spam protection, search functions, and seamless integration with...
Google Calendar to TestLocallyGoogle Calendar is a time management tool providing scheduling features, event reminders, and integration...
Questions
Diagrams.so and TestLocally, answered
What can start an automation from Diagrams.so?
Any of Diagrams.so's 1 trigger in the catalog, including New diagram. Describe the moment in plain language and your agent picks the right one.
What can your agent do in TestLocally when something happens in Diagrams.so?
Any of TestLocally's 4 actions, including Find Tests, Get Random Locations, Get Test Results and Request New Test. Your agent maps the data both ways and tests every scenario before it ships.
Can it also run from TestLocally to Diagrams.so?
Yes. When something happens in TestLocally, your agent can act in Diagrams.so too. This page covers both directions: TestLocally's triggers and Diagrams.so's actions are listed here as well.
Do I have to build a connector for Diagrams.so or TestLocally?
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.