JEdward7777/translation_helps_mcp_proxy

DEPRICATED: This project was rewritten with more features in TypeScript. Subsequently the upstream data source changed formats requiring a rewrite of the TypeScript version. This Python version of the library will no longer work because of the upstream changes and is thus depricated.

WARNING: This project was vibe coded and there are a minimal number of MCP commands which have actually been completed. Do not be fooled by the overly optimistic automatic documentation. The development methodology is to pick a specific command that needs to be implemented and get the agent to write a test which verifies that it is failing, and then push it until it no longer fails. This has been done with the MCP command fetch_translation_notes. There are a couple other commands which do work, but most do not until this process is repeated on them.

Translation Helps MCP Proxy

A Python stdio MCP server that bridges MCP clients with the translation-helps-mcp server. This proxy handles JSON-RPC 2.0 formatting and protocol translation to make the upstream HTTP server fully compatible with MCP clients.

📚 Upstream Project

This project is a wrapper around the translation-helps-mcp project, providing MCP (Model Context Protocol) compatibility for the upstream HTTP API.

Upstream Details:

• Repository: https://github.com/klappy/translation-helps-mcp
• Live Demo: https://translation-helps-mcp.pages.dev/
• Description: "The Aqueduct - Stateless RAG High-performance API platform providing instant access to unfoldingWord translation resources with word-level alignment precision for Mother Tongue Translators worldwide."

🎯 Current Status

✅ PRODUCTION READY - All functionality working as of October 2025

• MCP Initialization: ✅ Proper JSON-RPC 2.0 handshake
• Tool Discovery: ✅ Discovers all 12 tools from upstream server
• Tool Execution: ✅ Successfully executes all tools including fetch_scripture
• Stdio Protocol: ✅ Complete MCP stdio workflow operational
• Error Handling: ✅ Graceful error handling and cleanup

Test Results: 37/37 comprehensive tests passing (100% operational)

🔧 Technical Architecture

Protocol Flow

MCP Client ←→ Proxy Server ←→ Upstream Server
(stdio)        (stdio)         (HTTP)
JSON-RPC 2.0   JSON-RPC 2.0    API endpoints

Key Features

• Protocol Translation: Converts between MCP stdio and HTTP API calls
• Response Formatting: Handles various upstream response formats (MCP content, scripture data, wrapped results)
• Smart Routing: Routes fetch_scripture calls to dedicated /api/fetch-scripture endpoint
• Error Recovery: Robust async error handling and resource cleanup

📁 Project Structure

translation_helps_mcp_proxy/
├── src/
│   └── translation_helps_mcp_proxy/
│       ├── __init__.py           # Package initialization
│       ├── __main__.py           # Main entry point
│       └── mcp_proxy_server.py   # Main proxy server
├── tests/                        # Comprehensive pytest test suite (37 tests)
│   ├── __init__.py              # Package initialization
│   ├── conftest.py              # Shared test fixtures
│   ├── test_upstream_connectivity.py  # Upstream connection tests
│   ├── test_mcp_protocol.py           # MCP protocol tests
│   ├── test_tool_execution.py         # Tool execution tests
│   ├── test_stdio_workflow.py         # End-to-end workflow tests
│   ├── test_fetch_translation_notes.py # Translation notes tool tests
│   ├── test_get_translation_word.py    # Translation word tool tests
│   ├── test_tool_filtering.py          # Tool filtering tests
│   └── test_strict_translation_notes.py # Strict translation notes tests
├── pyproject.toml            # Python package configuration (uvx compatible)
├── pytest.ini               # Pytest configuration
├── requirements.txt          # Python dependencies (includes pytest)
├── setup.sh / setup.bat      # Cross-platform setup scripts
├── README.md                 # This file
├── CORRECT_mcp_config.json   # Example MCP client configuration
└── .gitignore               # Git ignore rules

⚡ Quick Start

Using uvx (Recommended - Zero Installation)

# Install and run with uvx (no local setup needed)
uvx git+https://github.com/JEdward7777/translation_helps_mcp_proxy.git

# Or install globally for repeated use
uvx install git+https://github.com/JEdward7777/translation_helps_mcp_proxy.git
translation-helps-mcp-proxy

# With custom options
uvx git+https://github.com/JEdward7777/translation_helps_mcp_proxy.git \
  --debug \
  --enabled-tools "fetch_scripture,fetch_translation_notes,get_system_prompt"

