Comprehensive Model Context Protocol server for managing Home Assistant through AI assistants.
Utilify is installed from its publisher's own source and answers where it runs, so this marketplace is not in the path of a single call. There is no address here to send one to, and a panel that pretended otherwise would be showing you an answer we made up. Install it and call it from your own client — the Installation tab has the entry for each one.
What it does
AI agents compare and sign up for Texas utility plans: electricity, internet, gas, water, trash.
Quickstart
# 1 — add it to Claude Code
claude mcp add --scope user --transport http utilify-mcp https://utilify.io/mcp
# 2 — ask your agent for something these tools do
# search_utility_providers, get_provider_details, compare_providers and 5 more
Utilify costs nothing on mcprush: there is no plan to choose here, no cap to set and nothing mcprush can bill you for.
Collected from a public index. Nobody has claimed this account, so nothing here was written by its author — claim it if it is yours.
Where are you running it?
Every route below installs the same thing and ends at the same approval screen. Nothing here runs on your machine and nothing runs on ours: this server answers at its publisher’s own address, and what you install is the connection straight to it.
This is a public server: it answers at its publisher’s own address and this marketplace is not in the path. Claude Code registers it in one command; --scope user makes it available in every project. The transport below is http, as the publisher's own manifest declares it.
claude mcp add --scope user --transport http utilify-mcp https://utilify.io/mcpReconnect, or start a new session, and the tools appear in the model’s tool list.
One config entry pointing straight at the publisher’s own address — this marketplace is not in the path, and nothing from this listing executes on your machine.
8 tools, with what each one reads, writes and reaches shown before you agree — the same list on every route above. Read the tool surface.
Tool surface
What the model actually sees. Descriptions are diffed on every release — see version history.
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 j
| Parameter | Type | Required | Notes |
|---|---|---|---|
| address | string | yes | Full street address including city, state, and ZIP code |
| utility_types | array | no | Filter by utility types. If omitted, returns all available types. |
| tenancy | string | no | Whether the user is renting or buying. Changes plan preferences and enables homeowner-only cross-sells (solar). |
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, ear
| Parameter | Type | Required | Notes |
|---|---|---|---|
| provider_slug | string | yes | The provider slug identifier |
| zip_code | string | no | ZIP code to check plan availability and pricing |
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
| Parameter | Type | Required | Notes |
|---|---|---|---|
| provider_slugs | array | yes | Provider slugs to compare (2-5) |
| address | string | yes | Full street address for plan availability |
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
| Parameter | Type | Required | Notes |
|---|---|---|---|
| provider_id | string | yes | The provider to sign up with. Accepts either the provider UUID (from search_utility_providers) or the provider slug (e.g. "chariot-energy"). |
| plan_id | string | yes | The specific plan to enroll in |
| address | string | yes | Full service address including city, state, and ZIP code |
| move_in_date | string | yes | ISO 8601 date for desired service start |
| customer_info | object | yes | Customer contact information |
| session_id | string | no | Optional session ID for tracking |
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 fro
| Parameter | Type | Required | Notes |
|---|---|---|---|
| signup_id | string | yes | The signup ID returned by initiate_signup |
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
| Parameter | Type | Required | Notes |
|---|---|---|---|
| address | string | yes | Full move-in address including city, state, and ZIP code |
| move_date | string | no | ISO 8601 date for the planned move-in |
| tenancy | string | no | Whether the user is renting or buying their new place. Shapes the checklist and unlocks homeowner cross-sells. |
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 disco
| Parameter | Type | Required | Notes |
|---|---|---|---|
| address | string | yes | Full street address including city, state, and ZIP code |
| utility_types | array | no | Filter promotions by utility type |
| provider_slugs | array | no | Filter promotions by specific provider slugs |
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 a
| Parameter | Type | Required | Notes |
|---|---|---|---|
| address | string | yes | Full service address including city, state, and ZIP code |
| string | yes | Homeowner email. Required — Utilify sends a confirmation link here, and nothing is released to an installer until it is clicked. | |
| phone | string | no | Homeowner phone, if they want calls or texts. Optional; never used before the homeowner confirms by email. |
| first_name | string | no | Homeowner first name |
| last_name | string | no | Homeowner last name |
| move_in_date | string | no | ISO 8601 move-in date, if applicable |
| estimated_monthly_bill | number | no | Current or expected monthly electricity bill in USD |
| interest_level | string | no | How close to decision. 'curious' = may consider later; 'researching' = actively comparing; 'ready' = wants quotes now. |
| session_id | string | no | Optional agent session ID for attribution tracking |
- Every tool — any call limit is its publisher’s, not ours
- No card, and mcprush charges nothing for it
- Runs at its publisher’s own address — this marketplace is not in the path
- Nothing to cap, because mcprush bills nothing
What counts against your monthly calls
| Tool | Unit | Calls used | Out of the allowance |
|---|
Nothing here is billable: mcprush charges nothing to install Utilify or to call it, at any volume.
Two independent axes, because powerful and malicious are different questions. The grade is threat only. The capability level is blast radius, and it is never a penalty on the grade — it is priced as one subtract-only term in the score, where you can see it.
This listing is an address its publisher runs, and you connect to it directly — this marketplace is not in the path. The scanner reads packages and public source, and an address is neither: the repository linked on this page is where this record was collected from, not a copy of what the address serves, so it is not graded in its place. So there is no grade — not a withheld one, an unmeasured one.
Release history
This is an address its publisher runs: which release it serves is theirs to choose, so there is nothing here to pin. The history below is for reading; the current release on file is 0.1.0.
No release note was published with this version.
One review per account, from a signed-in account that does not publish this listing. Nothing else is asked — you can say what you think before you install it. Publishers can reply once per review, and a review can be edited or deleted by whoever wrote it.
Any signed-in account that does not publish Utilify can review it, once — before installing it or after. A review from an account that has installed it is marked as one.
Nobody has reviewed this listing. The rating on the card is the mean of the reviews written here and nothing else, so there is no rating until somebody writes the first — which takes a signed-in account that does not publish it, and nothing else.