home / mcp / remote mcp server template mcp server
mcp-server-template
Configuration
View docs{
"mcpServers": {
"ahramadan44-remote-mcp-server-template": {
"url": "https://YOUR-APP-NAME.ondigitalocean.app/mcp",
"headers": {
"PORT": "8080"
}
}
}
}This guide explains how to use and set up a remote MCP server that checks domain availability using WHOIS lookups and DNS resolution. It lets you deploy the checker to the cloud or run it locally, and then connect MCP-compatible clients to perform batch domain checks from anywhere.
You connect a remote domain-checker MCP server to your MCP client by pointing the client at either the deployed HTTP URL or the local/CI-based stdio setup. The remote option runs the checker as a cloud service, while the local option lets you run the checker inside your own environment for development and testing. After you configure the MCP server URL or command, you can perform single-domain checks or batch checks for multiple domains, receiving a structured result that indicates availability and the underlying WHOIS and DNS signals.
Prerequisites: ensure Python 3.8 or higher and the pip package manager are available on your system.
Step-by-step commands to set up the local MCP server:
git clone https://github.com/ajot/domain-checker-mcp-server.git
cd domain-checker-mcp-server
python -m venv venv
# On macOS/Linux
source venv/bin/activate
# On Windows
venv\Scripts\activate
pip install -r requirements.txtConfiguration options include two ways to connect to the MCP server: a deployed HTTP URL or a local stdio setup. Use the HTTP method when you have deployed the server to a cloud provider. Use the stdio method for local development or when running the server directly in your environment.
Remote HTTP MCP configuration example you can use in your MCP client:
{
"mcpServers": {
"domain-checker": {
"url": "https://YOUR-APP-NAME.ondigitalocean.app/mcp",
"description": "Check domain availability"
}
}
}If you deploy to DigitalOcean App Platform, you typically run the app with port 8080. You configure the app to listen on port 8080 and expose the /mcp endpoint for MCP clients to connect.
Local development configuration for the MCP server can be added to MCP client configurations, pointing to the local script that runs the checker.
Example local MCP client configuration for a stdio-based setup:
{
"mcpServers": {
"domain-checker": {
"command": "/path/to/your/venv/bin/python",
"args": ["/path/to/your/local-domain-checker.py"]
}
}
}Common issues include activation of the virtual environment, missing dependencies, and network timeouts when querying WHOIS servers. Ensure the virtual environment is activated before running commands and that all dependencies listed in requirements.txt are installed.
If you encounter deployment issues on cloud platforms, verify that the port configuration matches 8080 and that the runtime command aligns with how the server is started in your environment.