Alpic Connector for AI agents.

18 live capabilities

Manage your Connector deployments and infrastructure with automated agent commands.

Live agent request Alpic / Connector

Waiting for input…

AI Agent

Why people use Alpic

Alpic for Automated Infrastructure Management

With Alpic, you just tell your agent what needs to happen. It updates the variables, triggers the deployment, and monitors the logs for you. You move from being a manual operator to an infrastructure conductor, getting a success message instead of a headache.

What Vinkius changes

You replace manual dashboard clicks with direct, agent-led infrastructure commands.

Use it from Claude, ChatGPT, Cursor or another AI client you already have.

One account · 5,900+ Connectors

Real-world use case 01

The Broken Production Fix

An engineer sees a spike in errors.
Real-world use case 02

New Project Onboarding

A dev needs a new environment.
Real-world use case 03

The Security Audit

A security officer wants to see what's live.

Complete set · 18capabilities

The complete Alpic capability set.

These are the exact actions your AI can choose when you ask it to work with Alpic.

Capability set01 / 05

01—04

4 capabilities in this set.

Part of 18 available through Alpic.

01 Capability
Update project
Use `update_project` to rename projects or point to new repository branches. You only need to pass the specific fields you want to change.
02 Capability
Create project
Use `create_project` to start a new MCP project in Alpic. You can link it to a git repository and set initial configurations immediately.
03 Capability
Delete project
Use `delete_project` to permanently remove an Connector project from your account. This action is final and requires a confirmation step.
04 Capability
Delete variable
Use `delete_variable` to clean up old or unused configuration keys. This helps keep your environment variables organized and secure.

Capability set02 / 05

05—08

4 capabilities in this set.

Part of 18 available through Alpic.

05 Capability
Deploy environment
Use `deploy_environment` to push new versions of your Connector to a specific target. It returns a deployment ID so you can track the progress.
06 Capability
Get deployment logs
Use `get_deployment_logs` to see the build output or startup errors for an environment. It's the fastest way to debug a failed deployment.
07 Capability
Get deployment
Use `get_deployment` to check the status of a specific deployment. You can review the history and metadata of any past push.
08 Capability
Get project analytics
Use `get_project_analytics` to monitor request counts and latency trends. It helps you identify performance issues in your Connector infrastructure.

Capability set03 / 05

09—12

4 capabilities in this set.

Part of 18 available through Alpic.

09 Capability
Get project
Use `get_project` to review the settings and repo links for a specific project. It helps you verify your configuration before making updates.
10 Capability
Get server info
Use `get_server_info` to verify which capabilities are exposed and check if your Connector is running correctly. It provides a quick status check.
11 Capability
List environments
Use `list_environments` to see all dev, staging, and production targets for a project. It shows the current status and unique URLs for each.
12 Capability
List projects
Use `list_projects` to get an overview of all Connector projects in your account. You can see team associations and deployment statuses at a glance.

Capability set04 / 05

13—15

3 capabilities in this set.

Part of 18 available through Alpic.

13 Capability
List teams
Use `list_teams` to see all teams associated with your account. This helps you identify which group a project belongs to.
14 Capability
List variables
Use `list_variables` to audit the configuration keys for an environment. It returns metadata and masked values to keep your secrets safe.
15 Capability
Publish to registry
Use `publish_to_registry` to make your Connector publicly available. It handles the submission to the official registry for you.

Capability set05 / 05

16—18

3 capabilities in this set.

Part of 18 available through Alpic.

16 Capability
Add variable
Use `add_variable` to set API keys, database URLs, or feature flags for your Connector. It stores these values securely for your specific project and environment.
17 Capability
Create environment
Use `create_environment` to build a new dev, staging, or production space. It gives each environment a unique URL for your Connector client connections.
18 Capability
Get tunnel ticket
Use `get_tunnel_ticket` to get a URL and token for local testing. This lets you preview your Connector before you push it to a live environment.

Set up in minutes

One URL. Then ask Alpic to work.