# Hide problematic parameters from downstream tools
uvx git+https://github.com/JEdward7777/translation_helps_mcp_proxy.git \
  --hide-params "language,organization"

# List available tools
uvx git+https://github.com/JEdward7777/translation_helps_mcp_proxy.git --list-tools

uvx Benefits:

• ⚡ Zero setup - No Python environment management needed
• 🔄 Always latest - Automatically pulls latest version from git
• 🧹 Clean - No local dependencies or virtual environments
• 🚀 Fast - uvx handles all dependency management automatically

Using uv sync (Alternative to pip)

If you prefer using uv for dependency management instead of pip:

# Clone the repository
git clone https://github.com/JEdward7777/translation_helps_mcp_proxy.git
cd translation_helps_mcp_proxy

# Sync dependencies using uv (creates .venv automatically)
uv sync

# Activate the virtual environment
. .venv/bin/activate  # Linux/macOS
# or
.venv\Scripts\activate  # Windows

# Test the package
python -m src.translation_helps_mcp_proxy --help

# Run tests
pytest

uv sync Benefits:

• 🚀 Faster - Much faster dependency resolution and installation
• 🔒 Locked - Uses uv.lock file for reproducible builds
• 📦 Unified - Single tool for all dependency management
• 🎯 Dev dependencies - Automatically installs dev dependencies from [dependency-groups]

Note: The uv sync command reads from and creates/updates the virtual environment with all required dependencies, including development dependencies like pytest.

Local Development Setup

# Clone the repository
git clone https://github.com/JEdward7777/translation_helps_mcp_proxy.git
cd translation_helps_mcp_proxy

# Linux/macOS
./setup.sh

# Windows
setup.bat

# Or manual setup
python3 -m venv venv
. venv/bin/activate  # Linux/macOS (note: use dot, not 'source')
pip install -r requirements.txt

# Test the package
python -m src.translation_helps_mcp_proxy --help

# Run tests
pytest

Important: Always activate the virtual environment before running any commands when developing locally. Use . venv/bin/activate (with dot) if source command is not available.

🧪 Testing

Modern pytest Test Suite (Recommended)

Run all tests:

# Activate venv first (REQUIRED)
. venv/bin/activate  # Use dot if 'source' doesn't work

# Run all tests
pytest

# Run with verbose output
pytest -v

# Run specific test files
pytest tests/test_upstream_connectivity.py
pytest tests/test_tool_execution.py
pytest tests/test_fetch_translation_notes.py
pytest tests/test_get_translation_word.py
pytest tests/test_tool_filtering.py

# Run specific test functions
pytest tests/test_stdio_workflow.py::test_stdio_workflow
pytest tests/test_fetch_translation_notes.py::test_fetch_translation_notes_basic
pytest tests/test_get_translation_word.py::test_get_translation_word_basic
pytest tests/test_tool_filtering.py::test_tool_filtering_specific_tools

# Run tests in parallel (faster)
pytest -n auto

# Run comprehensive test suite (all tests)
pytest tests/ -v

# Run all tool-specific tests
pytest tests/test_fetch_translation_notes.py tests/test_get_translation_word.py tests/test_tool_filtering.py tests/test_parameter_hiding.py -v

🧪 Comprehensive Test Suite

Total Test Coverage: 43 test cases across 7 test files

# Run all tests with detailed output
. .venv/bin/activate
pytest tests/ -v

# Expected output summary:
# tests/test_upstream_connectivity.py: 2 tests ✅
# tests/test_mcp_protocol.py: 2 tests ✅
# tests/test_tool_execution.py: 4 tests ✅
# tests/test_stdio_workflow.py: 2 tests ✅
# tests/test_fetch_translation_notes.py: 7 tests ✅
# tests/test_get_translation_word.py: 9 tests ✅
# tests/test_tool_filtering.py: 9 tests ✅
# tests/test_parameter_hiding.py: 6 tests ✅
# tests/test_strict_translation_notes.py: 2 tests ✅
# = 43 tests total

Test Categories:

• Core Infrastructure (8 tests) - Protocol, connectivity, basic tool execution
• Translation Notes (9 tests) - Complete fetch_translation_notes validation + strict tests
• Translation Words (9 tests) - Complete get_translation_word validation
• Tool Filtering (9 tests) - Safety controls and rollout management
• Parameter Hiding (6 tests) - Parameter filtering for downstream compatibility
• Upstream Connectivity (2 tests) - Connection and tool discovery validation

Simple Test Execution

# Just run pytest - discovers and runs all 37 tests automatically
. venv/bin/activate
pytest

