eRegulations MCP Server
Click on "Deploy Server".
Wait a few minutes for the server to deploy. Once ready, it will show a "Started" state.
In the chat, type
@followed by the MCP server name and your instructions, e.g., "@eRegulations MCP Server list all available procedures"
That's it! The server will respond to your query, and you can continue using it as needed.
Here is a step-by-step guide with screenshots.
eRegulations MCP Server
A Model Context Protocol (MCP) server implementation for accessing eRegulations API data. This server provides structured, AI-friendly access to eRegulations instances, making it easier for AI models to answer user questions about administrative procedures.
Features
Access eRegulations data through a standardized protocol
Query procedures, steps, requirements, and costs
MCP prompt templates to guide LLM tool usage
Streamlined implementation using standard I/O connections
Related MCP server: Federal Register MCP Server
Installation
Quick Installation with Smithery
The easiest way to install and run the eRegulations MCP Server is through Smithery:
Visit https://smithery.ai/server/@unctad-ai/eregulations-mcp-server for the installation command.
Installation via npm Registry
You can also run the eRegulations MCP Server directly using npx with the published npm package:
# Set environment variables and run with npx
export EREGULATIONS_API_URL=https://example.com/api && export NODE_ENV=production && npx -y @unctad-ai/eregulations-mcp-server@latestConfiguration
The server can be configured using command-line arguments (preferred) or environment variables:
Command-line Arguments
--api-url: URL of the eRegulations API to connect to
Environment Variables
EREGULATIONS_API_URL: URL of the eRegulations API to connect to (fallback if --api-url is not provided)
Note: Command-line arguments take precedence over environment variables.
Available Tools
The MCP server provides the following tools:
listProcedures
Lists all available procedures in the eRegulations system.
getProcedureDetails
Gets detailed information about a specific procedure by its ID.
Parameters:
procedureId: ID of the procedure to retrieve
getProcedureStep
Gets information about a specific step within a procedure.
Parameters:
procedureId: ID of the procedurestepId: ID of the step within the procedure
Prompt Templates
The server provides prompt templates to guide LLMs in using the available tools correctly. These templates explain the proper format and parameters for each tool. LLM clients that support the MCP prompt templates capability will automatically receive these templates to improve their ability to work with the API.
Development
# Run in development mode
npm run start
# Run tests
npm test
# Run tests with watch mode
npm run test:watch
# Run test client
npm run test-clientAvailable Tools
3 toolsgetProcedureDetailsA
Get detailed information about a specific procedure by ID.
Inputs: procedureId (required).
getProcedureStepB
Get information about a specific step within a procedure.
Inputs: stepId (required), procedureId (required).
listProceduresA
List all available procedures in the eRegulations system.
Inputs: no named parameters.
Tool Schema Changelog
Recent tool additions, removals, and schema changes observed during successful MCP inspections.
Loading tool schema changelog…
TDQS
Scored across 3 tools
Each tool has a distinct purpose: listing all procedures, retrieving a specific procedure's details, and getting a specific step within a procedure. There is no overlap or confusion between these operations.
All tool names follow a consistent camelCase verb_noun pattern: listProcedures, getProcedureDetails, getProcedureStep. The naming is uniform and predictable.
Three tools is slightly on the lower end but reasonable for a focused read-only procedures lookup server. Each tool serves a clear purpose, and the count is not thin enough to feel incomplete.
The server covers the essential read operations for procedures and steps. A minor gap is the lack of a search or list steps function, but the core lookup workflow is supported.
Related MCP Connectors
Semantic retrieval across 295,000+ Indonesian regulations and 5.6M+ legal provisions, updated daily. Give AI direct access to Indonesian regulatory knowledge before reasoning.
US Federal Register for AI agents: rules, notices, executive orders, agency lookup. No keys.
US Federal Register for AI agents: rules, notices, executive orders, agency lookup. No keys.
Search and trace US federal rules across the Federal Register, eCFR, and Regulations.gov.
Related MCP Servers
- FlicenseDqualityNot gradedmaintenanceA Model Context Protocol server implementation that provides structured, AI-friendly access to eRegulations data, making it easier for AI models to answer user questions about administrative procedures.419 npm-
- AlicenseAqualityDmaintenanceEnables AI assistants to search and retrieve executive orders, presidential documents, rules, and agency information from the Federal Register API through natural language queries.129 npmMIT
- AlicenseNot gradedqualityNot gradedmaintenanceEnables interaction with the Regulations.gov API to search federal rulemaking dockets, proposed and final rules, public comments, and comment periods. Supports tracking FAR/DFARS case histories and monitoring open comment periods across federal agencies with optional API key authentication for higher rate limits.MIT
- AlicenseNot gradedqualityBmaintenanceEnables querying the US Federal Register API for federal register documents and data through natural language.102 npmMIT