Integration
Connect Anchor to Meraki
When New Proposal Sent fires in Anchor, your agent runs Add network in Meraki. Describe the whole flow 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 Anchor and Meraki 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)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 Anchor can start in Meraki
When New Proposal Sent in Anchor
then Add network in Meraki
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 Anchor and Meraki
Triggers and actions 4 triggers · 18 actions
- Agreement Amended
Triggers when an agreement is amended.
- New Proposal Sent
Triggers when a proposal is sent to a client.
- Proposal Approved
Triggers when a proposal is approved. The payload is the resulting agreement (a proposal becomes an agreement on approval).
- Proposal Published
Triggers when a proposal is published.
- Add Service to Agreement
Adds a service to a signed Anchor agreement as a new amendment.
- Create Contact
Creates a new client contact in Anchor.
- Find Contact by ID
Looks up a single contact by its Anchor ID.
- List Contacts
Returns a list of contacts (client businesses), optionally filtered by search text or status.
- Publish Proposal
Publishes a proposal draft as a proposal and, unless set to silent, emails the client.
- Submit Charges
Submits charges on an agreement to issue an invoice now or schedule one for a future billing date.
- Add network
Creates a new network in a Meraki organization and returns the created network.
- Add organization admin
Creates a new dashboard administrator in a Meraki organization with the chosen organization, tag and network access.
- Add VLAN
Adds a VLAN to a Meraki network's security appliance, with optional subnet, DHCP and IPv6 settings.
- Delete network
Deletes a Meraki network.
- Get network
Returns a Meraki network's details, including its name, organization, product types, time zone, tags and notes.
- List networks
Returns the networks you have access to in a Meraki organization, optionally filtered by tag, product type or config template.
- List organization admins
Returns the dashboard administrators in a Meraki organization, optionally limited to admins with access to specific networks.
- List organizations
Returns the Meraki organizations the connected account has privileges on.
- List SSIDs
Returns the wireless (MR) SSIDs configured in a Meraki network, with each SSID's name, number, enabled state and security settings.
- List VLANs
Returns the VLANs configured on a Meraki security appliance network.
- Update network
Updates a network's name, timezone, tags, enrollment string or notes.
- Update SSID
Updates the settings of a wireless SSID (name, authentication, encryption, VLAN, bandwidth and more) on a Meraki network and returns the updated SSID.
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 Anchor
Anchor to OutlookOutlook is Microsoft's email and calendaring platform integrating contacts and scheduling, enabling users to...
Anchor to HubSpotHubSpot is your all-in-one stop for all of your marketing software needs.
Anchor to SalesforceSalesforce is a leading enterprise customer relationship management (CRM) platform.
Anchor to SlackSlack is a messaging platform for teams. Post messages, manage channels, users, reminders, and react to...
Anchor to Google SheetsGoogle Sheets
Anchor to GmailGmail is Google’s email service, featuring spam protection, search functions, and seamless integration with...
More into Meraki
Google Calendar to MerakiGoogle Calendar is a time management tool providing scheduling features, event reminders, and integration...
Questions
Anchor and Meraki, answered
What can start an automation from Anchor?
Any of Anchor's 4 triggers in the catalog, including New Proposal Sent, Agreement Amended, Proposal Approved and Proposal Published. Describe the moment in plain language and your agent picks the right one.
What can your agent do in Meraki when something happens in Anchor?
Any of Meraki's 12 actions, including Update network, Update SSID, Add network and Add organization admin. Your agent maps the data both ways and tests every scenario before it ships.
Can it also run from Meraki to Anchor?
Meraki has no triggers in the catalog today, so automations start in Anchor. If you need the other direction, ask: your agent reads Meraki's API documentation and adds it.
Do I have to build a connector for Anchor or Meraki?
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 Anchor and Meraki 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.