Test Coverage:

1. Upstream Connectivity ✅ - Verifies connection and tool discovery
2. MCP Protocol ✅ - Tests JSON-RPC 2.0 initialization
3. Tool Execution ✅ - Validates tool calls including fetch_scripture
4. Stdio MCP Workflow ✅ - Complete end-to-end John 3:16 test
5. Translation Notes ✅ - Tests fetch_translation_notes tool (7 test cases)
6. Translation Words ✅ - Tests get_translation_word tool (9 test cases)

pytest Expected Output:

========================= test session starts =========================
collected 16 items

tests/test_upstream_connectivity.py::test_upstream_connectivity PASSED
tests/test_upstream_connectivity.py::test_tools_list_format PASSED
tests/test_mcp_protocol.py::test_mcp_protocol_initialization PASSED
tests/test_mcp_protocol.py::test_mcp_response_format PASSED
tests/test_tool_execution.py::test_tool_execution PASSED
tests/test_tool_execution.py::test_get_system_prompt_tool PASSED
tests/test_tool_execution.py::test_fetch_scripture_tool PASSED
tests/test_stdio_workflow.py::test_stdio_workflow PASSED
tests/test_fetch_translation_notes.py::test_fetch_translation_notes_basic PASSED
tests/test_fetch_translation_notes.py::test_fetch_translation_notes_missing_reference PASSED
tests/test_fetch_translation_notes.py::test_fetch_translation_notes_different_book PASSED
tests/test_fetch_translation_notes.py::test_fetch_translation_notes_default_params PASSED
tests/test_fetch_translation_notes.py::test_fetch_translation_notes_invalid_reference PASSED
tests/test_fetch_translation_notes.py::test_fetch_translation_notes_response_structure PASSED
tests/test_fetch_translation_notes.py::test_fetch_translation_notes_tool_integration PASSED
tests/test_get_translation_word.py::test_get_translation_word_basic PASSED

========================= 16 passed in X.XXs =========================

pytest Benefits

• Individual Test Execution: Run specific tests for focused debugging
• Parallel Execution: Faster test runs with -n auto
• Better Output: Cleaner, more detailed test reports
• Context Efficiency: Individual test files are 40-160 lines vs 418 lines

🚀 Usage

MCP Proxy Mode

# Using uvx (recommended)
uvx git+https://github.com/JEdward7777/translation_helps_mcp_proxy.git

# Local development
. venv/bin/activate
python -m src.translation_helps_mcp_proxy

# Local development (after setup)
. venv/bin/activate
translation-helps-mcp-proxy

# With options
uvx git+https://github.com/JEdward7777/translation_helps_mcp_proxy.git \
  --debug \
  --enabled-tools "fetch_scripture,fetch_translation_notes,get_system_prompt"

Advanced Options

# Different upstream URL
translation-helps-mcp-proxy --upstream-url "http://localhost:5173/api/mcp"

# Debug mode (detailed logging)
translation-helps-mcp-proxy --debug

# Tool filtering (controlled rollout)
translation-helps-mcp-proxy --enabled-tools "fetch_scripture,fetch_translation_notes"

# Parameter hiding (hide specific parameters from tool schemas)
translation-helps-mcp-proxy --hide-params "language,organization"

# Combined options
translation-helps-mcp-proxy \
  --upstream-url "http://localhost:5173/api/mcp" \
  --debug \
  --enabled-tools "fetch_scripture,fetch_translation_notes" \
  --hide-params "language,organization"

Production Deployment

uvx Installation (Recommended):

# Install globally on server
uvx install git+https://github.com/JEdward7777/translation_helps_mcp_proxy.git

# Run in production
translation-helps-mcp-proxy --enabled-tools "fetch_scripture,fetch_translation_notes,get_system_prompt"

Docker Deployment:

FROM python:3.11-slim
RUN pip install uv
RUN uvx install git+https://github.com/JEdward7777/translation_helps_mcp_proxy.git
CMD ["translation-helps-mcp-proxy"]

🛡️ Tool Filtering for Controlled Rollout

Control which MCP tools are available for enhanced safety during testing:

# FIRST: Discover all available tools
python -m src.translation_helps_mcp_proxy --list-tools

# Enable all tools (default behavior)
python -m src.translation_helps_mcp_proxy

# Enable only specific tools (comma-separated, no spaces around commas)
python -m src.translation_helps_mcp_proxy --enabled-tools "fetch_scripture,fetch_translation_notes"

