Skip to main content
Glama
Traia-IO

Test MCP Feb4 MCP Server

by Traia-IO

Test MCP Feb4 MCP Server

This is an MCP (Model Context Protocol) server that provides access to the Test MCP Feb4 API. It enables AI agents and LLMs to interact with Test MCP Feb4 through standardized tools.

Features

  • 🔧 MCP Protocol: Built on the Model Context Protocol for seamless AI integration

  • 🌐 Full API Access: Provides tools for interacting with Test MCP Feb4 endpoints

  • 🐳 Docker Support: Easy deployment with Docker and Docker Compose

  • Async Operations: Built with FastMCP for efficient async handling

Related MCP server: Test MCP Feb 5 MCP Server

API Documentation

Available Tools

This server provides the following tools:

  • example_tool: Placeholder tool (to be implemented)

Note: Replace example_tool with actual Test MCP Feb4 API tools based on the documentation.

Installation

  1. Clone this repository:

    git clone https://github.com/Traia-IO/test-mcp-feb4-mcp-server.git
    cd test-mcp-feb4-mcp-server
  2. Run with Docker:

    ./run_local_docker.sh

Using Docker Compose

  1. Create a .env file with your configuration:

PORT=8000


2. Start the server:
```bash
docker-compose up

Manual Installation

  1. Install dependencies using uv:

    uv pip install -e .
  2. Run the server:

uv run python -m server


## Usage

### Health Check

Test if the server is running:
```bash
python mcp_health_check.py

Using with CrewAI

from traia_iatp.mcp.traia_mcp_adapter import create_mcp_adapter

# Connect to the MCP server
with create_mcp_adapter(
    url="http://localhost:8000/mcp/"
) as tools:
    # Use the tools
    for tool in tools:
        print(f"Available tool: {tool.name}")
        
    # Example usage
    result = await tool.example_tool(query="test")
    print(result)

Development

Testing the Server

  1. Start the server locally

  2. Run the health check: python mcp_health_check.py

  3. Test individual tools using the CrewAI adapter

Adding New Tools

To add new tools, edit server.py and:

  1. Create API client functions for Test MCP Feb4 endpoints

  2. Add @mcp.tool() decorated functions

  3. Update this README with the new tools

  4. Update deployment_params.json with the tool names in the capabilities array

Deployment

Deployment Configuration

The deployment_params.json file contains the deployment configuration for this MCP server:

{
  "github_url": "https://github.com/Traia-IO/test-mcp-feb4-mcp-server",
  "mcp_server": {
    "name": "test-mcp-feb4-mcp",
    "description": "Test mcp feb4",
    "server_type": "streamable-http",
"capabilities": [
      // List all implemented tool names here
      "example_tool"
    ]
  },
  "deployment_method": "cloud_run",
  "gcp_project_id": "traia-mcp-servers",
  "gcp_region": "us-central1",
  "tags": ["test mcp feb4", "api"],
  "ref": "main"
}

Important: Always update the capabilities array when you add or remove tools!

Google Cloud Run

This server is designed to be deployed on Google Cloud Run. The deployment will:

  1. Build a container from the Dockerfile

  2. Deploy to Cloud Run with the specified configuration

  3. Expose the /mcp endpoint for client connections

Environment Variables

  • PORT: Server port (default: 8000)

  • STAGE: Environment stage (default: MAINNET, options: MAINNET, TESTNET)

  • LOG_LEVEL: Logging level (default: INFO)

Troubleshooting

  1. Server not starting: Check Docker logs with docker logs <container-id>

  2. Connection errors: Ensure the server is running on the expected port3. Tool errors: Check the server logs for detailed error messages

Contributing

  1. Fork the repository

  2. Create a feature branch

  3. Implement new tools or improvements

  4. Update the README and deployment_params.json

  5. Submit a pull request

License

MIT License

Maintenance

ActivityInactive
ResponsivenessNo issues

Related MCP Connectors

  • MCP server for building and testing AI agents with multi-model experimentation and insights.

  • The Mercado Pago MCP Server implements the Model Context Protocol to provide AI agents and LLMs with access to Mercado Pago's APIs and tools within compatible development environments. It acts as an intermediary that translates Mercado Pago resources into executable functions (tools) that AI applications can invoke to perform actions and automate flows. The server simplifies integration, enables using documentation to implement or improve code, and optimizes operations through natural language interactions without manual implementations.

  • MCP server exposing the Backtest360 engine API as tools for AI agents.

  • The Remote MCP server acts as a standardized bridge between LLM applications (like Claude, ChatGPT, and Cursor) and external services, enabling AI agents to access external tools and resources. Its primary capability is providing a centralized search tool to discover other MCP servers and their respective tools. Unlike local implementations, it runs remotely with OAuth authentication and permission controls for security.

Related MCP Servers

  • A
    license
    A
    quality
    D
    maintenance
    A Model Context Protocol server that enables AI assistants to make HTTP requests (GET, POST, PUT, DELETE) to external APIs through standardized MCP tools.
    4
    2
    MIT
  • F
    license
    Not graded
    quality
    D
    maintenance
    An MCP server that provides access to the Test MCP Feb 5 API, enabling AI agents to interact with its endpoints through standardized tools. It supports seamless AI integration via the Model Context Protocol and is designed for easy deployment using Docker or Google Cloud Run.
    -
  • F
    license
    Not graded
    quality
    D
    maintenance
    An MCP server that enables AI agents and LLMs to interact with the Test MCP Server Feb6 USDT API through standardized tools. It provides features such as Docker support and async operations for efficient integration.
    -
  • F
    license
    Not graded
    quality
    D
    maintenance
    This MCP server provides access to the Test mcp server Traia API, enabling AI agents and LLMs to interact with its endpoints through standardized tools. It features asynchronous operation handling and simple deployment options via Docker for efficient integration.
    -