Skip to main content
Glama
citizenteam

Citizen Deployment MCP Server

by citizenteam

Server Configuration

Describes the environment variables required to run the server.

NameRequiredDescriptionDefault

No arguments

Capabilities

Features and capabilities supported by this server

CapabilityDetails
tools
{}
resources
{}

Tools

Functions exposed to the LLM to take actions

NameDescription
get_instructions

CRITICAL: Call this FIRST before ANY deployment operation. Returns deployment instructions including polling intervals, error handling guides, and best practices. You MUST read and follow these instructions before calling deploy_from_git, deploy_from_local, or get_deployment_status.

authenticate

Authenticate with Citizen platform using device flow. ALWAYS call this first if check_auth_status shows not authenticated. Opens browser for user authorization.

check_auth_status

Check current authentication status. Call this at the start of any deployment workflow to ensure you are authenticated.

list_servers

List all Citizen servers in your organization. This discovers available deployment targets. Call this before list_apps to see which servers are available.

list_apps

List all applications you have access to (RBAC filtered). ALWAYS call this before deploying to understand which apps exist and which you have permission to deploy.

get_app_info

Get detailed information about a specific app including current deployment status and configuration.

deploy_from_git

Deploy application from git repository (requires member+ role). Use when user provides a git URL. After deployment starts, ALWAYS monitor with get_deployment_status until completion. If build fails, read logs to understand error and fix accordingly.

deploy_from_local

Deploy from local directory. Automatically creates tar.gz, uploads, and deploys. Use this when deploying current directory, local files, or when iterating on fixes. ALWAYS monitor with get_deployment_status after calling. If build fails, analyze logs, fix files locally, and redeploy.

get_deployment_status

Get deployment run status and detailed logs. CRITICAL: After starting any deployment, poll this every 5-10 seconds until status is "completed" or "failed". If failed, carefully read ALL logs to identify the error (missing dependencies, version mismatches, port binding issues, etc.) and suggest fixes.

list_deployment_runs

List recent deployment runs for an app with their status. Useful for debugging when user mentions "my last deployment failed".

open_app_url

Open app URL in system browser (not Cursor browser). Use this after successful deployment to verify the app is working. Opens the default browser just like device authentication flow.

Prompts

Interactive templates invoked by user choice

NameDescription

No prompts

Resources

Contextual data attached and managed by the client

NameDescription
Deployment InstructionsComplete guide for deploying applications to Citizen platform, including error handling, best practices, and example workflows

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/citizenteam/mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server