Move workflow to top

Signed-off-by: Dan Barr <[email protected]>

Author: danbarr

docs/toolhive/guides-mcp/meta-mcp.mdx

@@ -32,6 +32,16 @@ confusion by narrowing down the toolset to only those relevant for a given task.
 It also simplifies client configurations by providing a single access point to
 multiple MCP servers.
 
+The meta-mcp workflow:
+
+1. Your AI client sends the request to meta-mcp
+2. Meta-mcp uses hybrid search (semantic + keyword) to find relevant tools
+   across all connected MCP servers
+3. Meta-mcp server returns the short list of matching tools to the client
+4. Client selects one tool from the short list and uses meta-mcp to call that
+   tool
+5. Results are returned from meta-mcp to the client
+
 ## Metadata
 
 <MCPMetadata name='meta-mcp' />
@@ -138,20 +148,12 @@ Once meta-mcp is configured and running, you can use the same prompts you would
 normally use with individual MCP servers. The meta-mcp server automatically
 discovers and routes to appropriate tools.
 
-**Direct task examples:**
+Using the example MCP servers above, here are some sample prompts:
 
-- "Get the details of GitHub issue 1911 from stacklok/toolhive repo"
-- "List recent PRs from stacklok/toolhive repo"
-
-**The meta-mcp workflow:**
-
-1. Your AI client sends the request to meta-mcp
-2. Meta-mcp uses hybrid search (semantic + keyword) to find relevant tools
-   across all connected MCP servers
-3. Meta-mcp server returns the short list of matching tools to the client
-4. Client selects one tool from the short list and uses meta-mcp to call that
-   tool
-5. Results are returned from meta-mcp to the client
+- "Get the details of GitHub issue 1911 from the stacklok/toolhive repo"
+- "List recent PRs from the stacklok/toolhive repo"
+- "Fetch the latest news articles about AI"
+- "What is the current time in Tokyo?"
 
 ## Available tools