Agenten stärken
Installation vom Herausgeber. Kein PlugMCP-Endpunkt.
Host a copy with our keys and logs.
Noch kein paketiertes Release in der Registry. Folgen Sie der README des Repositorys.
Remote-URL oder ein Befehl auf Ihrem Rechner? Worin sich die beiden Installationen unterscheiden
Auf PlugMCP ausführen
A new server you create. It is not this listing's official endpoint. Use the publisher install when you want their URL and their credentials.
StartenVom Herausgeber
Shared machinery for a family of standalone MCP tool servers.
Each server (hex-mcp, ssh-mcp, eval-mcp, …) is a thin crate: implement
ToolGroup, call run. Everything else lives here, so a fix lands in every
server at once:
Shared machinery for standalone MCP tool servers: CLI, transports, single-tool mode and timeouts on top of the official rmcp SDK
--transport--single-tool--timeout--bind--auth-token--list-toolsrmcp SDK.--single-tool — collapses every tool into one dispatching tool for
clients that cap how many they accept.timeout argument on every tool, clamped to --max-timeout.--allow-unauthenticated is passed.use mcp_toolkit::{ServerOptions, ToolDef, ToolGroup, ToolOutput, ToolResult};
use async_trait::async_trait;
use serde_json::{Value, json};
struct Greeter;
#[async_trait]
impl ToolGroup for Greeter {
fn tools(&self) -> Vec<ToolDef> {
vec![ToolDef::new("greet", "Say hello.", json!({ "type": "object" }))]
}
async fn call(&self, _name: &str, _args: Value) -> ToolResult<ToolOutput> {
Ok(ToolOutput::text("hello"))
}
}
#[tokio::main]
async fn main() -> Result<(), Box<dyn std::error::Error>> {
let options = ServerOptions::parse();
mcp_toolkit::run("greeter", env!("CARGO_PKG_VERSION"), Arc::new(Greeter), options).await?;
Ok(())
}
ToolGroup trait rather than rmcp's macrosToolGroup is plain data plus an async function, deliberately independent of
rmcp. That means a tool crate can be unit-tested without standing up a
protocol server, and a host process can embed the tools directly — which is how
omni-mcp consumes them, as library calls rather than sidecar subprocesses.
--single-tool also needs to synthesise a tool at runtime from the others,
which the attribute macros cannot express.
--transport sse is accepted as an alias for http. The standalone SSE
transport was deprecated in the MCP specification in favour of Streamable HTTP,
which uses SSE for its streaming responses.
./scripts/build.sh
Runs cargo fmt --check, cargo clippy -D warnings (max 100 lines per
function) and the tests (which enforce max 1000 lines per file).
Unlicense (public domain).
Shared machinery for standalone MCP tool servers: CLI, transports, single-tool mode and timeouts on top of the official rmcp SDK
Tools
Noch keine Tool-Liste. Remote-Server erhalten eine nach dem ersten Health-Check.
FAQ
Kopieren Sie auf dieser Seite die stdio-Konfiguration für Cursor, Claude Desktop, Claude Code oder VS Code. Sie nutzt die Installation des Herausgebers, keinen PlugMCP-Proxy.
In diesem Eintrag ist keine erforderliche Umgebungsvariable aufgeführt.
MCP Toolkit läuft lokal über stdio.
Zuletzt geprüft: 2026-11-05. Shared machinery for standalone MCP tool servers: CLI, transports, single-tool mode and timeouts on top of the official rmcp SDK