# Enable only fully tested tools
python -m src.translation_helps_mcp_proxy --enabled-tools "fetch_scripture,fetch_translation_notes,get_system_prompt"

# Disable all tools (useful for testing)
python -m src.translation_helps_mcp_proxy --enabled-tools ""

🔒 Parameter Hiding for Downstream Compatibility

Hide specific parameters from tool schemas to solve downstream compatibility issues:

# Hide language and organization parameters from all tools
python -m src.translation_helps_mcp_proxy --hide-params "language,organization"

# Hide only specific parameters
python -m src.translation_helps_mcp_proxy --hide-params "language"

# Combine with tool filtering
python -m src.translation_helps_mcp_proxy \
  --enabled-tools "fetch_scripture,fetch_translation_notes" \
  --hide-params "language,organization"

Use Case: When downstream tools provide invalid values for certain parameters (e.g., incorrect language codes), you can hide those parameters from the tool schema. This prevents the downstream tool from sending those parameters, allowing the upstream server to use its default values instead.

How it works:

• Removes specified parameters from the properties section of tool input schemas
• Removes hidden parameters from the required list if present
• Applies to ALL tools that have the specified parameters
• Case-sensitive: must match parameter names exactly (e.g., language not Language)

Example: If a downstream tool keeps sending an invalid language parameter to fetch_translation_notes, use:

python -m src.translation_helps_mcp_proxy --hide-params "language,organization"

This hides both parameters, so the downstream tool won't send them, and the upstream server will use default values.

📚 Book/Chapter Note Filtering for Translation Workflows

Filter out book-level and chapter-level notes from fetch_translation_notes responses to reduce redundancy and cost:

# Enable filtering of book and chapter notes
python -m src.translation_helps_mcp_proxy --filter-book-chapter-notes

# Combine with other options
python -m src.translation_helps_mcp_proxy \
  --filter-book-chapter-notes \
  --enabled-tools "fetch_translation_notes"

Use Case: When processing verse-by-verse translations, the upstream server returns book-level and chapter-level notes for every verse in that book/chapter. This causes expensive redundancy when translating multiple verses sequentially.

Example Problem:

• Fetching notes for John 3:16 returns:
  • ✅ Verse-specific notes for John 3:16 (what you need)
  • ❌ "Introduction to John" (repeated for every verse in John)
  • ❌ "John 3 Chapter Introduction" (repeated for every verse in chapter 3)

How it works:

• Automatically filters out notes with Reference: "front:intro" (book-level)
• Automatically filters out notes with Reference: "<chapter>:intro" (chapter-level)
• Keeps only verse-specific notes (e.g., Reference: "3:16")
• Updates the response metadata to reflect the filtered count

Benefits:

• Reduces response size: Eliminates duplicate book/chapter notes
• Lowers costs: Less data to process in downstream translation workflows
• Improves clarity: Only verse-specific notes are returned
• Maintains compatibility: Preserves all metadata and response structure

Before filtering (John 3:16):

{
  "items": [
    {"Reference": "front:intro", "Note": "# Introduction to John..."},
    {"Reference": "3:intro", "Note": "# John 3 Chapter Introduction..."},
    {"Reference": "3:16", "Note": "Verse-specific note 1..."},
    {"Reference": "3:16", "Note": "Verse-specific note 2..."}
  ],
  "metadata": {"totalCount": 9}
}

After filtering (with --filter-book-chapter-notes):

{
  "items": [
    {"Reference": "3:16", "Note": "Verse-specific note 1..."},
    {"Reference": "3:16", "Note": "Verse-specific note 2..."}
  ],
  "metadata": {"totalCount": 7}
}

Recommended for:

• Verse-by-verse translation workflows
• Automated translation processing pipelines
• Cost-sensitive applications processing many verses
• Any scenario where book/chapter context is not needed per verse

📋 Tool Discovery

List all available tools before configuring:

# Discover what tools are available from upstream
. venv/bin/activate
python -m src.translation_helps_mcp_proxy --list-tools

Example output:

📋 Discovering available tools from upstream server...

✅ Found 12 available tools:

 1. get_system_prompt         - Get the complete system prompt and constraints
 2. fetch_scripture           - Fetch Bible scripture text for a specific reference
 3. fetch_translation_notes   - Fetch translation notes for a specific Bible reference
 4. get_languages             - Get available languages for translation resources
 5. fetch_translation_questions - Fetch translation questions for a specific Bible reference
 6. browse_translation_words  - Browse and search translation words by category or term
 7. get_context               - Get contextual information for a Bible reference
 8. extract_references        - Extract and parse Bible references from text
 9. fetch_resources           - Fetch multiple types of translation resources for a reference
