Cockpit CMS Connector
You're all set. Choose your MCP client and follow the setup instructions.
https://edge.vinkius.com/vk_preview_fNofB8llpPLT1euBpo7Rm0YeaMUb0DsJJHBkdNZ7/mcp
Connecting Cockpit CMS 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 Cockpit CMS link as the transport: { type: 'http', url: '<your link>' }. The link above is the URL.
- 3Call client.tools() and pass the tools to streamText. Cockpit CMS is now part of your AI SDK app.
{
"mcpServers": {
"cockpit-self-hosted-headless-cms-api-mcp": {
"url": "https://edge.vinkius.com/vk_preview_fNofB8llpPLT1euBpo7Rm0YeaMUb0DsJJHBkdNZ7/mcp"
}
}
}Vercel AI SDK + Cockpit CMS
One chat. Your Cockpit CMS, 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 Cockpit CMS Connector. Once yours is connected, they work in your sessions.
The full capability set, the prompts and the observed latency live on the Cockpit CMS Connector page.
Mission Control
See everything your Vercel AI SDK agents do in Cockpit CMS.
When your app runs a tool in Cockpit CMS, 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 Cockpit CMS is logged, enforced and auditable. See how AI Governance turns agent activity into accountability, and what it means for your Cockpit CMS workflows.
What sets us apart
It's not just the Connector that stays safe. Everything your agents do through it is.
Connecting Cockpit CMS to your AI is step one. But an open line between your agents and Cockpit CMS 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 Cockpit CMS is recorded and signed, so any change to the history becomes detectable.
Automatic Key Rotation
We rotate security keys every 24 hours. Your Cockpit CMS 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 Cockpit CMS actions never surprise you.
Isolated Sandbox
Every execution through Cockpit CMS 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 Cockpit CMS 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 Cockpit CMS.
Credential Validation
We test your Cockpit CMS 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 Cockpit CMS connection runs on. Read how our infrastructure protects everything your Vercel AI SDK agents do, end to end.
Inside Vinkius
Get Cockpit CMS ready for your AI. It's easy.
You choose Cockpit CMS from the Vinkius Catalog, sign in to your Cockpit CMS account, and get one connection link. That's it.
You choose Cockpit CMS
You find Cockpit CMS in the Catalog and install the Connector with one click.
Cockpit CMS
Active
Enable ConnectorActivating…You sign in
You connect your Cockpit CMS 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_fNofB8llpPLT1euBpo7Rm0YeaMUb0DsJJHBkdNZ7/mcpGo to DashboardConnection Token
vk_live_••••••••
Set it up once. Use Cockpit CMS 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 Cockpit CMS 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 Cockpit CMS is already there.
- 03
Do I need to hand my Cockpit CMS 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 Cockpit CMS?
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 Cockpit CMS leaves your app. Your Vinkius account keeps the connection and its history either way, ready for the next AI.
More questions about Cockpit CMS? The Connector page answers them. See everything the Cockpit CMS Connector can do
About the Connector
What Cockpit CMS adds to your AI.
Once you connect it, your AI gains 17 capabilities: the exact actions it can take in Cockpit CMS 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 Cockpit CMS Connector can do