Claude and ChatGPT only need the Connector URL. Copy it once, add it in settings, and use Alpic from the conversation.

Choose your client

Live preview

Advanced clients IDE · CLI

Claude · Web + desktop

Official guide ↗

Connector URL · ready to paste

Streamable HTTP

https://edge.vinkius.com/vk_preview_2KgnFzVSaiaSHBNFbROaJ4IhOHTa3rucrY1KgZYb/mcp

Step 01

Open Connectors

In Claude Web or Claude Desktop, open Settings and choose Connectors.
Step 02

Add the URL

Choose Add custom connector, name it Alpic, and paste the URL above.
Step 03

Turn it on in chat

Select +, open Connectors, and enable Alpic for the conversation.

ChatGPT · Web + desktop

Official guide ↗

Connector URL · ready to paste

Streamable HTTP

https://edge.vinkius.com/vk_preview_2KgnFzVSaiaSHBNFbROaJ4IhOHTa3rucrY1KgZYb/mcp

Step 01

Open MCP settings

On desktop, open Settings and MCP servers. On web, open your workspace app or connector settings.
Step 02

Add the URL

Choose Add server with Streamable HTTP, or create a custom MCP app, then paste the Alpic URL.
Step 03

Save and start

Save the connection and enable Alpic in your conversation. Desktop may ask you to restart once.

Cursor · IDE configuration

Official guide ↗

Advanced setup

{
  "mcpServers": {
    "alpic": {
      "url": "https://edge.vinkius.com/vk_preview_2KgnFzVSaiaSHBNFbROaJ4IhOHTa3rucrY1KgZYb/mcp"
    }
  }
}

Step 01

Open MCP Settings

Press Cmd+Shift+P (macOS) or Ctrl+Shift+P (Windows/Linux) → search "MCP Settings"
Step 02

Add the server config

Paste the JSON configuration above into the mcp.json file that opens
Step 03

Save the file

Cursor will automatically detect the new Connector
Step 04

Start using Alpic

Open Agent mode in chat and ask: "Using Alpic, help me...". 18 tools available

VS Code Copilot · IDE configuration

Official guide ↗

Advanced setup

{
  "mcpServers": {
    "alpic": {
      "url": "https://edge.vinkius.com/vk_preview_2KgnFzVSaiaSHBNFbROaJ4IhOHTa3rucrY1KgZYb/mcp"
    }
  }
}

Step 01

Create MCP config

Create a .vscode/mcp.json file in your project root
Step 02

Add the server config

Paste the JSON configuration above
Step 03

Enable Agent mode

Open GitHub Copilot Chat and switch to Agent mode using the dropdown
Step 04

Start using Alpic

Ask Copilot: "Using Alpic, help me...". 18 tools available

Windsurf · IDE configuration

Official guide ↗

Advanced setup

{
  "mcpServers": {
    "alpic": {
      "url": "https://edge.vinkius.com/vk_preview_2KgnFzVSaiaSHBNFbROaJ4IhOHTa3rucrY1KgZYb/mcp"
    }
  }
}

Step 01

Open MCP Settings

Go to Settings → MCP Configuration or press Cmd+Shift+P and search "MCP"
Step 02

Add the server

Paste the JSON configuration above into mcp_config.json
Step 03

Save and reload

Windsurf will detect the new server automatically
Step 04

Start using Alpic

Open Cascade and ask: "Using Alpic, help me...". 18 tools available

Cline · IDE configuration

Official guide ↗

Advanced setup

{
  "mcpServers": {
    "alpic": {
      "url": "https://edge.vinkius.com/vk_preview_2KgnFzVSaiaSHBNFbROaJ4IhOHTa3rucrY1KgZYb/mcp"
    }
  }
}

Step 01

Open Cline MCP Settings

Click the Connectors icon in the Cline sidebar panel
Step 02

Add remote server

Click "Add Connector" and paste the configuration above
Step 03

Enable the server

Toggle the server switch to ON
Step 04

Start using Alpic

