Skip to main content
Environment variable values are masked by default for security. Use show_values: true only when necessary.

​
detect_services

Detect cloud services and deployment platforms configured in the project. Scans for Firebase, Supabase, Vercel, Netlify, Docker, Railway, and AWS Amplify configurations.
​
project_id
string
Project ID (auto-detected if omitted)
Returns: Array of detected services with configuration details.
​
service
string
Service name (e.g., “Firebase”, “Vercel”, “Docker”)
​
config_files
array
List of configuration files found (e.g., firebase.json, vercel.json)
​
detected
boolean
Whether the service was detected in the project
Example: 
{
  "name": "detect_services",
  "arguments": {}
}
Response: 
[
  {
    "service": "Vercel",
    "config_files": ["vercel.json"],
    "detected": true
  },
  {
    "service": "Docker",
    "config_files": ["Dockerfile", "docker-compose.yml"],
    "detected": true
  },
  {
    "service": "Firebase",
    "config_files": [],
    "detected": false
  }
]

​
list_env_files

List all environment files (.env, .env.local, .env.development, etc.) in the project with variable counts.
​
project_id
string
Project ID (auto-detected if omitted)
Returns: Array of environment files found in the project.
​
file_name
string
Name of the environment file (e.g., .env, .env.local)
​
file_path
string
Absolute path to the file
​
variable_count
integer
Number of variables defined in the file
​
size_bytes
integer
File size in bytes
Example: 
{
  "name": "list_env_files",
  "arguments": {}
}
Response: 
[
  {
    "file_name": ".env",
    "file_path": "/Users/you/projects/my-app/.env",
    "variable_count": 12,
    "size_bytes": 456
  },
  {
    "file_name": ".env.local",
    "file_path": "/Users/you/projects/my-app/.env.local",
    "variable_count": 3,
    "size_bytes": 89
  }
]

​
get_env_variables

Parse and return variables from a specific environment file. Values are masked by default for security.
​
file_name
string
required
Environment file name (e.g., .env, .env.local)
​
show_values
boolean
Show actual values instead of masked (default: false)
​
project_id
string
Project ID (auto-detected if omitted)
Returns: Object mapping variable names to values (masked or plain).
​
variables
object
Dictionary of environment variable names to values
​
file_name
string
Name of the file that was parsed
Example (masked values): 
{
  "name": "get_env_variables",
  "arguments": {
    "file_name": ".env"
  }
}
Response: 
{
  "file_name": ".env",
  "variables": {
    "DATABASE_URL": "***",
    "API_KEY": "***",
    "OPENROUTER_API_KEY": "***",
    "DEBUG": "true",
    "PORT": "3000"
  }
}
Example (showing values): 
{
  "name": "get_env_variables",
  "arguments": {
    "file_name": ".env",
    "show_values": true
  }
}
Only use show_values: true when absolutely necessary. Environment variables often contain sensitive credentials.

​
Supported Services

CodeFire can detect the following services:
ServiceConfiguration Files
Firebasefirebase.json, .firebaserc
Supabasesupabase/config.toml
Vercelvercel.json, .vercel/
Netlifynetlify.toml, .netlify/
DockerDockerfile, docker-compose.yml
Railwayrailway.json, railway.toml
AWS Amplifyamplify/ directory

​
Security Best Practices

The API masks values by default. Only request plain values when you need to use them programmatically.
Environment files should be in .gitignore. CodeFire helps detect if they’re tracked by git.
Keep production secrets in .env.production, development config in .env.local, etc.
If environment variables are ever committed to version control, rotate those credentials immediately.

​
Notes

  • Environment variables are project-scoped
  • Values are masked by default (shown as ***)
  • Only .env* files in the project root are scanned
  • Service detection is based on config files, not running processes

Project Management

Learn about project structure and configuration

MCP Integration

Use environment tools in AI workflows

Build docs developers (and LLMs) love

Get started for freeTalk to us