About MCP Server TypeScript Starter
MCP Server TypeScript Starter is a TypeScript MCP server starter for location lookups by coordinates or IP address. It also includes a health-check tool and uses IPInfo.io for IP-based lookups.
Key features
- 01Coordinate-based location lookup
- 02IP-based lookup via IPInfo.io
- 03Service health-check tool
- 04TypeScript server setup
Use cases
- 01Look up a location from latitude and longitude
- 02Retrieve location details for an IP address
- 03Check whether the service is healthy
MCP support
It exposes coordinate lookup, IP-based location lookup, and health-check tools to MCP clients. The IP lookup uses IPInfo.io.
Configuration
Local server config is the same for every client. Copy it into your client’s MCP config file.
Tools
4Saved tool list · updated 3w ago
| Parameter | Type | Required | Description |
|---|---|---|---|
| latitude | string | Yes | Latitude coordinate |
| longitude | string | Yes | Longitude coordinate |
Details
From the project READMEMCP Server TypeScript Starter
This is a Model Context Protocol (MCP) server implementation that provides location services. It demonstrates how to build an MCP server using TypeScript with real-world functionality for location lookups via coordinates or IP addresses.
Features
- TypeScript configuration
- Complete MCP server setup
- Location service implementation
- Coordinate-based location lookup
- IP-based location lookup (using IPInfo.io)
- Health check endpoint
- Type-safe development environment
- Integration with external APIs
Installation
npm install mylocation-mcp
Usage
- Create a
.envfile with your IPInfo.io API token:
IPINFO_TOKEN=your_ipinfo_token_here
- Import and use in your code:
import { McpServer } from 'mylocation-mcp';
Development
If you want to modify or contribute to the package:
# Clone the repository
git clone https://github.com/yhwancha/mylocation-mcp.git
cd mylocation-mcp
# Install dependencies
npm install
# Set up environment variables
cp .env.example .env
# Edit .env and add your IPInfo.io API token
# Build the project
npm run build
Project Structure
.
├── src/
│ └── index.ts # Main server implementation with location tools
├── build/ # Compiled JavaScript files
├── package.json # Project dependencies and scripts
├── tsconfig.json # TypeScript configuration
├── .env.example # Environment variables template
└── README.md # Documentation
Implemented Tools
1. get-location-by-coordinates
server.tool(
"get-location-by-coordinates",
"Get location information from provided coordinates",
{
latitude: z.string().describe("Latitude coordinate (-90 to 90)"),
longitude: z.string().describe("Longitude coordinate (-180 to 180)")
},
async ({ latitude, longitude }) => {
// Implementation details...
}
);
2. get-location-by-ip
server.tool(
"get-location-by-ip",
"Get location information from IP address",
{
ipAddress: z.string().describe("IP address to lookup")
},
async ({ ipAddress }) => {
// Implementation details...
}
);
3. health
server.tool(
"health",
"Check the health status of the service",
{},
async () => {
// Implementation details...
}
);
MCP Server Configuration
To use this MCP server in your project, add the following configuration:
{
"mcpServers": {
"location-service": {
"command": "npx",
"args": [
"-y",
"mylocation-mcp-server"
],
"env": {
"IPINFO_TOKEN": <IPINFO_TOKEN>
}
}
}
}
Response Format
All tools return responses in this format:
{
"content": [
{
"type": "text",
"text": "JSON string containing the response data"
}
]
}
The response data follows this structure:
{
"status": "success|error",
"source": "user_provided|ip_based",
"data": {
// Location data when successful
},
"error": "Error message when failed"
}
Dependencies
@modelcontextprotocol/sdk: MCP server implementationzod: Schema validationaxios: HTTP client for IPInfo APIdotenv: Environment variable management- TypeScript development tools
License
MIT
Comments
New to MCP?
From what the protocol is to installing your first server, these answers cover most first questions.
An open protocol that defines how AI applications connect to external tools and data in a uniform way. Clients talk to the model; MCP servers provide tools, resources and prompt templates. They exchange standard messages, so one server can be reused by many clients.