seeclickfix

The SeeClickFix MCP Server exposes a single MCP tool named get_requests that lets clients query real-time civic issue reports from SeeClickFix's Open311 API by geographic location. It supports location-based searching, returning nearby civic problems, service requests, and related metadata such as descriptions, statuses, and timestamps. To use it, send an MCP request to the server with the get_requests tool and provide latitude and longitude parameters. This enables MCP clients to retrieve contextual civic data for a given point, useful for mapping, dashboards, or automated monitoring of local infrastructure issues.

You can interact with the tool by specifying the following arguments: latitude and longitude as strings. For example, a request object includes the tool name and an arguments dictionary containing latitude and longitude. The server is built on MCP SDK and uses Axios for HTTP requests to the SeeClickFix Open311 API, returning standardized MCP-compatible responses that downstream clients can interpret.

Prerequisites:

• Node.js 18+ (LTS)
• npm (comes with Node.js)

Installation steps:

1. Clone the repository: git clone https://github.com/chrisjamesbond/seeclickfix-mcp-server cd seeclickfix-mcp-server

2. Install dependencies: npm install

3. Build the project: npm run build npm run bundle

4. Run the server (development or production as needed):

   • Development: npm run dev
   • Production (after build/bundle): node dist/server.js (or the appropriate entry point if different in your setup)

5. Optional: verify the server is listening and accessible from your MCP client, using the provided get_requests tool with latitude/longitude parameters.

Notes and tips:

• This MCP server relies on the SeeClickFix Open311 API for data. Ensure network access to the API is available and that any API keys or rate limits are handled as required by your deployment environment.
• The configured entry point path in mcp_config may need to be updated to the actual built server file (e.g., dist/server.js or build/output.js) after your build process.
• If you plan to deploy in a container or cloud environment, consider mapping environment variables for API endpoints, timeouts, and logging levels. You can add variables under the env section of the mcp_config for the seeclickfix server.
• Common issues: missing dependencies, incorrect entry path, or API rate limiting from SeeClickFix. Check build artifacts and ensure the Node.js runtime matches the required version (Node.js 18+).
• The server uses MCP SDK conventions; ensure MCP clients you deploy are compatible with the get_requests tool payload format (tool name and arguments).