Install
$ agentstack add mcp-virtuslab-llm-tools-mcp ✓ scanned · ✓ verified — works with Claude Code, Cursor, and more.
Security review
✓ PassedNo issues found. Passed automated security review. · v0.1.0 How review works →
- ✓ Prompt-injection patterns
- ✓ Secret / credential exfiltration
- ✓ Dangerous shell & filesystem operations
- ✓ Untrusted network calls
- ✓ Known-malicious package signatures
What it can access
- ✓ Network access No
- ✓ Filesystem access No
- ✓ Shell / process execution No
- ✓ Environment & secrets No
- ✓ Dynamic code execution No
From automated source analysis of v0.1.0. “Used” means the capability is present in the source — more access means more to trust, not that it’s unsafe.
About
llm-tools-mcp
Connect to MCP servers right from your shell. Plugin for llm (by @simonw).
[](https://pypi.org/project/llm-tools-mcp/) [](https://github.com/VirtusLab/llm-tools-mcp/releases) [](https://github.com/VirtusLab/llm-tools-mcp/actions/workflows/test.yml) [](https://github.com/VirtusLab/llm-tools-mcp/blob/main/LICENSE)
> [!Note] > Current focus: Authorization #4
Installation
Install this plugin in the same environment as LLM:
llm install llm-tools-mcp
Usage
> [!WARNING] > It's recommended to use the --ta flag and approve each tool execution.
- Create
mcp.jsonfile in~/.llm-tools-mcp.
Example file:
``json { "mcpServers": { "filesystem": { "command": "npx", "args": [ "-y", "@modelcontextprotocol/server-filesystem", "~/demo" ] } } } ``
- List available tools.
> [!WARNING] > llm tools is not implemented for dynamic toolboxes (see this), > so tools loaded as part of MCP won't be visible.
``sh llm tools list ``
- Run
llmwith tools.
``sh llm --ta -T MCP "what files are in the demo directory? show me contents of one of the files (any)" ``
Other examples
Dynamically change your MCP config:
llm --ta -T 'MCP("/path/to/custom/mcp.json")' "your prompt here"
Development
Now (to be verified)
- Sync dependencies:
uv sync --all-extras - Run linters / type checker:
./check.sh - Run tests:
./test.sh - Run end to end tests:
./e2e/e2e-docker.sh
To Do
- [x] Release alpha version
- [x] support all transports
- [x] streamable http
- [x] sse
- [x] stdio
- [ ] Build a solid test suite
- [x] test config file validation
- [x] test sse with dummy server
- [x] test stdio with dummy server
- [x] test http streamable with dummy server (see #1)
- [x] manual test for sse with real server
- [x] manual test for stdio with real server
- [x] manual test for http streamable with real server
- [x] Redirect
stdout/stderrfrom the MCP SDK to a file or designated location - [ ] Reuse stdio connections
- [x] Support non-stdio MCP servers
- [ ] Handle tool name conflicts (prefix with mcp server name?)
- [ ] Gather feedback on the
~/.llm-tools-mcpdirectory naming - [x] Improve failure handling:
- [x] When connecting to an MCP server fails
- [x] When
mcp.jsonis malformed - [ ] Improve this README:
- [ ] Add more detail in the [Development](#development) section (mention
uv?)
Source & license
This open-source MCP server is cataloged on AgentStack and links to its original source — we do not rehost the code.
- Author: VirtusLab
- Source: VirtusLab/llm-tools-mcp
- License: Apache-2.0
- Homepage: https://pypi.org/project/llm-tools-mcp/
Install and usage instructions live in the source repository linked above.
Reviews
No reviews yet — be the first.
Write a review
Versions
- v0.1.0 Imported from the upstream source.