Ask Cline: "Using Alpic, help me...". 18 tools available

Claude Code · Terminal command

Official guide ↗

Advanced setup

claude mcp add alpic --transport http "https://edge.vinkius.com/vk_preview_2KgnFzVSaiaSHBNFbROaJ4IhOHTa3rucrY1KgZYb/mcp"

Step 01

Install Claude Code

Run npm install -g @anthropic-ai/claude-code if not already installed
Step 02

Add the Connector

Run the command above in your terminal
Step 03

Verify the connection

Run claude mcp to list connected servers, or type /mcp inside a session
Step 04

Start using Alpic

Ask Claude: "Using Alpic, show me...". 18 tools are ready

Where the request belongs

Work Alpic can move forward.

Built around the request

This is for the DevOps engineer who's tired of manual deployments and the platform team managing dozens of Connectors across different environments. It's for anyone who needs to automate the plumbing of AI infrastructure.

01

DevOps Engineer

Automates deployments and monitors logs for 5+ environments to ensure 99.9% uptime.

02

Platform Engineer

Manages team access and project permissions across the entire organization's MCP portfolio.

03

AI Infrastructure Manager

Oversees the lifecycle and registry status of all company Connectors to keep them discoverable.

Build the capability set

Each Connector adds new actions and data without changing how you work.

Browse Connectors

01 27 capabilities

Runlayer

AI enterprise control plane: manage MCP servers, skills, agents, and security policies via agents.

02 11 capabilities

Smithery

AI MCP registry: discover, search, and connect MCP servers to your agents via Smithery.

03 8 capabilities

MintMCP

Enterprise MCP Gateway: manage authentication, monitoring, and security guardrails via centralized virtual servers.

04 10 capabilities

Vinkius AI Catalog

Give your AI agent full access to the Vinkius MCP catalog. Search, browse, and discover MCPs. their capabilities, debugger grades, FAQs, and documentation. all programmatically.

05 8 capabilities

PAN-OS

Connect PAN-OS to any AI agent via MCP.

06 8 capabilities

Metorial

Enterprise observability and serverless scaling infrastructure directly mapping MCP agents logic.

Bring your own AI

Change the model, client or framework. Keep Alpic connected.

Before you connect

Questions about Alpic.

The practical details behind the request, access and result.

Can Alpic manage multiple environments for my Connectors?

Yes, it lets you create and manage dev, staging, and production environments separately. This ensures your configurations stay isolated and your production environment remains stable.

How do I see my Connector logs when something goes wrong?

You can ask your agent to pull logs for any specific environment. It will fetch the real-time build output and runtime data so you can debug issues quickly.

Is it safe to store my API keys in Alpic?

Yes, Alpic stores your environment variables securely. When you list them, the values are masked to ensure your secrets are never exposed in plain text.

Can I use Alpic to manage my team's access?

Yes, Alpic includes team management and access controls. You can organize your projects under different teams and manage who has permission to see or edit them.

How do I test my Connector locally before deploying?

You can use the tunnel ticket capability. It provides a URL for local testing, allowing you to verify everything works perfectly before you push your code to a live environment.

Can Alpic help me put my Connector on a public registry?

Yes, the platform includes a capability to publish your Connector to the official registry. This makes your capabilities discoverable to other users in the ecosystem.

Can I deploy environments from specific Git branches directly from the terminal?

Yes! You can operate create_environment mapping parameters matching your active branches, then instruct your agent to trigger the deploy_environment sync.

Are environment variables secured during deployment processes?

Absolutely. You can invoke add_variable providing exact tokens without storing them in repositories. They remain encrypted at rest and dynamically injected upon startup.

Can I test server configuration before final production merges?

Yes. Request your AI agent to trigger get_tunnel_ticket enabling you to natively tunnel local host environments through Alpic before pushing any true integration commits.

One connection away

Give your agent a direct line to Alpic.

Connect Alpic once. Keep it beside 5,900+ managed Connectors when the next task needs more.

Explore every Connector No credit card required · Free tier available