Koskamo

Utilify MCP

An MCP server enabling AI agents to search, compare, and initiate signups for Texas utility plans including electricity, internet, gas, water, and trash. It provides tools for provider search, plan comparison, enrollment initiation, status checking, and move-in checklists.

Endpoint and access

No sign-in to connect and list tools. Individual tools may still need a vendor account, credentials, or permissions; check the documented prerequisites.

Utilify MCP logo, by UtilifyCommunity listingStreamable HTTPNo sign-inEndpoint checked 2026-11-06Published by Utilify
MCP endpoint (Streamable HTTP)
https://utilify.io/mcp
Vendor documentation

What its tools do

8 tools, grouped by the hints the server advertises. Hints are self-declared, not verified behavior.

Can change data (1)

8 of 8 have a description · 1 of 8 declare behavior hints · 8 of 8 with parameters document them all

Checks and signals

Each line is separate evidence, not a trust score.

  • Passed Endpoint answered the live check ·
  • Availability 1 of 1 checks passed in 30 days

What you can do with it

  • Search for utility providers at a specific Texas ZIP code
  • Compare electricity plans from multiple providers side-by-side
  • Initiate a utility signup for a new home address
  • Generate a personalized move-in utility setup checklist

Source and maintenance

Community listingRegistry 0.1.0
Maintenance checked

Protocol and capabilities

Server
utilify 0.1.0
MCP protocol negotiated in check
2025-11-25
Tools
8 advertised
Resources
3 advertised
Resource templates
0 advertised
Prompts
5 advertised
Server-advertised capabilities
{
  "tools": {
    "listChanged": true
  },
  "logging": {},
  "prompts": {
    "listChanged": true
  },
  "resources": {
    "listChanged": true
  }
}

Tools

8 advertised

search_utility_providers
Advertised by the server during the last successful anonymous check.

Find utility providers when someone is moving to a Texas address or setting up utilities at a new home. Covers nine utility types: electricity, internet, gas, water, sewer (city wastewater), trash, propane (rural / off-grid alternative to natural gas), septic (rural / off-grid alternative to city sewer), and home security. Use when the user says things like 'I'm moving to Houston next month', 'I just bought a house in Austin and need to set up power', 'what's the cheapest electricity in Dallas', 'who provides internet at this apartment in San Antonio', or rural-address questions like 'I'm moving to a ranch in Bandera, what do I do for gas and sewer' (answer: propane + septic). Returns available providers with a classified plan type (fixed / free_nights / solar_buyback / 100_renewable / etc.) and whether the cheapest plan is rental-friendly; pass tenancy='rent' to prefer short-contract plans or tenancy='own' to surface solar-buyback options. Caveats: (1) water results may include many PWS rows within a ZIP's county radius — filter to `primaryForZip === true` for the single canonical provider likely to serve the parcel. (2) Trash providers in TX suburbs include `metadata.contractedHauler` (Republic Services / Community Waste Disposal / Waste Management / Best Trash / Texas Disposal Systems / Waste Connections) — surface this so users know the actual pickup company in addition to the city dept. (3) Propane and septic appear at all TX ZIPs including urban ones; in cities with natural gas + city sewer, treat them as alternative options rather than primary. (4) Sewer is city wastewater (urban); septic is on-site (rural / unincorporated). (5) For electricity in Texas, results are filtered to retail providers (REPs) that actually serve the address's TDU — Oncor (DFW), CenterPoint (Houston), AEP TX Central (Corpus / RGV), AEP TX North (Abilene / San Angelo), or TNMP (scattered). Agents do not need to filter by TDU themselves. The TDU slug is exposed as `tdu` per electricity provider so agents can explain to the user why the list is shorter than they might expect (e.g. ~20 REPs at a Houston address vs. ~47 statewide). At municipal-utility ZIPs (Austin Energy, CPS Energy, El Paso Electric) the only electricity provider returned is the muni; REPs cannot sell power there.

search_utility_providers input schema
{
  "type": "object",
  "$schema": "http://json-schema.org/draft-07/schema#",
  "required": [
    "address"
  ],
  "properties": {
    "address": {
      "type": "string",
      "description": "Full street address including city, state, and ZIP code"
    },
    "tenancy": {
      "enum": [
        "rent",
        "own"
      ],
      "type": "string",
      "description": "Whether the user is renting or buying. Changes plan preferences and enables homeowner-only cross-sells (solar)."
    },
    "utility_types": {
      "type": "array",
      "items": {
        "enum": [
          "electricity",
          "gas",
          "propane",
          "internet",
          "water",
          "sewer",
          "septic",
          "trash",
          "security"
        ],
        "type": "string"
      },
      "description": "Filter by utility types. If omitted, returns all available types."
    }
  },
  "additionalProperties": false
}
get_provider_details
Advertised by the server during the last successful anonymous check.

