Look up permits, licenses, and fees for food service businesses in Austin, SF, and NYC.
MCP server for CanIDo — the regulatory intelligence API that answers: "What permits, licenses, or regulations apply if I want to do X at location Y?"
Give any MCP-compatible AI agent (Claude Desktop, Cursor, Continue, etc.) the ability to look up structured permit requirements for food service businesses in:
Add to your claude_desktop_config.json:
{
"mcpServers": {
"canido": {
"command": "npx",
"args": ["-y", "@canido/mcp-server"],
"env": {
"CANIDO_API_KEY": "your_api_key_here"
}
}
}
}
Get a free API key at canido-api-production.up.railway.app (10 queries/month, no credit card required).
Any MCP-compatible client will work. Point them at:
command: npx
args: ["-y", "@canido/mcp-server"]
env:
CANIDO_API_KEY: your_api_key
lookup_requirementsLook up permits, licenses, and regulatory requirements for a business activity in a specific location.
Parameters:
activity: food_truck | restaurant | catering | cottage_foodlocation: austin_tx | san_francisco_ca | new_york_city_nycategory (optional): health | fire | zoning | building | alcohol | tax | business_registration | certificationlist_locationsGet all supported locations.
get_requirement_detailGet detailed info about a specific requirement by ID.
Ask Claude:
"What do I need to open a food truck in Austin?"
Claude will call lookup_requirements and come back with structured data: permits, fees, agencies, processing times, prerequisites, and common gotchas.
MIT
Source-derived launch command. Check the maintainer’s required arguments and credentials before running:
npx -y @canido/mcp-serverMerge this template into ~/Library/Application Support/Claude/claude_desktop_config.json. Keep existing servers. Add any arguments, credentials, and permissions required by the maintainer; this template has not been install-tested.
{
"mcpServers": {
"io-github-benswork-space-canido-mcp": {
"command": "npx",
"args": [
"-y",
"@canido/mcp-server"
]
}
}
}Restart Claude Desktop completely for changes to take effect. Confirm the server appears connected in the client’s tool list, then try a read-only example from its documentation.
Claude Desktop setup reference@canido/mcp-servernpmio.github.benswork-space/canido-mcp works with any MCP-compatible client. Copy the config snippet from the Configuration section above and add it to the file shown for your client, then restart the application.
~/Library/Application Support/Claude/claude_desktop_config.jsonRestart Claude Desktop completely for changes to take effect.~/.cursor/mcp.jsonRestart Cursor for changes to take effect..vscode/mcp.jsonReload VS Code window for changes to take effect.~/.codeium/windsurf/mcp_config.jsonRestart Windsurf for changes to take effect..mcp.jsonSave at the project root, then start Claude Code in that project and review the MCP server approval prompt. Keep real credentials out of shared files.