MCP servers and tools
The agent's tools, and adding more with MCP servers.
Built-in tools
| Tool | What it does | Shown on the phone as |
|---|---|---|
| read | Read a file | Reading path |
| write | Create or overwrite a file | Editing path |
| edit, multiedit | Change text in a file | Editing path |
| apply_patch | Change several files at once | Editing … |
| bash | Run a command in the project | Running command |
| grep, glob | Search contents or file names | Searching pattern |
Every tool follows your rules in Settings → Permissions (Allow, Ask, Deny). An Ask becomes an approval you can answer from your phone. BambooKit never runs commands itself: actions from the phone are passed to the agent, so its tools and rules stay in charge.
MCP servers
MCP servers give the agent extra tools, such as databases, browsers or issue trackers. Open the MCP list with Ctrl+; (Toggle MCPs): it shows each server as connected, failed, needs auth or disabled. Toggle servers there, and click needs auth to sign in to servers that use OAuth.
Add servers in the agent's configuration file (the Settings → MCP page is not editable yet). Example:
{
"mcp": {
"filesystem": {
"type": "local",
"command": ["npx", "-y", "@modelcontextprotocol/server-filesystem", "C:\\Users\\me\\code"],
"enabled": true
},
"issues": {
"type": "remote",
"url": "https://mcp.example.com/mcp",
"headers": { "Authorization": "Bearer <YOUR_TOKEN>" }
}
}
}There is one global configuration file for your Windows user and, optionally, one in a project's root folder; their exact locations are listed under Agent engine → Configuration files in the BambooKit documentation repository. MCP servers run on your PC with your user's rights; the phone sees their tool calls but cannot add or start servers. Keep tokens out of files you commit.