get_project_detail — fline MCP Tool Read-only
get_project_detail
(get project detail) 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 get_project_detail from your client
- Claude Code fline get_project_detail run in your project directory
- Claude Desktop fline get_project_detail ~/Library/Application Support/Claude/claude_desktop_config.json
- Cursor fline get_project_detail ~/.cursor/mcp.json
- VS Code fline get_project_detail .vscode/mcp.json
- Zed fline get_project_detail ~/.config/zed/settings.json
- Windsurf fline get_project_detail ~/.codeium/windsurf/mcp_config.json
- Cline fline get_project_detail ~/Library/Application Support/Code/User/globalStorage/saoudrizwan.claude-dev/settings/cline_mcp_settings.json
- Gemini CLI fline get_project_detail ~/.gemini/settings.json
- Grok fline get_project_detail .mcp.json (in your project root)
- ChatGPT fline get_project_detail Settings → Connectors → Advanced → Developer mode
- Claude.ai fline get_project_detail Settings → Connectors → Add custom connector
- LangChain fline get_project_detail pip install langchain-mcp-adapters
Fastest route
claude mcp add --transport http fline https://mcp.fline.sh/mcpOther tools on this server
- list_projects
- create_project
- delete_project
- get_upload_url
- complete_upload
- get_project
- submit_declaration
- answer_questions
- declare_env_names
- 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_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.