Pooja/mcp doc fix (#506)

* Add Flash Docs

* clarify API key setup and update create with agent

* Moved from flash to ff cli

* Moved to Advanced section

* Fix broken links

* move around the files and split the section into pages

* Update FlutterFlow CLI documentation: rename 'Download Projects' to 'Exporting Projects' and enhance 'Build with AI Agents' section with more info about the mcp tool

* remove redundant info box and clarify workspace description

* Remove outdated DSL gaps

* address review comments

* Fix broken links

* nit fixes

* reorganize sections on agent edit scope, branches, and rollback, and clarify project switching process.

* Add Makefile for staging deployment and update README with usage instructions

* added visuals

* nit fix

* reorganizing MCP server tools into categories

* Update Google Analytics configuration to conditionally set tracking ID based on environment

* nit fix

* [bugfix] wrong step name for existing project id

* [bugfix] remove unintended header + add hyperlinks

---------

Co-authored-by: Pinkesh <[email protected]>

Author: PoojaB26

docs/ff-concepts/advanced/flutterflow-cli/flutterflow-mcp.md

@@ -279,14 +279,15 @@ So nothing gets silently overwritten, but expect occasional retries when you and
 
 - Anything outside the FlutterFlow project itself — running the app, deploying it, creating Firebase projects, managing secrets, App Store submissions.
 
-## MCP Server Tools
 
 ### Refreshing Stale Context
 
 If you've made visual edits since the agent last read the project, the agent's local snapshot is stale. Two ways to fix it:
 
-- **Ask the agent to refresh.** Most agents call the MCP `refreshContext` tool on their own when they detect drift, but you can prompt explicitly: "refresh the project context."
-- **Run it from the CLI.** `flutterflow ai context-check` reports whether the local snapshot is behind, and `flutterflow ai refresh-context <project-id>` pulls the latest.
+- **Ask the agent to refresh.** Most agents call the [`refresh-context`](#mcp-tools) tool on their own when they detect drift, but you can prompt explicitly: "refresh the project context."
+- **Run it from the CLI.** `flutterflow ai context-check` reports whether the local snapshot is behind, and `flutterflow ai refresh-context <project-id>` pulls the latest. 
+
+See [MCP tools](#mcp-tools) for the full command list.
 
 ## Branches and Rollback