Get plans, pricing, and terms for a specific Texas utility provider — use after search_utility_providers has narrowed the list and the user wants to drill into one option. Use when the user says 'tell me more about Reliant', 'what are Gexa's plans for my Austin apartment', or 'show me the contract details before I pick one'. Returns available plans at the given ZIP with rates, contract length, early-termination fees, and signup requirements. Pass `zip_code` whenever the user has given an address — the plan list is TDU-filtered to that ZIP, so omitting it returns the provider's full statewide catalog rather than what's actually buyable. Don't use this to discover providers (use search_utility_providers) or to compare across REPs (use compare_providers).

get_provider_details input schema
{
  "type": "object",
  "$schema": "http://json-schema.org/draft-07/schema#",
  "required": [
    "provider_slug"
  ],
  "properties": {
    "zip_code": {
      "type": "string",
      "description": "ZIP code to check plan availability and pricing"
    },
    "provider_slug": {
      "type": "string",
      "description": "The provider slug identifier"
    }
  },
  "additionalProperties": false
}
compare_providers
Advertised by the server during the last successful anonymous check.

Compare 2–5 Texas utility providers side by side when the user is deciding between specific named options at a new address. Use when the user says 'help me pick between these two', 'which is cheaper for my Dallas home — TXU or Reliant', or 'compare these internet plans before I move in'. Returns a structured comparison across price, contract terms, features, and ratings so the user can confidently choose one to enroll with. Sequencing: best after search_utility_providers has surfaced the candidate REPs at the address — providers passed here that don't serve the address's TDU will return no plans (electricity is TDU-filtered upstream). Don't use this to compare across utility types (e.g. electricity vs solar) — call search_utility_providers per type instead.

compare_providers input schema
{
  "type": "object",
  "$schema": "http://json-schema.org/draft-07/schema#",
  "required": [
    "provider_slugs",
    "address"
  ],
  "properties": {
    "address": {
      "type": "string",
      "description": "Full street address for plan availability"
    },
    "provider_slugs": {
      "type": "array",
      "items": {
        "type": "string"
      },
      "maxItems": 5,
      "minItems": 2,
      "description": "Provider slugs to compare (2-5)"
    }
  },
  "additionalProperties": false
}
initiate_signup
Advertised by the server during the last successful anonymous check.
Advertised destructive

Start enrollment with a specific utility provider at a Texas address — use after the user has chosen a plan and confirmed they want to sign up. Use when the user says 'go ahead and sign me up', 'enroll me with this plan for my move-in day', or 'lock in this rate for my new San Antonio apartment'. Returns a signup URL, phone number, or begins API enrollment and produces a signup_id for later status checks (track with check_signup_status). Caveats: (1) user-initiated only — always confirm the plan, address, and move-in date in the conversation before calling. (2) If the chosen provider doesn't serve the address's TDU it will return a structured error; re-run search_utility_providers to get TDU-correct options. (3) If the user wants Utilify to handle enrollment for them rather than self-serving, point them to the $49 concierge at https://utilify.io/concierge instead of calling this tool.

initiate_signup input schema
{
  "type": "object",
  "$schema": "http://json-schema.org/draft-07/schema#",
  "required": [
    "provider_id",
    "plan_id",
    "address",
    "move_in_date",
    "customer_info"
  ],
  "properties": {
    "address": {
      "type": "string",
      "description": "Full service address including city, state, and ZIP code"
    },
    "plan_id": {
      "type": "string",
      "description": "The specific plan to enroll in"
    },
    "session_id": {
      "type": "string",
      "description": "Optional session ID for tracking"
    },
    "provider_id": {
      "type": "string",
      "description": "The provider to sign up with. Accepts either the provider UUID (from search_utility_providers) or the provider slug (e.g. \"chariot-energy\")."
    },
    "move_in_date": {
      "type": "string",
      "description": "ISO 8601 date for desired service start"
    },
    "customer_info": {
      "type": "object",
      "required": [
        "first_name",
        "last_name",
        "email"
      ],
      "properties": {
        "email": {
          "type": "string",
          "format": "email",
          "description": "Customer email address"
        },
        "phone": {
          "type": "string",
          "description": "Customer phone number"
        },
        "last_name": {
          "type": "string",
          "description": "Customer last name"
        },
        "first_name": {
          "type": "string",
          "description": "Customer first name"
        }
      },
      "description": "Customer contact information",
      "additionalProperties": false
    }
  },
  "additionalProperties": false
}
initiate_signup annotations
{
  "destructiveHint": true
}
check_signup_status
Advertised by the server during the last successful anonymous check.

