1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
|
# MCP-Bridge
Let external MCP tools be used by LLM-Functions.
## Get Started
### 1. Create a `mcp.json` at `<llm-functions-dir>`.
```json
{
"mcpServers": {
"sqlite": {
"command": "uvx",
"args": [
"mcp-server-sqlite",
"--db-path",
"/tmp/foo.db"
]
},
"git": {
"command": "uvx",
"args": [
"mcp-server-git",
"--repository",
"path/to/git/repo"
],
"prefix": false
},
"github": {
"command": "npx",
"args": [
"-y",
"@modelcontextprotocol/server-github"
],
"env": {
"GITHUB_PERSONAL_ACCESS_TOKEN": "<YOUR_TOKEN>"
}
}
}
}
```
> 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:
```
argc mcp start
```
> Run `argc mcp stop` to stop the bridge server, recover functions.json.
> Run `argc mcp logs` to check the server's logs.
|