Frequently Asked Questions about the eRegulations MCP Server

Q: What is an MCP Server? A: MCP stands for Model Context Protocol. An MCP server acts as a bridge, standardizing how applications provide context to Large Language Models (LLMs). In the case of the eRegulations MCP Server, it provides a structured way for AI models to access and interact with eRegulations API data.

Q: What is the purpose of the eRegulations MCP Server? A: The eRegulations MCP Server simplifies accessing eRegulations API data for AI models. It provides a standardized protocol and structured data, allowing AI to easily query procedures, steps, requirements, and costs related to administrative regulations.

Q: How do I install the eRegulations MCP Server? A: The recommended method is using Docker. You can pull the latest image from the GitHub Container Registry (GHCR) and run it, providing the URL of your eRegulations API. Alternatively, you can install it using Smithery.

Q: What environment variable is required to run the server? A: The EREGULATIONS_API_URL environment variable is required. It should be set to the base URL of the eRegulations instance you want to connect to (e.g., https://api-tanzania.tradeportal.org).

Q: What tools are available in the MCP server? A: The server provides tools such as listProcedures (to list all procedures), getProcedureDetails (to get details about a specific procedure), getProcedureStep (to get details about a specific step in a procedure), and searchProcedures (to search for procedures by keyword).

Q: What are prompt templates and how are they used? A: Prompt templates guide LLMs in using the available tools correctly. They explain the proper format and parameters for each tool, improving the LLMs’ ability to work with the API. LLM clients supporting the MCP prompt templates capability will automatically receive these templates.

Q: Can I use the eRegulations MCP Server with UBOS? A: Yes! The eRegulations MCP Server is designed to integrate seamlessly with the UBOS platform. UBOS is a full-stack AI Agent Development Platform that helps you orchestrate AI Agents, connect them with your enterprise data, and build custom AI Agents.

Q: What if the eRegulations API I am connecting to requires authentication? A: The eRegulations MCP server currently relies on the underlying eRegulations API for authentication. Ensure your EREGULATIONS_API_URL points to an endpoint that either doesn’t require authentication or handles authentication appropriately for the MCP server to access the data.