About LLM Tools MCP
LLM Tools MCP is an MCP server published by VirtusLab in the AI category: connect to MCP servers right from your shell. Plugin for simonw/llm.
The repository has 38 stars and 7 forks, with the last commit 11 months ago. Six months or more without a commit doesn't mean the server is broken, but check the open issues before depending on it in production.
Install
git clone https://github.com/VirtusLab/llm-tools-mcpThis server has no ConduID identity, so agent calls to it are not receipted. Pin the version you install and review the source before granting it credentials.
Ask AI
Ask AI about LLM Tools MCP
Powered by Claude · Grounded in docs
Security checks
Static checks derived from the repository 15 hours ago. Heuristics on the source, not an audit.
- ✓README presentThe repository ships documentation.
- ✓License declaredUsable under a stated license.
- ✓Tests presentA test suite exists in the repository.
- ✓Dependencies pinnedA lockfile pins dependency versions.
- ✓No dynamic code executionSource scan found no eval, dynamic Function, or shell execution.
- !Scoped permissionsDoesn't declare a permission scope. Assume it can do anything its process can.
Releases
README
llm-tools-mcp
Connect to MCP servers right from your shell. Plugin for llm (by @simonw).
[!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
--taflag and approve each tool execution.
-
Create
mcp.jsonfile in~/.llm-tools-mcp.Example file:
{ "mcpServers": { "filesystem": { "command": "npx", "args": [ "-y", "@modelcontextprotocol/server-filesystem", "~/demo" ] } } } -
List available tools.
[!WARNING]
llm toolsis not implemented for dynamic toolboxes (see this), so tools loaded as part of MCP won't be visible.llm tools list -
Run
llmwith tools.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
- Release alpha version
- support all transports
- streamable http
- sse
- stdio
- Build a solid test suite
- test config file validation
- test sse with dummy server
- test stdio with dummy server
- test http streamable with dummy server (see #1)
- manual test for sse with real server
- manual test for stdio with real server
- manual test for http streamable with real server
- Redirect
stdout/stderrfrom the MCP SDK to a file or designated location - Reuse stdio connections
- Support non-stdio MCP servers
- Handle tool name conflicts (prefix with mcp server name?)
- Gather feedback on the
~/.llm-tools-mcpdirectory naming - Improve failure handling:
- When connecting to an MCP server fails
- When
mcp.jsonis malformed
- Improve this README:
- Add more detail in the Development section (mention
uv?)
- Add more detail in the Development section (mention
README fetched from the repository 15 hours ago. The original is authoritative.