YAMS (Yet Another MCP Server)
Click on "Deploy Server".
Wait a few minutes for the server to deploy. Once ready, it will show a "Started" state.
In the chat, type
@followed by the MCP server name and your instructions, e.g., "@YAMS (Yet Another MCP Server)search the web for the latest Python release notes"
That's it! The server will respond to your query, and you can continue using it as needed.
Here is a step-by-step guide with screenshots.
YAMS
Yet Another MCP Server
YAMS is a batteries-included MCP server that provides the common tools most coding agents need:
Web search
Fetching and parsing web pages
File system access
Shell command execution
Git integration
Basic utility tools
Built in Python. Run with uv.
No Electron. No Docker required. No enterprise platform. Just tools.
Why?
Every agent stack ends up rebuilding the same MCP tools:
search
fetch
grep
git
run commands
read/write files
YAMS packages the boring, standard functionality into a single MCP server that works well locally, in CI, or on remote hosts.
The goal is not to be clever.
The goal is to be useful.
Related MCP server: mcp-devtools
Features
Fast startup
Single-process architecture
Async Python implementation
Designed for local-first workflows
Works well with Claude Code-style agents
Easy to extend with custom tools
Sensible defaults
Minimal configuration
Installation
From GitHub
uv tool install git+https://github.com/carlosroman/yams.gitOr run without installing:
uvx --from git+https://github.com/carlosroman/yams.git yamsQuick Start
Start the server:
uvx yamsExample MCP client configuration:
{
"mcpServers": {
"yams": {
"command": "uvx",
"args": ["yams"]
}
}
}Included Tools
Planned tools (none implemented yet):
Tool | Description | Status |
| Search the web | ⏳ Planned |
| Fetch and parse web pages | ⏳ Planned |
| Execute shell commands | ⏳ Planned |
| Read files | ⏳ Planned |
| Write files | ⏳ Planned |
| Search project contents | ⏳ Planned |
| Git status | ⏳ Planned |
| Git diff | ⏳ Planned |
| Create commits | ⏳ Planned |
| List directories | ⏳ Planned |
More tools will be added over time.
Philosophy
YAMS follows a few simple rules:
Local-first
Your tools should work on your machine without requiring cloud infrastructure.
Unix-style
Small composable tools beat giant opaque systems.
Predictable over magical
Agents need reliable tooling more than “AI-native” abstractions.
Boring technology wins
Python. JSON. stdio. HTTP.
These things work.
Development
Clone the repository:
git clone https://github.com/your-org/yams.git
cd yamsInstall dependencies:
uv syncRun the server:
uv run yamsRun tests:
uv run pytestLint:
uv run ruff checkFormat:
uv run ruff formatProject Structure
yams/
├── pyproject.toml
├── src/yams/
│ ├── server.py
│ ├── tools/
│ ├── transport/
│ └── config/
├── tests/
└── README.mdRoadmap
Browser automation tools
Better sandboxing
Remote execution support
Tool permissions
Persistent sessions
Caching
Authentication support
Plugin system
Non-Goals
YAMS is not:
an agent framework
an orchestration platform
a workflow engine
a hosted service
an IDE replacement
It is just an MCP server.
Name
Yes, the name is recursive.
No, this probably didn't need to exist.
License
MIT
This server cannot be deployed
Maintenance
Related MCP Connectors
Nifty's MCP server — exposes tasks, projects, messages, and files as tools for AI agents.
Personal assistant MCP server with search, execute, packages, jobs, secrets, and integrations.
A comprehensive Model Context Protocol (MCP) server that enables AI assistants to interact with yo…
Agent-native MCP server over the public saagarpatel.dev corpus. Read-only, stateless.
Related MCP Servers
- AlicenseBqualityCmaintenanceA local-first MCP server that provides AI agents with safe codebase access through file discovery, hybrid lexical-semantic search, and project introspection. It features durable local memory and semantic indexing while keeping all data and processing entirely on your local machine.7447 npm6MIT
- AlicenseBqualityDmaintenanceProduction-grade MCP server that gives AI agents safe access to your local dev environment: filesystem, databases, processes, and OpenAPI specs.1528 npm3MIT
- FlicenseCqualityCmaintenanceA security-first MCP server that provides LLMs with structured tools for filesystem, process, search, build/test/lint, IDE integration, and more.402-
- AlicenseNot gradedqualityAmaintenanceLocal-first MCP server that provides project context, verification gates, and structured tools for coding agents to discover knowledge, run diagnostics, and execute allowlisted commands within a repository.24 npmMIT