de en es ja ko ru zh

Python MCP Server Template

Name: Python MCP Server Template
Author: nictuku

by nictuku

Overview Schema Source Related Servers Discussions Admin

Python

py-mcp-服务器模板

此代码库是一个模板，可帮助您使用 Python 创建自己的 MCP（模型上下文协议）服务器。您可以 fork 此代码库来开始使用。

使用 uv 设置

本项目使用uv进行 Python 打包和管理虚拟环境。如果您尚未安装uv ，请参阅官方 uv 安装指南。

克隆你的分支存储库：

git clone https://github.com/YOUR_USERNAME/YOUR_REPOSITORY_NAME.git
cd YOUR_REPOSITORY_NAME

创建并激活虚拟环境： uv通常会在项目根目录中创建一个.venv目录。

uv venv
source .venv/bin/activate  # On macOS/Linux
# .venv\Scripts\activate   # On Windows

**安装依赖项：**本项目使用pyproject.toml来管理依赖项。
```
uv pip install .
```
如果添加了新的依赖项，请在pyproject.toml文件中定义它们，然后再次运行此命令。如果出于某种原因使用了requirements.txt文件，可以使用uv pip install -r requirements.txt进行安装。

Related MCP server: mcp-framework-starter

运行服务器

mcp_server.py脚本启动 MCP 服务器。

直接运行服务器：

uv run python mcp_server.py

与 Claude Desktop 或 Cursor 集成

要将此 MCP 服务器与 Claude Desktop 或 Cursor 等应用程序一起使用，您需要在应用程序的设置中进行配置。配置通常涉及指定运行服务器的命令。

以下是一个示例配置片段。您需要将/ABSOLUTE/PATH/TO/PARENT/FOLDER/YOUR_REPOSITORY_NAME替换为您系统上项目目录的实际绝对路径。

{
    "mcpServers": {
        "my-custom-python-server": {
            "command": "uv",
            "args": [
                "run",
                "--python",
                "/ABSOLUTE/PATH/TO/PARENT/FOLDER/YOUR_REPOSITORY_NAME/.venv/bin/python",
                "/ABSOLUTE/PATH/TO/PARENT/FOLDER/YOUR_REPOSITORY_NAME/mcp_server.py"
            ],
            "workingDirectory": "/ABSOLUTE/PATH/TO/PARENT/FOLDER/YOUR_REPOSITORY_NAME"
        }
    }
}

配置说明：

"my-custom-python-server" ：这是您为服务器配置指定的名称。
"command": "uv" ：指定uv作为要执行的命令。
"args" ： uv命令的参数列表：
- "run" ：告诉uv在其管理环境中执行命令。
- "--python" ：指定要使用的 Python 解释器。务必将其指向uv虚拟环境 ( .venv/bin/python ) 中的 Python 解释器。
- "/ABSOLUTE/PATH/TO/PARENT/FOLDER/YOUR_REPOSITORY_NAME/mcp_server.py" ：服务器脚本的绝对路径。
"workingDirectory" ：指定服务器进程的工作目录，该目录应该是项目的根目录。

重要的：

确保args和workingDirectory中的路径对于您的系统来说是正确的。
如果应用程序找不到uv ，您可能需要在"command"字段中指定其完整路径。通常，您可以在 macOS 或 Linux 的终端中运行which uv来找到此路径，或者在 Windows 上where uv来找到此路径。
按照mcp_server.py ( mcp.run(transport='stdio') ) 中的配置，服务器默认在stdio上监听，这通常是 Cursor 等应用程序所期望的。

配置完成后，应用程序应该能够与您的 Python MCP 服务器通信。

Available Tools

3 tools

get_jokeD

ParametersJSON Schema

Name	Required	Description	Default
No parameters

TDQS

D1/5.0

Behavior1/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

Tool has no description.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness1/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Tool has no description.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness1/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Tool has no description.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters1/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Tool has no description.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose1/5

Does the description clearly state what the tool does and how it differs from similar tools?

Tool has no description.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines1/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Tool has no description.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

get_pingD

ParametersJSON Schema

Name	Required	Description	Default
`message`	Yes

TDQS

D1/5.0

Behavior1/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

Tool has no description.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness1/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Tool has no description.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness1/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Tool has no description.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters1/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Tool has no description.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose1/5

