aboutsummaryrefslogtreecommitdiffstats
path: root/mcp/bridge/README.md
diff options
context:
space:
mode:
Diffstat (limited to 'mcp/bridge/README.md')
-rw-r--r--mcp/bridge/README.md17
1 files changed, 14 insertions, 3 deletions
diff --git a/mcp/bridge/README.md b/mcp/bridge/README.md
index aec3703..46cf2de 100644
--- a/mcp/bridge/README.md
+++ b/mcp/bridge/README.md
@@ -4,7 +4,7 @@ Let external MCP tools be used by LLM-Functions.
## Get Started
-1. Create a `mpc.json` at `<llm-functions-dir>`.
+### 1. Create a `mpc.json` at `<llm-functions-dir>`.
```json
{
@@ -17,6 +17,15 @@ Let external MCP tools be used by LLM-Functions.
"/tmp/foo.db"
]
},
+ "git": {
+ "command": "uvx",
+ "args": [
+ "mcp-server-git",
+ "--repository",
+ "path/to/git/repo"
+ ],
+ "prefix": false
+ },
"github": {
"command": "npx",
"args": [
@@ -31,9 +40,11 @@ Let external MCP tools be used by LLM-Functions.
}
```
-> MCP-Bridge will launch the server and register all the tools listed by the server. The tool identifier will be `server_toolname` to avoid clashes.
+> MCP-Bridge will launch the server and register all the tools listed by the server.
+
+> To avoid name clashes, The server automatically prefix tool names with `<server>_`. You can disable this behavior by add `prefix: false` to server configuration.
-2. Run the bridge server, build mcp tool binaries, update functions.json, all with:
+### 2. Run the bridge server, build mcp tool binaries, update functions.json, all with:
```
argc mcp start