10. get_words_for_reference   - Get translation words specifically linked to a Bible reference
11. get_translation_word      - Get translation words linked to a specific Bible reference
12. search_resources          - Search across multiple resource types for content

💡 Usage: --enabled-tools "tool1,tool2,tool3"
   Example: --enabled-tools "fetch_scripture,fetch_translation_notes"

🔧 Integration with MCP Clients

The proxy is designed to work seamlessly with MCP clients like KiloCode, Claude Desktop, and other MCP-compatible tools. It provides a standard MCP stdio interface that any MCP client can connect to.

Example Integration Workflow

MCP Client → Translation Helps MCP Proxy → Translation Helps Server
     ↓              ↓                         ↓
JSON-RPC 2.0 → Protocol Translation → Bible Resources

How It Works:

1. MCP Client: Makes standard MCP tool calls via stdio
2. MCP Proxy: Translates requests to HTTP API calls
3. Translation Server: Returns Bible scripture, notes, and translation resources
4. MCP Response: Formats data for seamless client integration

💡 Recommended Workflow:

1. Run --list-tools to see all available tools
2. Start with verified tools: --enabled-tools "fetch_scripture,fetch_translation_notes,get_system_prompt"
3. Test each new tool individually before adding to your enabled list
4. Gradually expand your enabled tools as you verify each one works

Key Features:

• Safe rollout: Only enable tools you've verified work correctly
• Invalid tool detection: Server will error if you specify non-existent tools
• Case-sensitive: Tool names must match exactly (e.g., fetch_scripture not FETCH_SCRIPTURE)
• No whitespace: Use "tool1,tool2" not "tool1, tool2"

Available Tools for Filtering:

fetch_scripture             ✅ Verified working
fetch_translation_notes     ✅ Verified working
get_system_prompt          ✅ Verified working
fetch_translation_questions 🔄 Needs verification
browse_translation_words   🔄 Needs verification
get_translation_word       🔄 Needs verification
get_words_for_reference    🔄 Needs verification
get_context                🔄 Needs verification
extract_references         🔄 Needs verification
fetch_resources            🔄 Needs verification
search_resources           🔄 Needs verification
get_languages              🔄 Needs verification

Example Safe Configuration (Only Verified Tools):

python -m src.translation_helps_mcp_proxy --enabled-tools "fetch_scripture,fetch_translation_notes,get_system_prompt"

MCP Client Configuration

KiloCode Configuration (Recommended)

Step 1: Find your absolute paths and set up the virtual environment:

# Navigate to your translation_helps_mcp_proxy directory (replace with your actual path)
cd /absolute/path/to/your/translation_helps_mcp_proxy

# Activate virtual environment
. venv/bin/activate

# Note these paths for the configuration
pwd                # Current directory (use for 'cwd')
which python       # Python executable path (use for 'command')

Step 2: Add this configuration to your KiloCode MCP settings JSON:

{
  "translation-helps-mcp-proxy": {
    "command": "/absolute/path/to/your/translation_helps_mcp_proxy/venv/bin/python",
    "args": ["-m", "src.translation_helps_mcp_proxy"],
    "cwd": "/absolute/path/to/your/translation_helps_mcp_proxy",
    "env": {
      "PYTHONPATH": "/absolute/path/to/your/translation_helps_mcp_proxy"
    }
  }
}

Replace the paths above with your actual paths:

• Replace /absolute/path/to/your/translation_helps_mcp_proxy with your real directory path
• The command should point to your venv's Python: YOUR_PATH/venv/bin/python
• All three path fields should use the same base directory

Key Configuration Notes:

• command: Use the venv Python executable (not system python)
• cwd: Absolute path to the translation_helps_mcp_proxy directory
• env.PYTHONPATH: Ensures Python can find the modules
• Server name: translation-helps-mcp-proxy (use this name in KiloCode)

Alternative: Generic MCP Client Configuration

For other MCP clients that don't support virtual environments well:

{
  "translation-helps-mcp-proxy": {
    "command": "python",
    "args": ["-m", "src.translation_helps_mcp_proxy"],
    "cwd": "/absolute/path/to/translation_helps_mcp_proxy"
  }
}

Verification Steps

Test the configuration:

