remote-capable server
The server can be hosted and run remotely because it primarily relies on remote services or has no dependency on the local environment.
Integrations
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
Installation
Configuration
The server can be configured using command-line arguments (preferred) or environment variables:
Command-line Arguments (Preferred)
--api-url
: URL of the eRegulations API to connect to--help
: Show all available command-line options
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.
Usage
Using Standard I/O
For integration with LLM systems that support MCP over standard I/O:
Docker Deployment
You can deploy the MCP server using Docker. Create a docker-compose.yml
file:
Then run:
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
Logs
The MCP Server redirects all console output to a TCP socket to avoid interfering with the MCP protocol which requires clean JSON communication on stdout.
To view logs:
- Start the log server in a separate terminal:Copy
- Then run the MCP server with the MCP inspector or directly:Copy
All logs will appear in the log server terminal window instead of stdout/stderr.
License
MIT
This server cannot be installed
A 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.