UsingMcpServers

This MCP server hosts three text transformation tools that the TranslationAgent can invoke during a chat. The LeetSpeakTool converts normal text into leet speak (1337), the CodeSpeakTool performs a generic code-like transformation to illustrate formatting or encoding, and the ReverseTool reverses the input text. When a user chats with the TranslationAgent, the LLM may decide to call these tools via the MCP transport (Server-Sent Events) exposed by TranslationTools. The tools are registered in the MCP Tool Registry and executed on demand, with responses flowing back to the chat so the user sees transformed results integrated into the conversation.

Prerequisites:

• .NET 6+ SDK installed on your machine
• Git installed

Install and run the MCP server (TranslationTools) and the client (TranslationAgent):

1. Clone the repository
2. Build the TranslationTools project dotnet build TranslationTools/TranslationTools.csproj
3. Run the MCP server for TranslationTools dotnet run --project TranslationTools This will start the Kestrel web server hosting the MCP tools (default URL http://localhost:5000).
4. In a separate terminal, run the TranslationAgent client dotnet run --project TranslationAgent
5. Open the TranslationAgent console app and start typing prompts. If a prompt benefits from text transformation, the LLM may invoke MCP tools (LeetSpeakTool, CodeSpeakTool, ReverseTool) and you will see transformed responses integrated into the chat.

Notes and tips:

• The MCP server is exposed via Server-Sent Events (SSE) transport; ensure your environment allows SSE connections and localhost network traffic during development.
• TranslationTools registers three tools: LeetSpeakTool, CodeSpeakTool, and ReverseTool. You can extend the Tools/ directory with additional tool implementations and register them in the MCP registry.
• If you modify environment variables or ports, update ASPNETCORE_URLS accordingly and restart both services.
• For production, consider hosting TranslationTools behind a reverse proxy and applying proper TLS termination. Use managed identities per the project guidance when connecting to other Azure resources.
• If the TranslationAgent cannot reach TranslationTools, verify that the TranslationTools process is running and listening on the configured URL (default http://0.0.0.0:5000).
• Log files and diagnostic output will help diagnose tool invocation issues; check console output from both TranslationTools and TranslationAgent during debugging.