Cloud/Create Connector/Connector Deploy
Connector Deploy
The first path in Create Connector: build your connector as code with the Connector Framework and ship it to the hardened edge with one command. No Dockerfile, no CI pipeline, just mcp-server deploy.
Connector Deploy is the first path inside Create Connector, and it is the one for builders. The console describes it in one line: "The AI-first Connector. Deploy once and connect your app to any AI agent." You write your connector as code with the Connector Framework, Vinkius ships it to hardened edge infrastructure, and AI agents discover and connect to your app instantly, worldwide. The two tags the console puts on this card are the promise: Edge Hardened and Connector Framework.
Deploy Connector
Name it here, deploy it from your terminal.
The mockup is the real wizard. Type a name, hit Deploy to Edge and watch the phases run, then read the three terminal commands your project needs and copy them. Deploy Another starts a fresh run.
Name it here, deploy it from your terminal
The wizard for this path asks exactly one thing in the browser: a Server Name. That is the whole form, because your code is the connector. The console's own subtitle says the division of labor: "Name it here, deploy it from your terminal." Everything else happens from your project, with the Connector Framework doing the heavy lifting.
Your edge server is ready
The moment the deploy lands, the screen flips to the success state with a pulsing fuchsia badge: Edge · High Secure · Ready. What follows is a three step recipe, each with a command you can copy:
- Configure the target. Point your project at this server with
npx mcp-server remote --server-id {id}. This is the one time your server id matters. - Set the deploy token. Save the connection token to your project with
npx mcp-server token {token}. The console warns in amber: "Save this token now. It won't be shown again." The plaintext is never stored, authentication is HMAC-SHA256. - Deploy to edge. Ship your bundled code with
npx mcp-server deploy. This is the command you will type every day, and the only one the education panel keeps on screen: "No Dockerfile. No CI pipeline. Just mcp-server deploy."
After initial setup, every subsequent deploy is just that last command. The wizard also hands you the framework links: the Connector Framework on GitHub and the Deploy & CLI guide in the docs.
What deploys, exactly
Behind the button, the console walks four phases before your connector is live: provisioning the edge target, generating deploy credentials, preparing the V8 Isolate sandbox, and then your server is ready for deployment. That sandbox is the security story: your code runs isolated on Vinkius infrastructure, the same Edge Hardened runtime every connector gets, with Zero-Trust DLP and cost controls available from the governance switches.
What you get when it is live
A deployed connector is a first-class citizen of your Library: it shows up with its own Connector detail page, where Dashboard, Credentials, Connection Tokens, AI Capabilities and Playground all work the same way they do for catalog connectors. Deploy Another resets the wizard to a clean state, and View Servers takes you back to your connectors.
The free-plan gate
On the free plan this path is locked like the others: the wizard hands you an upgrade pitch instead of a name field, and the deal is the same, unlimited connectors, Zero-Trust DLP, the ability to monetize your tools, and the global edge runtime. Upgrade and the wizard unlocks.
Why this path exists
Some things are not an API you can point at. They are logic: routing, transforms, presenters, anti-hallucination guards. Connector Deploy is how that logic becomes an AI Capability that any agent can call, deployed to the edge in one command, governed like everything else you run on Vinkius.
What comes next
The other Create Connector paths each have their own guide, one at a time: Agent Skills (teach agents knowledge with the SKILL.md standard), OpenAPI / Swagger (paste one spec URL, every endpoint becomes a tool), and Manual Setup (no spec? add endpoints by hand, step by step).