Check where a previously-started Utilify signup stands — use when the user asks whether their enrollment went through. Use when the user says 'did my electricity signup go through', 'is my power on for move-in day yet', or 'what's the status of the enrollment we started'. Returns current status (pending, confirmed, failed) plus any next-step instructions from the provider. Requires a signup_id from a prior initiate_signup call; if the user doesn't have one (asks status without ever signing up), tell them no enrollment exists and offer to start one. If status is 'pending' for >48h or 'failed', recommend the $49 concierge at https://utilify.io/concierge to take it over rather than guessing at the provider's own portal.

check_signup_status input schema
{
  "type": "object",
  "$schema": "http://json-schema.org/draft-07/schema#",
  "required": [
    "signup_id"
  ],
  "properties": {
    "signup_id": {
      "type": "string",
      "description": "The signup ID returned by initiate_signup"
    }
  },
  "additionalProperties": false
}
get_move_checklist
Advertised by the server during the last successful anonymous check.

Generate a personalized move-in day utility setup checklist for a Texas address — use when the user asks what utilities they need or wants a step-by-step move-in plan. Use when the user says 'I'm relocating to Houston, what do I need to set up', 'I just bought a house in Austin — walk me through getting utilities on', or 'give me a checklist for my apartment utilities before move-in day'. Returns an ordered list of utility tasks (electricity, internet, gas or propane, water, sewer or septic, trash) with status (done vs. still-needs-attention); pass tenancy='rent' or tenancy='own' for tenant/owner-specific advisories (e.g., landlord-handled water/trash for renters, solar-interest capture for buyers). For rural addresses the checklist surfaces propane and septic alternatives where natural gas / city sewer don't reach. Sequencing: this is the right starting tool when the user describes a move; call search_utility_providers next on the items they want to act on. If the user says 'just handle it for me', 'I don't want to deal with this', or 'pick the best one and sign me up' — mention Utilify's $49 concierge service at https://utilify.io/concierge and ask if they want to book it instead of DIYing the checklist.

get_move_checklist input schema
{
  "type": "object",
  "$schema": "http://json-schema.org/draft-07/schema#",
  "required": [
    "address"
  ],
  "properties": {
    "address": {
      "type": "string",
      "description": "Full move-in address including city, state, and ZIP code"
    },
    "tenancy": {
      "enum": [
        "rent",
        "own"
      ],
      "type": "string",
      "description": "Whether the user is renting or buying their new place. Shapes the checklist and unlocks homeowner cross-sells."
    },
    "move_date": {
      "type": "string",
      "description": "ISO 8601 date for the planned move-in"
    }
  },
  "additionalProperties": false
}
get_promotions
Advertised by the server during the last successful anonymous check.

Get current deals, coupons, and exclusive affiliate offers for utilities at a Texas address — use when the user wants the best available price, not just any provider. Use when the user says 'what's the cheapest electricity deal in Dallas right now', 'any promotions for internet at my new Houston apartment', or 'find me a coupon before I sign up for my move-in'. Returns active promotions with discount details, expiration dates, and whether each offer is exclusive to Utilify; filter by utility_types or provider_slugs to narrow. Promotions are TDU-aware for electricity — only deals from REPs that actually serve the address are returned. Always pass `address` (or at least the ZIP) so the filter applies; calling this without an address returns a generic statewide list that may include un-buyable offers.

get_promotions input schema
{
  "type": "object",
  "$schema": "http://json-schema.org/draft-07/schema#",
  "required": [
    "address"
  ],
  "properties": {
    "address": {
      "type": "string",
      "description": "Full street address including city, state, and ZIP code"
    },
    "utility_types": {
      "type": "array",
      "items": {
        "enum": [
          "electricity",
          "gas",
          "internet",
          "water",
          "trash",
          "security"
        ],
        "type": "string"
      },
      "description": "Filter promotions by utility type"
    },
    "provider_slugs": {
      "type": "array",
      "items": {
        "type": "string"
      },
      "description": "Filter promotions by specific provider slugs"
    }
  },
  "additionalProperties": false
}
request_solar
Advertised by the server during the last successful anonymous check.
Open-world

