Integration
Connect LightSpeed VT to Npm Registry
When Location Created fires in LightSpeed VT, your agent runs Find packages by text in Npm Registry. 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 LightSpeed VT and Npm Registry 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 LightSpeed VT can start in Npm Registry
When Location Created in LightSpeed VT
then Find packages by text in Npm Registry
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 LightSpeed VT and Npm Registry
Triggers and actions 5 triggers · 17 actions
- Access Info
Triggers when a user signs in to LightSpeed VT.
- Location Created
Triggers when a new location is added in LightSpeed VT.
- Location Updated
Triggers when a location's name, status or vendor ID changes in LightSpeed VT.
- User Created
Triggers when a new user is created in LightSpeed VT.
- User Updated
Triggers when a user's details change in LightSpeed VT.
- Deduct Leaderboard Points
Deducts points from a user's leaderboard tally.
- Find Email
Finds the user who has a given email address.
- Find User
Checks whether a username is still free to use before you create a user with it.
- Get Course
Returns a course by course ID.
- Get Leaderboard Total Points
Returns a user's leaderboard points total.
- Get Location
Returns a location by location ID.
- Get User
Returns a user by user ID.
- Get User Login URL
Returns a single sign-on URL that signs a user straight into their LightSpeed VT training.
- List Courses
Returns the courses available in your system.
- List Job Positions
Returns the job positions in your system.
- List Locations
Returns the locations in your LightSpeed VT system.
- List Teams
Returns the teams, optionally in one location.
- List User Completed Courses
Returns the courses a user has completed.
- Set User LeaderBoard Points by User ID
Adds points to a user's leaderboard tally.
- Find packages by text
Searches the public npm registry for packages matching your text and returns the matching packages with their scores, ranked by relevance.
- Get package
Returns the full registry metadata for an npm package, including its description, dist-tags, every published version, publish times, maintainers and README.
- Get package version
Returns the published metadata for one version of an npm package, including its dependencies, license, maintainers and download tarball details.
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 LightSpeed VT
LightSpeed VT to SalesforceSalesforce is a leading enterprise customer relationship management (CRM) platform.
LightSpeed VT to SlackSlack is a messaging platform for teams. Post messages, manage channels, users, reminders, and react to...
LightSpeed VT to MailchimpMailchimp marketing automation and email platform.
LightSpeed VT to StripeStripe is a payment processing platform for online businesses.
LightSpeed VT to ShopifyShopify is a commerce platform for online stores and retail point-of-sale.
LightSpeed VT to QuickBooks OnlineQuickBooks Online accounting — manage customers, invoices, bills, payments, vendors, expenses, and more via...
More into Npm Registry
HubSpot to Npm RegistryHubSpot is your all-in-one stop for all of your marketing software needs.
Google Sheets to Npm RegistryGoogle Sheets is Google's online spreadsheet app for creating, editing and sharing spreadsheets.
Gmail to Npm RegistryGmail is Google’s email service, featuring spam protection, search functions, and seamless integration with...
Google Calendar to Npm RegistryGoogle Calendar is a time management tool providing scheduling features, event reminders, and integration...
Questions
LightSpeed VT and Npm Registry, answered
What can start an automation from LightSpeed VT?
Any of LightSpeed VT's 5 triggers in the catalog, including Location Created, Location Updated, User Created and User Updated. Describe the moment in plain language and your agent picks the right one.
What can your agent do in Npm Registry when something happens in LightSpeed VT?
Any of Npm Registry's 3 actions, including Find packages by text, Get package and Get package version. Your agent maps the data both ways and tests every scenario before it ships.
Can it also run from Npm Registry to LightSpeed VT?
Npm Registry has no triggers in the catalog today, so automations start in LightSpeed VT. If you need the other direction, ask: your agent reads Npm Registry's API documentation and adds it.
Do I have to build a connector for LightSpeed VT or Npm Registry?
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 LightSpeed VT and Npm Registry 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.