How do I use Python MCP Server?

1. Click on "Deploy Server". 2. Wait a few minutes for the server to deploy. Once ready, it will show a "Started" state. 3. In the chat, type @ followed by the MCP server name and your instructions, e.g., "@Python MCP Server add 15 and 27 for me" 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.

Python MCP Server

by Yoshua-Carrera

Overview Schema Source Related Servers Discussions Admin

Python

Local

Python MCP Server

This is a simple demonstration of a fastmcp server and client.

Setup and Installation (with uv)

This project uses uv for environment and dependency management.

Create the virtual environment:
```
uv venv
```
Activate the virtual environment:
```
source .venv/bin/activate
```
Install the dependencies:
```
uv pip sync pyproject.toml
```

Related MCP server: Fast MCP Local

Usage (with uv)

Make sure your virtual environment is activated before running these commands.

Run the MCP server:
```
uv run python server.py
```
The server will start on localhost:8000.

Usage for gemini

Configue Gemini CLI Add the following configuration on ~/.gemini/settings.json

{
  "security": {
    "auth": {
      "selectedType": "oauth-personal"
    }
  },
  "mcpServers": {
    "serverName": {
      "command": "/home/<USER>/.local/bin/uv",
      "args": [
        "--directory",
        "/home/<USER>/code/python-mcp-server",
        "run",
        "server.py"
      ]
    }
  }
}

And yes, the home directory can't be summarized to just "~"

Th server does not need to be running simply run Gemini CLI:
```
gemini
```
From there, you will be able to know if the MCP has been adopted by running the command /mcp list. You should see the tools listed there, similar to this:
```
ℹConfigured MCP servers:

  🟢 serverName - Ready (2 tools)
    Tools:
    - addNumbers
    - greet


  💡 Tips:
    • Use /mcp desc to show server and tool descriptions
    • Use /mcp schema to show tool parameter schemas
    • Use /mcp nodesc to hide descriptions
    • Use /mcp auth <server-name> to authenticate with OAuth-enabled servers
    • Press Ctrl+T to toggle tool descriptions on/off
```
In this example you will be able to ask Gemini to greet you or add numbers, as long as you provide enough context to fill in the arguments. If you do not provide arguments, Gemini will ask for more information.
Once all the arguments are provided, Gemini will ask for confirmation before the MCP is hit, and only then will it execute the logic.

Available Tools

2 tools

addNumbersD

ParametersJSON Schema

Name	Required	Description	Default
`a`	Yes
`b`	Yes

Output Schema

ParametersJSON Schema

Name	Required	Description
`result`	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.

greetD

ParametersJSON Schema

Name	Required	Description	Default
`name`	Yes

Output Schema

ParametersJSON Schema

Name	Required	Description
`result`	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.

2 tool updatesOct 3, 2025
- First observedaddNumbers
- First observedgreet

Deploy Server

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

TDQS

D1.5/5.0

Scored 2026-04-18 08:30 across 2 tools

Disambiguation5/5

The two tools have clearly distinct purposes: addNumbers performs a mathematical operation, while greet handles a social interaction. There is no overlap or ambiguity between them, making misselection unlikely.

Naming Consistency2/5

The naming is inconsistent: addNumbers uses camelCase, while greet uses lowercase. There is no predictable pattern across the set, though both names are readable individually.

Tool Count2/5

With only 2 tools, the server feels thin and under-scoped for a general-purpose Python MCP server. This minimal set suggests limited functionality that may not cover typical Python-related tasks.

Completeness1/5

The tool surface is severely incomplete for a Python server domain. It lacks basic operations like code execution, file handling, or library management, leaving obvious gaps that will cause agent failures in practical scenarios.

Maintenance

ActivityInactive

ResponsivenessNo issues

Resources

GitHub Repository

Need Help?

Related Servers

Related MCP Connectors

mcp-aichatOAuth
io.github.AceDataCloud
MCP server for AI dialogue using various LLM models via AceDataCloud
AI & Machine Learning
2
staging-mcpOAuth
dev.riskprofiler
An MCP server that provides a hello tool
Developer Tools
1
test-mcp B
dev.riskprofiler
An MCP server that provides a hello tool
Developer Tools
11
mcp-glmOAuth
io.github.AceDataCloud
MCP server for GLM chat completions using Zhipu AI models via AceDataCloud
AI & Machine Learning Developer Tools
2

Related MCP Servers

Greeter MCP Server
Developer Tools Code Execution
jrmlhermitte
A
license
D
quality
D
maintenance
A simple demonstration MCP server that provides a greeting functionality when integrated with Gemini CLI.
Updated a year ago (2025-07-14 17:38 UTC)
1
MIT
Fast MCP Local
Developer Tools
karthik78180
A
license
Not graded
quality
D
maintenance
A minimal FastMCP server implementation that provides basic mathematical and greeting tools. Enables users to perform simple operations like adding numbers and greeting people by name through a lightweight MCP interface.
Updated a year ago (2025-10-15 21:53 UTC)
MIT
FastAPI MCP Demo Server
Developer Tools
MAIMOONA-ISLAM
F
license
Not graded
quality
D
maintenance
A demonstration MCP server built with FastAPI that provides basic mathematical operations and greeting services. Integrates with Gemini CLI to showcase MCP protocol implementation with simple REST endpoints.
Updated a year ago (2025-10-28 06:58 UTC)
-
Simple FastMCP Server
Developer Tools
zongjieshen
F
license
Not graded
quality
D
maintenance
A minimal demonstration MCP server that provides basic mathematical addition and greeting functionality, serving as a template for building and deploying FastMCP servers.
Updated 10 months ago (2025-11-09 23:42 UTC)
-

Python MCP Server

Setup and Installation (with uv)

Usage (with uv)

Usage for gemini

Available Tools

Output Schema

TDQS

Output Schema

TDQS

Tool Schema Changelog

TDQS

Maintenance

Resources

Related MCP Connectors

Related MCP Servers

Greeter MCP Server

Fast MCP Local

FastAPI MCP Demo Server

Simple FastMCP Server