Utilify MCP Server
The first Model Context Protocol server for utility signup. Plug Utilify into any MCP-compatible agent — Claude Desktop, Claude Code, Cursor, Continue, or custom — and your agent can search, compare, and initiate utility signups at any Texas address on behalf of its user. No API key, no auth, no signup.
https://utilify.io/mcp
Streamable HTTP
none
/.well-known/mcp/server-card.json
/llms.txt
/openapi.json
utilify-io/utilify-mcp
Quick start
Claude Desktop
Add this to ~/Library/Application Support/Claude/claude_desktop_config.json (macOS) or %APPDATA%\Claude\claude_desktop_config.json (Windows):
{
"mcpServers": {
"utilify": {
"command": "npx",
"args": ["-y", "mcp-remote", "https://utilify.io/mcp"]
}
}
}
Restart Claude Desktop. Try: "What electricity plans are available in Houston 77002?"
Claude Code
claude mcp add utilify -- npx -y mcp-remote https://utilify.io/mcp
Cursor
Open Cursor Settings → MCP → Add New MCP Server:
{
"utilify": {
"command": "npx",
"args": ["-y", "mcp-remote", "https://utilify.io/mcp"]
}
}
Other MCP clients (Continue, Zed, custom)
Any client supporting Streamable HTTP transport can connect directly. Point it at https://utilify.io/mcp. No auth headers needed.
Local open-source agents (Ollama, LM Studio, llama.cpp)
Run a local LLM on a Mac Studio or workstation? Utilify works with the MCP clients most local agents use. No data leaves your machine except the API call to https://utilify.io/mcp — no auth, no tracking pixels.
Ollama via ollmcp (terminal TUI that bridges Ollama + MCP):
pip install ollmcp
ollmcp add utilify https://utilify.io/mcp
ollmcp --model qwen3.5:9b
Models with strong tool-calling as of 2026: qwen3.5:9b, gemma4:e4b, llama4:8b. Smaller models may struggle with multi-step tool use.
LM Studio: Settings → Integrations → MCP → Add Server → paste https://utilify.io/mcp. LM Studio auto-detects Streamable HTTP transport.
llama.cpp built-in web UI (as of March 2026): launch llama-server with --mcp https://utilify.io/mcp. Tools appear in the agent loop automatically.
Continue.dev in your code editor: add this to .continue/mcpServers/utilify.yaml in your workspace:
name: utilify
command: npx
args: ["-y", "mcp-remote", "https://utilify.io/mcp"]
OpenHands, CrewAI, AutoGen, LangChain: use mcp-remote or each framework's MCP adapter to connect to https://utilify.io/mcp. No API key required.
ChatGPT Custom GPT / Zapier / OpenAPI tools
Not using MCP? Utilify also publishes an OpenAPI 3.1 spec:
https://utilify.io/openapi.json
Paste that URL into ChatGPT's Custom GPT Actions, a Zapier webhook, Make.com, LangChain, or any OpenAPI-aware integration. Read-only endpoints require no auth. For signup flows, redirect users to https://utilify.io/zip/{zip}.
Plugin manifest: /.well-known/ai-plugin.json
Example prompts
- "Find the cheapest electricity plan in 77002."
- "Compare internet providers in Austin."
- "Set up utilities for my new apartment at ZIP 75201, moving in May 15."
- "What's a good renewable electricity plan under $0.12/kWh in Dallas?"
- "Generate a move-in checklist for a house in 78701."
Tools exposed
| Tool | Description |
|---|---|
search_utility_providers | List every electricity, internet, gas, water, and trash provider at an address. |
get_provider_details | Plans, pricing, contract terms, fees, and reviews for a provider. |
compare_providers | Side-by-side comparison of multiple providers. |
initiate_signup | Start a utility signup. Returns a ready-to-use redirect URL for the user. |
check_signup_status | Poll the status of a previously-initiated signup. |
get_move_checklist | Personalized setup checklist based on move date and address. |
get_promotions | Current deals, sign-up bonuses, and referral codes. |
Coverage
- Geographic: Texas only — 4,844 ZIP codes across Houston, Dallas-Fort Worth, Austin, San Antonio, and hundreds of smaller cities. Non-Texas requests return a coverage-request form.
- Utility types: electricity, internet, natural gas, water, trash, home security.
- Data freshness: plans updated weekly. Internet availability verified against FCC Broadband Data Collection.
How signups work
When your agent calls initiate_signup, Utilify returns a short redirect URL (https://utilify.io/go/{planId}?zip={zip}) for the user to open in their browser. The redirect carries affiliate-tracking parameters on our end and lands the user on the provider's official signup page, where they complete enrollment directly with the provider. Utilify earns a referral commission on completed signups — we never touch the user's payment info or credentials.
Plans are ranked by price, not by commission rate. We do not sell user data.
Fair use
- No API key or rate limit today. Cache tool responses client-side when you can — most data updates weekly.
- Do not construct
/go/{planId}URLs yourself — always callinitiate_signupso the click is properly tracked and disclosed. - If your product adds material volume, email [email protected] so we can provision capacity.
Questions or issues?
Email [email protected]. We read every message.