1. Save the JSON configuration in KiloCode
2. Restart KiloCode or reload MCP servers
3. In KiloCode, verify the server appears in the MCP tools list
4. Try calling a tool like fetch_scripture with {"reference": "John 3:16"}

Expected behavior:

• Server should connect without errors
• 12 tools should be available
• fetch_scripture should return John 3:16 text
• fetch_translation_notes should return translation notes

Troubleshooting KiloCode Integration

If the server doesn't start:

# Test manually first (replace with your actual path)
cd /absolute/path/to/your/translation_helps_mcp_proxy
. venv/bin/activate
python -m src.translation_helps_mcp_proxy --debug

Common issues:

• Wrong Python path: Ensure you're using venv/bin/python, not system python
• Missing dependencies: Run pip install -r requirements.txt in the venv
• Path issues: Use absolute paths for all directory references
• Permissions: Ensure the venv directory is readable

Debug configuration in KiloCode:

• Check KiloCode's MCP server logs for connection errors
• Verify the server name matches exactly (translation-helps-mcp-proxy)
• Ensure no other MCP servers are using the same name

🛠️ Available Tools (12 Total)

The proxy automatically discovers and forwards all tools from the upstream server:

Example: Fetching John 3:16

The fetch_scripture tool successfully retrieves Bible verses with multiple translations:

{
  "name": "fetch_scripture",
  "arguments": {"reference": "John 3:16"}
}

Returns: "For God so loved the world, that he gave his One and Only Son, so that everyone believing in him would not perish but would have eternal life." (ULT v86) plus UST, T4T, and UEB translations.

🔍 Response Format Handling

The proxy intelligently handles various upstream response formats:

1. Scripture Format: {"scripture": [...]} → Formatted multi-translation display
2. MCP Format: {"content": [...]} → Proper MCP TextContent objects
3. Wrapped Results: {"result": ...} → Extracts and formats result
4. Raw JSON: Any other format → JSON stringification fallback

🐛 Troubleshooting

Import Errors

# Ensure virtual environment is activated (MOST COMMON ISSUE)
. venv/bin/activate  # Use dot if 'source' command doesn't work

# Reinstall dependencies
pip install -r requirements.txt

⚠️ Common Issue: Most problems are caused by forgetting to activate the virtual environment. Always run . venv/bin/activate before any Python commands.

Connection Issues

# IMPORTANT: Activate venv first
. venv/bin/activate

# Test upstream connectivity
python -c "
import asyncio, httpx
async def test():
    client = httpx.AsyncClient(verify=False)
    r = await client.get('https://translation-helps-mcp.pages.dev/api/mcp?method=ping')
    print(f'Status: {r.status_code}, Response: {r.text[:100]}')
    await client.aclose()
asyncio.run(test())
"

Debug Mode

# IMPORTANT: Activate venv first
. venv/bin/activate

python -m src.translation_helps_mcp_proxy --debug

Shows detailed upstream communication, response parsing, and error details.

Virtual Environment Notes

• Always activate venv: All Python commands require the virtual environment to be activated
• Use dot syntax: If source venv/bin/activate doesn't work, use . venv/bin/activate
• Per-session: You need to activate the venv in each new terminal session
• Verification: Your prompt should show (venv) when the virtual environment is active

📊 Performance & Reliability

• Timeout: 30-second timeout for upstream requests
• Connection: Persistent HTTP client with connection pooling
• Memory: Minimal memory footprint, suitable for long-running processes
• SSL: Handles certificate issues by disabling verification for upstream server
• Async: Proper async/await with TaskGroup error handling

🔮 Technical Details

Key Dependencies

mcp>=1.0.0                 # Official MCP SDK
httpx>=0.25.0             # Async HTTP client  
typing-extensions>=4.0.0   # Type hints support

Core Architecture

• MCPProxyServer: Main proxy class handling MCP protocol and upstream communication
• Smart Tool Routing: Special handling for fetch_scripture and other tools
• Response Transformation: Converts various upstream formats to proper MCP responses
• Error Handling: Graceful async error handling with proper cleanup

Future Enhancements

Potential improvements for advanced use cases:

• Convert to pytest-based test suite for better CI/CD integration
• Add response caching for frequently called tools
• Support for additional MCP features (resources, prompts)
• Metrics and monitoring capabilities
• Rate limiting and request queuing

📝 License

This proxy server is provided as-is to enable compatibility with the translation-helps-mcp service.

🎉 Production Ready - The proxy server successfully bridges MCP clients with the upstream translation-helps-mcp server, with all tools working including Bible verse fetching via fetch_scripture.