Build
Connect & operate
Design & teams
Start hereScope a build in one callBring a spec, a wireframe, or a paragraph. You leave with an architecture, a timeline, and a number.Book a scoping call
AI software
LLM & data systems
Vibe coding
Ready to ship?Put AI where the work isAgents, RAG, and private LLMs wired into the systems your team already uses — not a chatbot bolted to a homepage.Discuss an AI project
Domain firstWe learn your workflow before we model itRegulated, operational, or high-volume — the constraints belong in the schema, not in a training doc.Talk about your domain
Plan smarterEstimate before you commitCost ranges, scope templates, and the questions we ask in discovery — free, no form.Open the cost calculator
Real conversationsTalk with a technical leadNo SDR, no discovery gauntlet. The person on the call is the one who scopes the build.Book a call
MCP Servers · f

mcptools

mcptools is a Go-based CLI utility that discovers, calls, and manages tools, resources, and prompts from Model Context Protocol (MCP) servers. It supports multiple transport methods (stdio, HTTP, SSE) and output formats, with features including interactive shells, web interfaces, mock servers, and request proxying.

Source: GitHub — github.com/f/mcptools
1.6k
GitHub stars
124
Forks
Go
Primary language
MIT
License (OSI-approved)

Key facts

Objective fields from the source. Values we can't verify are shown as “Unknown” rather than guessed.

FieldValue
Repositoryf/mcptools
Ownerf
Primary languageGo
LicenseMIT — OSI-approved
Stars1.6k
Forks124
Open issues35
Latest releasev0.7.1 (2025-05-05)
Last updated2025-12-18
Sourcehttps://github.com/f/mcptools

What mcptools is

A command-line interface written in Go for MCP server interaction using JSON-RPC 2.0. Supports stdio transport, HTTP/HTTPS with SSE and streamable protocols, and offers functionality for discovery, tool invocation, resource access, session management, and server mocking/proxying.

Quickstart

Get the mcptools source

Clone the repository and explore it locally.

terminalbash
git clone https://github.com/f/mcptools.gitcd mcptools# follow the project's README for install & configuration

Need it deployed, integrated, or customized instead? DEV.co ships production installs.

Best use cases

MCP Server Discovery and Testing

Quickly list and test available tools, resources, and prompts from MCP servers during development and integration testing without building custom client code.

Interactive MCP Exploration

Use the interactive shell to explore and debug MCP server behavior in real-time, with support for multiple output formats (table, JSON, pretty-printed).

CI/CD and Automation Integration

Invoke MCP tools programmatically from scripts or pipelines using JSON parameter passing and structured output formats, enabling headless automation workflows.

Implementation considerations

  • Binary installation via Homebrew (macOS) is straightforward; Windows and Linux users must build from source via 'go install', requiring Go toolchain setup.
  • Transport auto-detection works for `/sse` paths and HTTP/HTTPS URLs; explicit specification may be needed for non-standard MCP server configurations.
  • Interactive shell and web interface are convenient for exploration but not documented as suitable for production monitoring or long-running services.
  • Mock server and proxy modes add extensibility; ensure shell script execution permissions and error handling are configured for proxy mode reliability.
  • Open issues (35 count) and relatively recent project creation (2025-03-25) suggest active development; review roadmap and pending issues for feature/stability impact.

When to avoid it — and what to weigh

  • Heavy Stateful RPC Workflows — If your use case requires complex multi-step sessions with complex state management beyond basic request/response, consider purpose-built client SDKs or custom integrations.
  • GUI-First User Experience Required — This is a CLI-only tool; if end-users need graphical interfaces, the web interface mode provides basic browsing but is not a full desktop application.
  • Windows Native GUI Dependency — While Windows is supported via source compilation, this is primarily a command-line utility; native Windows GUI integration is not available.
  • Production SLA-Critical Transport — Project is active (last push 2025-12-18) but still at v0.7.1; HTTP SSE transport only supports MCP protocol version 2024-11-05, limiting protocol flexibility.

License & commercial use

MIT License (MIT) – permissive open-source license permitting free use, modification, distribution, and commercial incorporation with attribution required.

MIT License explicitly permits commercial use without restriction. However, mcptools itself is a development and testing utility; any MCP servers or data accessed through it remain subject to their own licenses. Verify compliance of connected servers and their license terms before commercial deployment.

DEV.co evaluation signals

Editorial assessment — not user reviews. Directional, with an explicit confidence level.

SignalAssessment
MaintenanceActive
DocumentationAdequate
License clarityClear
Deployment complexityLow
DEV.co fitGood
Assessment confidenceHigh
Security considerations

Execution of arbitrary shell scripts in proxy mode requires careful input validation and access control. Stdio transport inherits security posture of spawned MCP servers. HTTP/HTTPS connections should use TLS; no explicit TLS pinning or certificate validation documentation provided. No secrets management documented; ensure credentials in MCP server configurations are stored securely. No authentication/authorization layer in the tool itself; rely on MCP server-level controls.

Alternatives to consider

Official MCP Inspector (Anthropic)

Official tool for MCP discovery; may have different transport support, tighter Anthropic ecosystem integration, and official security/support. Compare features via linked blog post.

Custom Go/Python MCP Client SDKs

Purpose-built SDKs offer programmatic control, deeper session management, and integration into larger applications. Trade-off: require code development vs. CLI simplicity.

For HTTP-only MCP servers, direct curl calls reduce tool dependency. Trade-off: manual JSON formatting, no discovery helpers, poor UX for exploration.

Software development agency

Build on mcptools with DEV.co software developers

Start with mcptools to explore MCP server capabilities via CLI. Perfect for development, testing, and scripting. MIT-licensed and actively maintained.

Talk to DEV.co

Related open-source tools

Surfaced by semantic similarity across the DEV.co open-source index.

Related on DEV.co

Explore the category and the services that help you build with it.

mcptools FAQ

Can I use mcptools in production to call MCP tools?
Technically yes (CLI tools can be called from any process), but the project is in active v0.x development. Evaluate stability requirements against the roadmap and issue tracker. No SLA or production support documentation is provided.
What is the difference between HTTP SSE and Streamable HTTP transport?
SSE is a legacy transport supporting only MCP protocol 2024-11-05; Streamable HTTP is the modern recommended approach with session management, resumability, and flexible response handling. Default for HTTP/HTTPS URLs.
How do I integrate mcptools into CI/CD pipelines?
Use the `call` command with JSON parameter flags (`--params '{...}'`) and structured output (`--format json`) for parsing. Script integration examples are shown in the README; ensure error handling for tool failures.
Is there an SDK or Go library for programmatic use?
Not clearly stated. mcptools appears to be CLI-only; for programmatic use in Go applications, building custom clients against MCP protocol specifications may be necessary.

Senior engineers for your next build

The gap between a working mcptools demo and a supportable mcp servers system is where DEV.co works. We offer custom software development and web development services for exactly that stretch.

Ready to Integrate MCP Servers?

Start with mcptools to explore MCP server capabilities via CLI. Perfect for development, testing, and scripting. MIT-licensed and actively maintained.