Bring Mcp Server
to Cursor

Use this to set API keys, database URLs, feature flags, or any configuration needed by your MCP server. Requires project ID, environment ID, variable key, and value. Variable values are stored securely. Add a new environment variable to an Alpic environment

Requires environment name and project ID. Optionally set initial variables and configuration. Each environment gets a unique URL for MCP client connections. Returns the created environment details. Create a new deployment environment (dev, staging, prod) for an Alpic project

Requires project name and team ID. Optionally set description, repository URL, and initial configuration. Returns the created project details including the new project ID needed for subsequent operations. Create a new MCP server project in Alpic

This action cannot be undone. Use with caution. Requires the project ID. Confirm with the user before proceeding. Delete an Alpic MCP server project

Use this to clean up unused configuration keys. Requires project ID, environment ID, and variable key. Delete an environment variable from an Alpic environment

The deployment runs asynchronously. Returns the deployment ID which can be used with get_deployment to check status. Use this to push new MCP server versions to dev, staging, or production environments. Trigger a new deployment for a specific Alpic environment

Requires the deployment ID. Use this to check if a deployment succeeded, review deployment history, or debug failed deployments. Get detailed status and metadata for a specific Alpic deployment

Useful for debugging failed deployments, understanding build output, or verifying successful startup of the MCP server. Requires project ID and environment ID. Get deployment logs for a specific Alpic environment

Requires the project ID from list_projects results. Use this to review project settings before making updates or triggering deployments. Get detailed information about a specific Alpic MCP server project

Requires the project ID. Use this to monitor MCP server health, identify performance trends, and troubleshoot issues. Get analytics and usage data for a specific Alpic project

Use this to verify which MCP tools are exposed and confirm the server is running correctly. Get server information and status for a specific Alpic project

Returns the tunnel URL and ticket token. Use this during development to test your MCP server before deploying to a production environment. Get a tunnel ticket for local development and testing of an MCP server

Each environment has its own URL, variables, and deployment status. Returns environment IDs, names, URLs, and current deployment state. Use this to identify which environment to deploy to or manage variables for. List all environments (dev, staging, prod) for a specific Alpic project

Returns project IDs, names, descriptions, associated teams, deployment status, and environment counts. Use this to overview your entire MCP infrastructure before managing specific projects or triggering deployments. List all MCP server projects in your Alpic account

Each team contains projects and environments for deploying MCP servers. Returns team IDs, names, and member counts. Use this first to identify which team to manage projects under. List all teams associated with your Alpic account

Variable values are masked for security. Returns variable keys and metadata. Use this to audit environment configuration before deploying or adding new variables. List all environment variables configured for an Alpic environment

Requires project ID and optionally a server description and category. Use this to make your MCP server publicly available. Publish an MCP server to the official MCP registry via Alpic

Only pass the fields you want to change. Requires the project ID from list_projects results. Use this to rename projects, update descriptions, or point to a new repository branch. Update an existing Alpic MCP server project configuration