Skip to main content
Glama
Omkar4141

Test MCP Server

by Omkar4141
OverviewSchemaRelated ServersScoreDiscussions
Python
Hybrid

test_mcp_server

A simple MCP (Model Context Protocol) server project demonstrating both local and remote MCP server setups using FastMCP, LangChain, and uv.

Requirements

  • Python 3.9+

  • pip

  • uv

Related MCP server: MCP Server Example

First-Time Setup

1. Install uv

pip install uv

2. Navigate to the project directory

cd test_mcp_server

3. Initialize the project with uv

uv init .

4. Add FastMCP

uv add fastmcp

Local MCP Server Setup

1. Create the local server file

Create a file named:

local_server.py

This file contains your MCP server implementation.

2. Add required dependencies

uv add langchain langchain-openai langchain_mcp_adapters

3. Create the client

Create a client file:

client.py

4. Run the local server using STDIO

The local MCP server communicates via STDIO.

Run the client:

uv run client.py

Remote MCP Server Setup

1. Create MCP tools

  • Define your MCP tools for the remote server

  • Ensure they are compatible with FastMCP Cloud

2. Deploy to FastMCP Cloud

  • Deploy the server to FastMCP Cloud

  • Obtain the remote server configuration

3. Update configuration

  • Add the remote MCP server configuration to your config file

  • Replace the local STDIO setup with the remote server endpoint

4. Run the client with the remote server

uv run client.py

Notes

  • Local server uses STDIO for communication

  • Remote server runs on FastMCP Cloud

  • uv handles dependency management and execution

  • Same client can be used for both local and remote servers by changing configuration

Remote MCP Server Deployment (FastMCP Cloud)

GitHub Access

  • GitHub repository access was granted to FastMCP Cloud

  • FastMCP Cloud pulls the source code directly from the repository

Deployment Steps

  1. Created MCP tools for the remote server

  2. Connected the GitHub repository to FastMCP Cloud

  3. FastMCP Cloud executed the server using:

main.py

  1. The server was successfully deployed as a remote MCP server

Client Configuration

  • Updated the MCP configuration file to point to the remote FastMCP Cloud endpoint

  • Reused the same client.py for both local and remote execution

Running the Client

uv run client.py

Available Tools

2 tools
addD
ParametersJSON Schema
NameRequiredDescriptionDefault
aYes
bYes

Output Schema

ParametersJSON Schema
NameRequiredDescription
resultYes

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.

subD
ParametersJSON Schema
NameRequiredDescriptionDefault
aYes
bYes

Output Schema

ParametersJSON Schema
NameRequiredDescription
resultYes

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. Dates show when Glama detected each change.

  1. 2 tool updatesv0.1.0
    • First observedadd
    • First observedsub
Install Server
RayrunBuild, deploy, and operate MCP servers without becoming an infrastructure team.ray.runAd

TDQS

D1.7/5.0
Disambiguation5/5

The two tools have clearly distinct purposes: 'add' for addition and 'sub' for subtraction. With only two basic arithmetic operations, there is no ambiguity or overlap in functionality.

Naming Consistency5/5

Both tool names follow a consistent pattern: short, lowercase verbs representing mathematical operations. There are no deviations in style or convention across the set.

Tool Count2/5

With only two tools, the server feels thin and under-scoped for a general-purpose 'Test MCP Server'. This minimal set lacks coverage for even basic arithmetic operations like multiplication or division, making it inadequate for typical testing or utility purposes.

Completeness1/5

The tool surface is severely incomplete for a test server domain. It only covers addition and subtraction, missing fundamental operations like multiplication, division, and other common functions, which will cause agent failures in most testing scenarios.

Maintenance

ActivityInactive
ResponsivenessSyncing

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

Related MCP Servers

  • MCP Server Example

    sakthigcp
    F
    license
    B
    quality
    D
    maintenance
    A simple example MCP server that demonstrates basic server functionality and can be easily run using uv package manager. Provides a minimal implementation for learning and development purposes.
    1
    -

  • My Awesome MCP

    elliotnorrevik
    -
    license
    Not graded
    quality
    Not graded
    maintenance
    A basic MCP server built with FastMCP framework that provides example tools including message echoing and server information retrieval. Supports both stdio and HTTP transports with Docker deployment capabilities.
    -

  • DDG MCP Server

    elliotnorrevik
    -
    license
    Not graded
    quality
    Not graded
    maintenance
    A basic MCP server built with FastMCP framework that provides example tools including message echoing and server information retrieval. Supports both stdio and HTTP transports with Docker deployment capabilities.
    -

Latest Blog Posts

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/Omkar4141/test_mcp_server'

If you have feedback or need assistance with the MCP directory API, please join our Discord server