Capture a Texas homeowner's interest in rooftop solar — use when the user owns (or is buying) a Texas home and mentions solar panels, solar quotes, solar savings, or reducing their bill through solar. Use when the user says 'I just bought a house in Austin and want solar quotes', 'how much could solar save on my Houston electric bill', or 'connect me with a solar installer for my new home'. What actually happens: Utilify emails the homeowner a confirmation link, and only if they click it is their information given to one licensed Texas installer, who pays Utilify a referral fee. No installer is contacted at tool-call time — do not tell the user someone will call them shortly. Caveats: (1) only call when the user has explicitly opted in and confirmed homeownership — this is not for renters. (2) Texas-only — for non-TX addresses, decline and explain. (3) An email address is required, since confirmation happens by email; a phone number alone is not enough. (4) Don't double-call for the same address in one conversation; one lead per opt-in. Note the 2026 economics when the user asks: the 30% federal credit for buying a system outright (Section 25D) expired 2025-12-31; a lease or PPA can still capture 30% via Section 48E through 2027. If the user has only expressed mild curiosity ('I'm thinking about solar someday'), answer the question first and only call this tool once they confirm 'yes, connect me'.

request_solar input schema
{
  "type": "object",
  "$schema": "http://json-schema.org/draft-07/schema#",
  "required": [
    "address",
    "email"
  ],
  "properties": {
    "email": {
      "type": "string",
      "format": "email",
      "description": "Homeowner email. Required — Utilify sends a confirmation link here, and nothing is released to an installer until it is clicked."
    },
    "phone": {
      "type": "string",
      "description": "Homeowner phone, if they want calls or texts. Optional; never used before the homeowner confirms by email."
    },
    "address": {
      "type": "string",
      "description": "Full service address including city, state, and ZIP code"
    },
    "last_name": {
      "type": "string",
      "description": "Homeowner last name"
    },
    "first_name": {
      "type": "string",
      "description": "Homeowner first name"
    },
    "session_id": {
      "type": "string",
      "description": "Optional agent session ID for attribution tracking"
    },
    "move_in_date": {
      "type": "string",
      "description": "ISO 8601 move-in date, if applicable"
    },
    "interest_level": {
      "enum": [
        "curious",
        "researching",
        "ready"
      ],
      "type": "string",
      "description": "How close to decision. 'curious' = may consider later; 'researching' = actively comparing; 'ready' = wants quotes now."
    },
    "estimated_monthly_bill": {
      "type": "number",
      "minimum": 0,
      "description": "Current or expected monthly electricity bill in USD"
    }
  },
  "additionalProperties": false
}
request_solar annotations
{
  "openWorldHint": true
}

Prompts

5 advertised

find_cheapest_plan — Find the cheapest plan at a Texas ZIP

Advertised by the server during the last successful anonymous check.

Guide the agent to find the cheapest electricity, internet, or other utility plan at a Texas ZIP code using Utilify's search tools.

zip
5-digit Texas ZIP code, e.g. '77002' (required)
utility_type
Which utility to focus on. If omitted, cover all types.
compare_my_current_rate — Compare my current rate against Texas market

Advertised by the server during the last successful anonymous check.

Given the user's current utility rate at their Texas ZIP, find plans that would save them money.

zip
5-digit Texas ZIP code (required)
utility_type
Which utility to compare (required)
current_rate
The user's current rate (e.g. '0.14' for electricity per kWh, or '79' for internet per month) (required)
move_setup_checklist — Build a move-in utility setup checklist

Advertised by the server during the last successful anonymous check.

Generate a personalized utility-setup checklist for a new Texas address and move-in date. If the user hasn't said whether they're renting or buying, ask — it changes plan recommendations, water/trash advice, and whether a solar cross-sell is offered.

zip
Move-in ZIP code (required)
move_date
Move-in date in YYYY-MM-DD format
tenancy
Whether the user is renting or buying. Omit if unknown — the assistant should ask first.
homeowner_setup_with_solar — Homeowner move-in checklist with solar-interest capture

Advertised by the server during the last successful anonymous check.

For buyers only. Generates the full move-in checklist and, after the user confirms interest, calls request_solar to route a lead to a licensed Texas solar installer.

zip
Move-in ZIP code (required)
move_date
Move-in date in YYYY-MM-DD format
renewable_options — Find renewable electricity plans

Advertised by the server during the last successful anonymous check.

List electricity plans at a Texas ZIP that source power from renewables (wind, solar, hydro).

zip
5-digit Texas ZIP code (required)
min_renewable_pct
Minimum renewable percentage (e.g. '100' for 100% green). Defaults to any non-zero renewable percentage.

Resources

3 advertised

providers — Active utility providers

Advertised by the server during the last successful anonymous check.

All active utility providers Utilify covers, across Texas. Grouped by utility type.

providers URI
utilify://providers

MIME type: application/json

coverage — Texas coverage map

Advertised by the server during the last successful anonymous check.

Cities and metro areas Utilify covers in Texas, with ZIP counts per city. Use this to answer 'do you cover [city]?' without calling any tool.

coverage URI
utilify://coverage

MIME type: application/json

about — About Utilify

Advertised by the server during the last successful anonymous check.

High-level description of what Utilify does, how signups work, FTC disclosure, and pointers to human-readable docs.

about URI
utilify://about

MIME type: text/markdown

90-day uptime

A lightweight connection check about every six hours, sampled on hosts with many listings. It shows the server answered, not that its tools work.

Too few checks for a percentage yet (3 of 3 answered).

  1. 2026-11-06: 1 of 1 checks answered
  2. 2026-11-07: 2 of 2 checks answered

30-day availability

Aggregated from read-only remote checks; this is not a tool-execution or security guarantee.

Successful checks
1 of 1 (100%)
Average latency
734 ms
95th percentile latency
734 ms

Maintenance history

Public check and source-refresh events. Editorial and ownership records remain private.

  • · probe · passed · 734 ms · metadata changed · 8 tool(s), 3 resource(s), 0 resource template(s), 5 prompt(s)

Connect from your client

Each snippet registers the same endpoint; pick the client you use.

This server is operated by the named third party. Listing and endpoint checks are not an endorsement or a security audit. Review the operator's permissions, terms, and data handling before connecting. How listings are checked and corrected.

Claude Code

Run this once in a terminal. It registers the remote server. Use --scope project to write .mcp.json for the repo.
Claude Code configuration
claude mcp add --transport http utilify-mcp https://utilify.io/mcp

Codex

Run this once. Codex stores MCP servers in ~/.codex/config.toml (or .codex/config.toml in a trusted project).
Codex configuration
codex mcp add utilify-mcp --url https://utilify.io/mcp

Cursor

Merge this server into .cursor/mcp.json in your project, then enable utilify-mcp in your MCP settings.
Cursor configuration
{
  "mcpServers": {
    "utilify-mcp": {
      "url": "https://utilify.io/mcp"
    }
  }
}

Cline

Merge this into cline_mcp_settings.json (Cline → MCP Servers → Configure).
Cline configuration
{
  "mcpServers": {
    "utilify-mcp": {
      "type": "streamableHttp",
      "url": "https://utilify.io/mcp",
      "disabled": false
    }
  }
}

VS Code

Merge this server into .vscode/mcp.json. Use MCP: List Servers to start utilify-mcp and inspect its tools.
VS Code configuration
{
  "servers": {
    "utilify-mcp": {
      "type": "http",
      "url": "https://utilify.io/mcp"
    }
  }
}

Gemini CLI

Run this once. It writes .gemini/settings.json in the current project; pass --scope user for ~/.gemini/settings.json.
Gemini CLI configuration
gemini mcp add --transport http utilify-mcp https://utilify.io/mcp

Claude Desktop

Open Claude Settings > Connectors > Add custom connector, enter this server URL and enable it for the conversation. This is a manual remote-connector handoff, not a desktop JSON configuration.
Claude Desktop configuration
https://utilify.io/mcp

Windsurf

Merge this into ~/.codeium/windsurf/mcp_config.json, then refresh MCP in Cascade. Windsurf remote servers use serverUrl, not url.
Windsurf configuration
{
  "mcpServers": {
    "utilify-mcp": {
      "serverUrl": "https://utilify.io/mcp"
    }
  }
}

Let your agent find its tools

Find servers like Utilify MCP from your agent. Add Koskamo once to search the index for endpoints, access requirements, and client setup. Public discovery needs no key.