Skip to content

Commit 801e26b

Browse files
committed
ad doc workflows
1 parent 80834f8 commit 801e26b

File tree

1 file changed

+8
-6
lines changed

1 file changed

+8
-6
lines changed

docs/Integration-MCP.md

Lines changed: 8 additions & 6 deletions
Original file line numberDiff line numberDiff line change
@@ -1,14 +1,16 @@
11
Model Context Protocol is a way for:
22

3-
1. LLMs to ***choreograph*** multiple MCP servers in a chain of calls - an agentic workflow. MCPs support shared contexts and goals, enabling the LLM to use the result from 1 call to determine whether the goals has been reached, or which service is appropriate to call next
3+
1. **Bus User ad hoc flows** using existing published mcp services (vs. hard-coding in IT as an endpoint; flows can be cached for repeated use)
44

5-
2. Chat agents to ***discover*** and ***call*** external servers, be they databases, APIs, file systems, etc. MCPs support shared contexts and goals, enabling the LLM
5+
* ***Natural Language access*** to corporate databases for improved user interfaces
66

7-
3. ***Corporate database participation*** in such flows, by making key functions available as MCP calls.
7+
* LLMs ***choreograph*** multiple MCP calls (to 1 or more MCP servers) in a chain of calls - an agentic workflow. MCPs support shared contexts and goals, enabling the LLM to use the result from 1 call to determine whether the goals has been reached, or which service is appropriate to call next
8+
9+
3. Chat agents to ***discover*** and ***call*** external servers, be they databases, APIs, file systems, etc. MCPs support shared contexts and goals, enabling the LLM
10+
11+
* ***Corporate database participation*** in such flows, by making key functions available as MCP calls.
812

9-
4. Chat agents to invoke ***NLM Natural Language services*** to corporate databases for improved user interfaces
1013

11-
5. Bus Users can create their own flows using existing published mcp services (vs. hard-coding in IT as an endpoint; flows can be cached for repeated use)
1214

1315
For tech background, see Appendix 2.
1416

@@ -75,7 +77,7 @@ You will need a ChatGPT APIKey.
7577
2. MCP Client Executor sends the query + schema (as prompt or tool definition) to the external LLM, here, ChatGPT (requires API Key).
7678

7779
* Tool definitions are OpenAI specific, so we are sending the schema in each prompt.
78-
* This schema is copied from `docs/db.dbml` (already created by als)
80+
* This schema is derived from `docs/db.dbml` (already created by als)
7981
* Note this strongly suggests this is a **subset** of your database.
8082

8183
3. LLM returns an MCP Tool Context JSON block.

0 commit comments

Comments
 (0)