Skip to content

metatools-mcp

metatools-mcp is the MCP server that exposes the tool stack via a small, progressive-disclosure tool surface. It composes toolfoundation, tooldiscovery, toolexec, and optionally toolexec/runtime for sandboxed execution.

Docs

Deep dives

Motivation

  • One MCP surface for discovery, docs, and execution
  • Progressive disclosure to keep tool context small
  • Pluggable design for search, runtimes, and engines

MCP tools exposed

  • search_tools
  • list_namespaces
  • describe_tool
  • list_tool_examples
  • run_tool
  • run_chain
  • execute_code (optional)

Quickstart

idx := index.NewInMemoryIndex()
docs := tooldoc.NewInMemoryStore(tooldoc.StoreOptions{Index: idx})
runner := run.NewRunner(run.WithIndex(idx))

cfg := adapters.NewConfig(idx, docs, runner, nil)
server, _ := server.New(cfg)

_ = server.Run(context.Background(), &mcp.StdioTransport{})

Usability notes

  • Fewer MCP tools means simpler agent prompts
  • Outputs are structured and aligned to MCP schemas
  • Search and execution behaviors are deterministic by default

Runtime notes (execute_code)

execute_code is optional and wired behind the toolruntime build tag. By default, the runtime uses the unsafe dev profile; when Docker is available, set METATOOLS_RUNTIME_PROFILE=standard to enable the hardened Docker backend. WASM can be enabled with METATOOLS_WASM_ENABLED=true and selected with METATOOLS_RUNTIME_BACKEND=wasm.

Interface Contracts

  • Transport: thread-safe; Serve honors context; Close is idempotent.
  • Backend: thread-safe; ListTools/Execute honor context; streaming backends return non-nil channel when err is nil.
  • ToolProvider: thread-safe; Handle honors context; streaming providers return non-nil channel when err is nil.

Next

  • Server architecture: architecture.md
  • Ordered execution plan: plan-of-record.md
  • Configuration and env vars: usage.md
  • Examples: examples.md
  • Design Notes: design-notes.md
  • User Journey: user-journey.md

Proposals

Master Plan: - ROADMAP - Master roadmap with all work streams, phases, and milestones

Architecture: - Pluggable Architecture - Extensible, modular design - Architecture Evaluation - Championship-level comparison - Component Library Analysis - Tool* library ecosystem - Architecture Review - Comprehensive proposal analysis and consistency check - MCP Spec Alignment - Targeted spec compliance improvements

Features: - Protocol-Agnostic Tools - Composable toolsets and protocol adapters - Multi-Tenancy Extension - Tenant isolation patterns - Agent Skills - Higher-level capability composition (see ROADMAP)

Implementation: - Implementation Phases - Phased rollout plan