Does the description clearly state what the tool does and how it differs from similar tools?

Tool has no description.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines1/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Tool has no description.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

get_weatherD

ParametersJSON Schema

Name	Required	Description	Default
`city`	Yes

TDQS

D1/5.0

Behavior1/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

Tool has no description.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness1/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Tool has no description.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness1/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Tool has no description.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters1/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Tool has no description.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose1/5

Does the description clearly state what the tool does and how it differs from similar tools?

Tool has no description.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines1/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Tool has no description.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Tool Schema Changelog

Recent tool additions, removals, and schema changes observed during successful MCP inspections.

3 tool updatesAug 18, 2025
- First observedget_joke
- First observedget_ping
- First observedget_weather

Deploy Server

Shareable, User-Owned Context BackendPeople, applications, and agents read, write, and coordinate together in one context lake. Reach it over MCP, a CLI, a Python SDK, or REST.fulcradynamics.comAd

TDQS

D1.8/5.0

Scored 2026-04-18 10:06 across 3 tools

Disambiguation5/5

Each tool has a clearly distinct purpose: get_joke retrieves jokes, get_ping checks server status, and get_weather fetches weather data. There is no overlap in functionality, making it easy for an agent to select the correct tool without confusion.

Naming Consistency5/5

All tool names follow a consistent verb_noun pattern with 'get_' as the prefix, using snake_case throughout. This predictable naming scheme enhances readability and usability for agents.

Tool Count3/5

With only 3 tools, the server feels thin for a general-purpose template, as it lacks depth in any specific domain. While the count is not extreme, it may be insufficient for complex workflows, though it's reasonable for a basic example.

Completeness2/5

The tool set is severely incomplete for a Python MCP server template, as it only includes three unrelated, trivial functions without covering any meaningful domain or lifecycle operations. There are significant gaps that would hinder agent performance in practical scenarios.

Maintenance

ActivityInactive

ResponsivenessNo issues

Resources

GitHub Repository

Need Help?

Related Servers

Related MCP Connectors

hithereiamaliff-mcp-nextcloudOAuth
ai.smithery
A comprehensive Model Context Protocol (MCP) server that enables AI assistants to interact with yo…
Cloud Storage File Systems Workplace & Productivity
238
mcp COAuth
com.wix
A Model Context Protocol server for Wix AI tools
Developer Tools Content Management Systems App Automation
215
anirbanbasu-pymcpOAuth
ai.smithery
Primarily to be used as a template repository for developing MCP servers with FastMCP in Python, P…
Developer Tools
28
Apideck MCP A
dev.apideck.mcp
Model Context Protocol server for the Apideck Unified API. Connect any MCP-compatible agent framework to 100+ accounting systems, HRIS platforms, file storage providers, and more through one integration. More information https://www.apideck.com/mcp-server
Developer Tools
42

Related MCP Servers

MCP Server Template
Developer Tools Agent Orchestration App Automation
hypermodel-labs
A
license
C
quality
D
maintenance
A starter template for building Model Context Protocol servers that can be integrated with Cursor or Claude Desktop, allowing developers to create custom tools and extensions for AI assistants.
Updated a year ago (2025-05-04 22:47 UTC)
1
10 npm
14
MIT
mcp-framework-starter
Developer Tools App Automation
QuantGeekDev
F
license
Not graded
quality
D
maintenance
A starter template for building Model Context Protocol (MCP) servers, enabling developers to create and add custom tools that can be integrated with Claude Desktop.
Updated 2 years ago (2025-04-01 01:26 UTC)
2
-
MCP Server Boilerplate
CaptainCrouton89
F
license
C
quality
D
maintenance
A starter template for building Model Context Protocol servers that integrate with AI assistants like Claude and Cursor, providing custom tools, resource providers, and prompt templates.
Updated a year ago (2025-07-21 00:05 UTC)
2
5 npm
-
MCP Server Boilerplate
CaptainCrouton89
F
license
C
quality
D
maintenance
A starter template for building Model Context Protocol servers that integrate with AI assistants like Claude and Cursor, providing custom tools, resource providers, and prompt templates.
Updated a year ago (2025-07-21 01:49 UTC)
2
5 npm
-