# Alpic MCP for AI Agents AI Agent Connect > Alpic is an infrastructure platform for managing the entire lifecycle of your Connectors. It lets your AI agents handle the heavy lifting of deploying to multiple environments, managing environment variables, and monitoring real-time logs. Instead of jumping between dashboards, you can use natural language to push updates, check health metrics, and manage team access in one place. ## Overview - **Category:** friends-mcp - **Price:** Free - **Endpoint:** https://edge.vinkius.com/vk_preview_2KgnFzVSaiaSHBNFbROaJ4IhOHTa3rucrY1KgZYb/ai-agent-connect - **Tags:** mcp-server, deployment, lifecycle-management, infrastructure-as-code, monitoring, automation ## Description Managing your Connectors shouldn't feel like a chore of constant context switching. Usually, you're juggling different terminal windows, manual configuration files, and a bunch of tabs just to keep your production environment stable. Alpic changes that by giving your AI agent a direct line to your infrastructure. You can tell your agent to spin up a new staging environment, swap out API keys, or grab the latest logs from a failed deployment without ever opening a dashboard. It handles the messy details of multi-environment scaling and secure variable management so you can focus on actually building stuff. By connecting Alpic to your workflow through the Vinkius marketplace, you turn infrastructure management into a conversation. You get a centralized way to manage teams, link git repos, and publish to the registry, all while keeping your dev tunnels and production logs organized. It's about moving from manual clicking to automated, agent-driven operations. ## Tools ### 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. ### 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. ### delete_project Use `delete_project` to permanently remove an Connector project from your account. This action is final and requires a confirmation step. ### delete_variable Use `delete_variable` to clean up old or unused configuration keys. This helps keep your environment variables organized and secure. ### 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. ### 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. ### get_deployment Use `get_deployment` to check the status of a specific deployment. You can review the history and metadata of any past push. ### get_project_analytics Use `get_project_analytics` to monitor request counts and latency trends. It helps you identify performance issues in your Connector infrastructure. ### 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. ### get_server_info Use `get_server_info` to verify which tools are exposed and check if your Connector is running correctly. It provides a quick status check. ### 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. ### 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. ### list_teams Use `list_teams` to see all teams associated with your account. This helps you identify which group a project belongs to. ### list_variables Use `list_variables` to audit the configuration keys for an environment. It returns metadata and masked values to keep your secrets safe. ### publish_to_registry Use `publish_to_registry` to make your Connector publicly available. It handles the submission to the official registry for you. ### 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. ### 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. ### 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. ## Prompt Examples **Prompt:** ``` List all my projects and tell me which ones are currently failing. ``` **Response:** ``` ### Project Status Overview I've checked your active projects. Here is the current status: | Project Name | Status | Error Rate | | :--- | :--- | :--- | | CustomerSupport_AI | **Critical** | 4.2% | | SalesOps_MCP | Healthy | 0.1% | | Inventory_Sync | Healthy | 0.0% | **Action Taken:** I've identified that `CustomerSupport_AI` is experiencing a high error rate. Would you like me to pull the latest deployment logs for that project? ``` **Prompt:** ``` Deploy the latest code to the staging environment. ``` **Response:** ``` ### Deployment Initiated I'm triggering the deployment for your **Staging** environment now. * **Action:** `deploy_environment` triggered. * **Target:** Staging * **Deployment ID:** `dep_99283471` I'll monitor the progress for you. You can ask me for the status at any time by providing that ID. ``` **Prompt:** ``` I need to add a new database URL for the production environment. ``` **Response:** ``` ### Update Configuration I can help you with that. Please provide the new database URL you'd like to use. Once you provide the value, I will use the `add_variable` tool to update the **Production** environment for your project. This will ensure the new connection is active for the next deployment. ``` ## Capabilities ### Multi-environment deployment Push new MCP versions to dev, staging, or production with a single command. ### Secure variable management Store and update API keys and database URLs across different deployment targets. ### Real-time log monitoring Fetch logs instantly to debug failed builds or verify successful startup. ### Development tunnels Create local testing URLs to preview your Connector before it goes live. ### Registry publishing Make your Connector discoverable to the public via the official registry. ### Git repository linking Connect your projects to git repos to keep your deployments in sync. ## Use Cases ### The Broken Production Fix An engineer sees a spike in errors. They ask the agent to fetch `get_deployment_logs`, identify the crash, and then use `add_variable` to rotate a failing API key instantly. ### New Project Onboarding A dev needs a new environment. They tell the agent to `create_project`, link the repo, and then `create_environment` for staging, all in one conversation. ### The Security Audit A security officer wants to see what's live. They ask the agent to `list_projects` and `list_variables` to verify that no secrets are exposed and all teams are correctly assigned. ### Public Registry Push A team finishes a new tool. They ask the agent to `publish_to_registry` so other users can find it, while simultaneously checking `get_server_info` to confirm it's live. ## Benefits - Deploy to multiple environments instantly using `deploy_environment` to keep dev and prod in sync. - Securely manage secrets and config keys with `add_variable` and `list_variables` for every target. - Debug faster by grabbing real-time logs with `get_deployment_logs` the moment a build fails. - Track performance trends and error rates using `get_project_analytics` to ensure high uptime. - Simplify local testing by creating dev tunnels with `get_tunnel_ticket` before hitting production. - Automate your release cycle by linking git repos and using `publish_to_registry` for public access. ## How It Works The bottom line is you replace manual dashboard clicks with direct, agent-led infrastructure commands. 1. Get your Alpic API token from the team settings dashboard. 2. Connect your AI client to the Alpic MCP and grant it permission to manage your projects. 3. Use natural language to deploy, check logs, or update variables. ## Frequently Asked Questions **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 tool. 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 tool to publish your Connector to the official registry. This makes your tools 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.