rollin

ROLLIN provides an MCP server that serves wheelchair accessibility data for thousands of locations. Once you have a Free API Key, you can run the server locally with Node.js and expose a standard MCP interface that any MCP client can connect to. The server exposes tools like search_locations, get_location_details, list_regions, submit_feedback, and check_health, allowing you to query accessibility scores, view feature breakdowns, discover coverage areas, submit corrections, and verify the service health. To use it, start the server with your API key and point your MCP client to the local or remote server instance using the provided configuration blocks. The MCP client will then be able to perform location searches, retrieve detailed accessibility information, and submit updates through natural prompts or structured commands.

Prerequisites:\n- Node.js 18 or newer (per the project’s compatibility)\n- npm (comes with Node.js)\n\n1) Install Node.js 18+ from https://nodejs.org if you don’t have it already.\n2) Ensure you have your ROLLIN API key from joinrollin.com/portal.\n3) No global install is required — you can run the MCP server directly via npx as shown below.\n\nUsage steps:\n1) Authenticate in your environment by exporting your API key:\n\nbash\nexport ROLLIN_API_KEY=your_api_key_here\n\n\n2) Run the MCP server using npx (no global install needed):\n\nbash\nnpx -y rollin-mcp-server\n\n\n3) Connect your MCP client to the running server using the appropriate client configuration (as shown in the examples in the README). The server expects the ROLLIN_API_KEY to be provided in environment variables or the client config.\n\n4) Optional: verify the server is up before making requests:\n\nbash\n# If you have a health check endpoint or tool, use it here per your client implementation.\n

Tips and common issues:\n- Ensure Node.js 18+ is installed; the server runs with npx without a global install.\n- Your ROLLIN_API_KEY must be supplied to the server (either via ROLLIN_API_KEY env var or the client configuration).\n- If you modify client configurations, you can reuse the same command (npx -y rollin-mcp-server) and just supply the proper API key in env or config.\n- The server exposes tools for searching nearby locations, retrieving detailed location scores, listing coverage regions, submitting corrections, and performing health checks.\n- When distributing to teammates or integrating into CI, consider passing the API key securely via environment variables rather than embedding in config files.\n- If you run into network or npm/pnpm workspace issues, ensure you’re using a Node 18+ environment and that your network can reach npmjs.org to resolve the rollin-mcp-server package.\n- MCP clients consuming this server should rely on the MCP protocol for interoperability; no bespoke wrappers are required.\n- If you need to customize the server name in configs, you can adapt the mcpServers map in your project’s MCP config to point to different keys as needed.