declare_env_names — fline MCP Tool
declare_env_names
(declare env names) is one of 40 tools on the
fline
MCP server. Connect the server and your client discovers it on the handshake.
by client
How to call declare_env_names from your client
- Claude Code fline declare_env_names run in your project directory
- Claude Desktop fline declare_env_names ~/Library/Application Support/Claude/claude_desktop_config.json
- Cursor fline declare_env_names ~/.cursor/mcp.json
- VS Code fline declare_env_names .vscode/mcp.json
- Zed fline declare_env_names ~/.config/zed/settings.json
- Windsurf fline declare_env_names ~/.codeium/windsurf/mcp_config.json
- Cline fline declare_env_names ~/Library/Application Support/Code/User/globalStorage/saoudrizwan.claude-dev/settings/cline_mcp_settings.json
- Gemini CLI fline declare_env_names ~/.gemini/settings.json
- Grok fline declare_env_names .mcp.json (in your project root)
- ChatGPT fline declare_env_names Settings → Connectors → Advanced → Developer mode
- Claude.ai fline declare_env_names Settings → Connectors → Add custom connector
- LangChain fline declare_env_names pip install langchain-mcp-adapters
Fastest route
claude mcp add --transport http fline https://mcp.fline.sh/mcp
Other tools on this server
- list_projects
- create_project
- delete_project
- get_upload_url
- complete_upload
- get_project
- submit_declaration
- answer_questions
- get_secrets_link
- deploy
- get_deploy_status
- get_images
- get_logs
- get_usage
- attach_domain
- create_service
- list_services
- delete_service
- get_config
- check_config
- refresh_config
- list_domains
- check_domain
- delete_domain
- list_env_names
- delete_env_name
- set_env
- get_project_detail
- get_events
- get_service
- pause_service
- resume_service
- stop
- restart
- list_versions
- rollback
- attach_external
- detach_external
- list_external
This list was read from the server itself, by connecting to it and calling tools/list on 17 October 2026. It is what
the server actually exposes, not what its listing claims.
Mutating and Read-only are read off each tool's name, not its schema — a hint, not a guarantee. The registry stores tool names only; connect the server for its live schemas.