
SkuVault Connector
You're all set. Choose your MCP client and follow the setup instructions.
https://edge.vinkius.com/vk_preview_GuaDd3WAt4jPQ6jCAoKTKpvkHPeRH9Je9Uqp9S4q/mcpConnecting SkuVault to the Vercel AI SDK
About a minute, in your code
- 1Install the MCP client: npm install @ai-sdk/mcp, and import createMCPClient from '@ai-sdk/mcp'.
- 2Create the client with your SkuVault link as the transport: { type: 'http', url: '<your link>' }. The link above is the URL.
- 3Call client.tools() and pass the tools to streamText. SkuVault is now part of your AI SDK app.
{
"mcpServers": {
"skuvault-mcp": {
"url": "https://edge.vinkius.com/vk_preview_GuaDd3WAt4jPQ6jCAoKTKpvkHPeRH9Je9Uqp9S4q/mcp"
}
}
}Vercel AI SDK + SkuVault
One chat. Your SkuVault, live inside Vercel AI SDK.
Real prompts, answered with live data. This is the kind of interaction your app will have once the client is in.
Waiting for input…
Works with modern AI clients that support MCP, including ChatGPT, Claude, Cursor, and more.
These prompts ship with the SkuVault Connector. Once yours is connected, they work in your sessions.
The full capability set, the prompts and the observed latency live on the SkuVault Connector page.
Mission Control
See everything your Vercel AI SDK agents do in SkuVault.
When your app runs a tool in SkuVault, it happens inside your code: you see the output, but not the request itself, what data it carried, or whether a rule was broken.
Now every move lands on your screen.
Every execution is recorded, enforced, and shown to you: what ran, what it returned, what was blocked, and why.
Know exactly what needs your attention before you even look at the charts. One briefing. The full picture. The next move.
AI Agents Activities
last 30 daysRequest Volume & Latency
requests latencyEvery request your Vercel AI SDK agents make through SkuVault is logged, enforced and auditable. See how AI Governance turns agent activity into accountability, and what it means for your SkuVault workflows.
What sets us apart
It's not just the Connector that stays safe. Everything your agents do through it is.
Connecting SkuVault to your AI is step one. But an open line between your agents and SkuVault is only half the story: without protection, every action they take runs unguarded.
That's why protection doesn't stop at the door.
Every action your agents take through the Connector runs inside our infrastructure: signed activity logs, automatic key rotation, spending limits that pause instead of surprise, and a sandbox that isolates every execution.
Tamper Proof Activity Log
Every request your agents make in SkuVault is recorded and signed, so any change to the history becomes detectable.
Automatic Key Rotation
We rotate security keys every 24 hours. Your SkuVault connection stays protected without any manual work.
Spending Protection
We enforce the spending limit you choose and pause actions that exceed it until approval is received. Your SkuVault actions never surprise you.
Isolated Sandbox
Every execution through SkuVault runs isolated, with 34+ security rules covering memory, CPU, network access, file handling and execution.
Security Event Streaming
Security events flow to Splunk, Datadog or your own webhook, so SkuVault activity lands in the tools you already rely on.
Instant Resume
Idle connections resume in 3 to 5 ms while preserving their state, keeping your Vercel AI SDK sessions responsive.
Malicious File Protection
We detect compressed files designed to exhaust system resources and block them before they ever reach SkuVault.
Credential Validation
We test your SkuVault credentials before saving them. Invalid credentials are rejected instead of being stored.
Separate Usage Limits
Usage stays isolated per account, so activity in one connection never consumes another account's allowance.
One Connector, one link, and the whole operation is protected. Not just the connection: everything your agents do through it.
These guarantees are not add-ons: they are the infrastructure every SkuVault connection runs on. Read how our infrastructure protects everything your Vercel AI SDK agents do, end to end.
Inside Vinkius
Get SkuVault ready for your AI. It's easy.
You choose SkuVault from the Vinkius Catalog, sign in to your SkuVault account, and get one connection link. That's it.
You choose SkuVault
You find SkuVault in the Catalog and install the Connector with one click.
SkuVault
Active
Enable ConnectorActivating…You sign in
You connect your SkuVault account and choose what you want your AI to access. Your credentials stay encrypted and separate from your AI.
Configure Credentials
Configure credentials for {{connectorName}}
RequiredEncryptedSave & ContinueYou add the link in your code
Vinkius gives you one connection link. In your app, you create an MCP client with the link as the HTTP transport URL, and the tools are ready.
Token generated successfully
MCP Connection URL
https://edge.vinkius.com/vk_preview_GuaDd3WAt4jPQ6jCAoKTKpvkHPeRH9Je9Uqp9S4q/mcpGo to DashboardConnection Token
vk_live_••••••••
Set it up once. Use SkuVault with the AI you already use.
FAQ
Vercel AI SDK access questions.
- 01
Which package does this use?
@ai-sdk/mcp, with the createMCPClient function. HTTP and SSE transports are supported, with optional headers and OAuth via an authProvider.
- 02
If I connect SkuVault to my app, can I use the same connection in Claude or ChatGPT later?
Yes, and that's the point: the connection is yours, not the app's. You paste the same link in any AI you use, and there's nothing new to set up or pay again. Connect a new AI and SkuVault is already there.
- 03
Do I need to hand my SkuVault password to my app?
Never. You sign in once at Vinkius, and we keep your logins encrypted and away from your AI. Your code only ever sees the link, and you can remove it whenever you want.
- 04
What can my app actually do with SkuVault?
Whatever the Connector covers: check data, run actions and bring answers back. Pass the tools to streamText and the model picks the right one. The Connector page lists every capability, with real examples you can copy.
- 05
The tools don't show up. What do I check?
Confirm the url matches your link exactly and that the Connector is active in your Vinkius account, then call tools() again. A deactivated Connector stops responding.
- 06
Can I remove the access later?
Anytime. Close the client and remove the tools from your call, and SkuVault leaves your app. Your Vinkius account keeps the connection and its history either way, ready for the next AI.
More questions about SkuVault? The Connector page answers them. See everything the SkuVault Connector can do
About the Connector
What SkuVault adds to your AI.
Once you connect it, your AI gains 20 capabilities: the exact actions it can take in SkuVault when you ask. The Connector page lists every one of them in detail, alongside the latency we measure in production and prompts worth trying first.
See everything the SkuVault Connector can do