ai-mcp
Click on "Install 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., "@ai-mcpWhat is your computer's OS?"
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.
ai-mcp
Lightweight MCP server for agent, register tools.
Overview
This project creates minimal MCP services that expose small tools (examples: system info, weather lookup) and run them via standard input/output. It is intended as a reference for wiring functions into MCP FastMCP instances.
Related MCP server: mon-serveur-mcp
Files
system_information_mcp.py— implement system information MCP and register toolget_system_info.weather_mcp.py— implement weather MCP and register tools to get weather info using the U.S. National Weather Service API.pyproject.toml— project metadata and dependencies..python-version— recommended Python version (3.12).
Requirements
Python 3.12
Recommended: use a virtual environment
Configuration agent
Configure MCP server in Cline
"system information mcp": {
"disabled": false,
"timeout": 60,
"type": "stdio",
"command": "uv",
"args": [
"--directory",
"D:/YJWANG/workspace/code/ai/ai-mcp",
"run",
"system_information_mcp.py"
]
},
"weather mcp": {
"disabled": false,
"timeout": 60,
"type": "stdio",
"command": "uv",
"args": [
"--directory",
"D:/YJWANG/workspace/code/ai/ai-mcp",
"run",
"weather_mcp.py"
]
}You should change the path according to your envrionment.
Run
System info MCP:
uv run system_information_mcp.pyWeather MCP (weather_mcp.py):
uv run weather_mcp.pyEach script creates a FastMCP instance, registers one or more tools, and runs in stdio mode. Use your MCP-compatible client or protocol over stdio to call the registered tools.
Then, you can ask questions in agent, such as Cline
How about tomorrow weather in Regina, SKWhat is your computer's OS?Available Tools
1 toolget_system_infoA
Retrieve system information including OS, CPU, and memory details. Returns: dict[str, str]: A dictionary containing system information.
| Name | Required | Description | Default |
|---|---|---|---|
No parameters | |||
Output Schema
| Name | Required | Description |
|---|---|---|
| result | Yes |
TDQS
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
No annotations provided, so the description carries the full burden. It states 'Retrieve' implying a read-only operation, but does not disclose other behavioral traits such as authorization needs, rate limits, or data freshness. For a simple retrieval tool, it is passable but not transparent.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
The description is two sentences: one stating the purpose, one detailing the return type. No unnecessary words, front-loaded with the action, and efficiently structured.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
Given zero parameters and an output schema that exists (though not shown), the description adds value by stating the return type (dict[str, str]). It is adequately complete for a simple info tool, though it could mention potential errors or data freshness.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
The tool has zero parameters, and schema coverage is 100% (no params). The baseline for 0 parameters is 4. The description does not need to add parameter info, so it meets the baseline.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
The description clearly states 'Retrieve system information including OS, CPU, and memory details.' It uses a specific verb ('Retrieve') and resource ('system information'), and lists key components. With no sibling tools, differentiation is not needed.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
No guidance on when to use this tool or any prerequisites. While the purpose is straightforward, the description lacks explicit usage context or alternatives, so it's merely adequate.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
TDQS
Only one tool exists, so there is no possibility of confusion with other tools.
The single tool uses a clear verb_noun pattern (get_system_info), which is consistent and self-explanatory.
While one tool is minimal, it is appropriate for the narrow scope of retrieving system information; however, the server could benefit from additional related tools to be more useful.
For the stated purpose of providing system information, the tool covers OS, CPU, and memory details comprehensively with no obvious gaps.
Maintenance
Resources
Unclaimed servers have limited discoverability.
Looking for Admin?
If you are the server author, to access and configure the admin panel.
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.
Hosted MCP server for live public-data APIs and Skills for AI agents.
MCP server exposing the Backtest360 engine API as tools for AI agents.
Related MCP Servers
- FlicenseBqualityDmaintenanceA simple MCP server that provides a tool to fetch current weather information for cities using the Open-Meteo API, communicating through stdin/stdout.12-
- FlicenseNot gradedqualityDmaintenanceExposes system tools (disk usage, file listing) and weather information via Open-Meteo to MCP-compatible LLMs.-
- FlicenseNot gradedqualityDmaintenanceMCP server providing tools to chat with an AI agent, fetch weather data, and monitor agent status via the Model Context Protocol.-
- FlicenseAqualityCmaintenanceA minimal MCP server that exposes a single tool to query local hardware information (OS, CPU, memory, architecture).1-
Latest Blog Posts
- Who's Calling? MCP Hosts Are an Identity Blind Spot (And the Spec Knows It)By Om-Shree-0709 on .mcpAgent IdentityOAuth 2.1
- Your AI Chatbot Just Exposed Your CEO's Salary to an InternBy Om-Shree-0709 on .Agent IdentityMCP SecurityOAuth Delegation
- Why MCP Servers Need Execution Sandboxing (And Why Your Current Stack Isn't Enough)By Om-Shree-0709 on .Agentic AiPrompt InjectionWebAssembly
MCP directory API
We provide all the information about MCP servers via our MCP API.
curl -X GET 'https://glama.ai/api/mcp/v1/servers/wangyj641/ai-mcp'
If you have feedback or need assistance with the MCP directory API, please join our Discord server