Interact with Microsoft 365 and Office services through the Microsoft Graph API.
MaidCentral MCP by usefulapi 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
Read services, prices and open dates; create leads, quotes, bookings and notes in MaidCentral.
Quickstart
# 1 — add it to Claude Code
claude mcp add --scope user --transport http maidcentral-mcp-by-usefulapi https://maidcentral.usefulapi.io/mcp
# 2 — ask your agent for something these tools do
# maidcentral_list_scope_groups, maidcentral_list_scopes, maidcentral_list_scope_frequencies and 17 more
MaidCentral MCP by usefulapi 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 maidcentral-mcp-by-usefulapi https://maidcentral.usefulapi.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.
20 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.
List service categories (scope groups) with their scopes of work and frequency ids. Start here: the ids feed quotes, pricing and bookings. API: GET /api/Lead/ScopeGroups.
No parameter schema on file.
List the scopes of work (and frequencies) of one scope group. API: GET /api/Lead/Scopes.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| scope_group_id | integer | yes | Scope group id. |
List the frequency options (one-time, weekly, ...) of one scope. API: GET /api/Lead/ScopeFrequencies.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| scope_id | integer | yes | Scope id. |
List the questions (home size, bedrooms, ...) and answer options for one or more scopes. Required questions must be answered in quotes and pricing. API: GET /api/Lead/Questions.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| scope_ids | array | yes | Scope ids. |
List the extras, discounts and other rate modifications available for a scope group. API: GET /api/Lead/RateModifications.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| scope_group_id | integer | yes | Scope group id. |
List dates on which a quoted job of a given length or price can be booked for a scope group. Give hours or amount. API: GET /api/Lead/Availability.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| scope_group_id | integer | yes | Scope group id. |
| hours | number | no | Job length in hours (hours or amount is required). |
| amount | number | no | Job amount (hours or amount is required). |
| start_date | string | no | Start date, ISO 8601. Default today. |
| end_date | string | no | End date, ISO 8601. Default one month from today. |
List the postal codes the company serves, with their home zone. API: GET /api/Lead/PostalCodes.
No parameter schema on file.
List customer (lead) sources. API: GET /api/Lead/CustomerSources.
No parameter schema on file.
List billing terms usable when booking. API: GET /api/Lead/BillingTerms.
No parameter schema on file.
List teams that jobs can be scheduled to. API: GET /api/Lead/Teams.
No parameter schema on file.
List tags with their category ids (lead tags = category 8, service set tags = 5, first job tags = 6). API: GET /api/Lead/Tags.
No parameter schema on file.
List note types (Email = 1, Note = 2, PhoneCall = 3, TextMessage = 4). API: GET /api/Note/Types.
No parameter schema on file.
Get a lead by id: contact details, status, source, scope group and addresses. API: GET /api/Lead/Lead.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| lead_id | integer | yes | Lead id. |
Get a quote by id: status, addresses, and per-scope and per-frequency prices, hours and booked state. API: GET /api/Lead/Quote.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| quote_id | string | yes | Quote id (uuid). |
Calculate a price for scopes, frequencies, extras and question answers without creating a lead or quote. Stores nothing. API: POST /api/Lead/CalculatePrice.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| scope_group_id | integer | yes | Scope group id. |
| postal_code | string | no | Service postal code. |
| scopes_of_work | array | yes | Scopes and frequencies to price. |
| questions | array | yes | Answers to the scope questions (use [] if none). |
WRITE: create a lead, or update one when lead_id is given. The postal code must be in a home zone. By default MaidCentral may send the lead email, add the lead to campaigns and trigger webhooks: set send_lead_email, add_to_campaigns and trigger_webhook to false to avoid that. Without allow_duplicates, a matching contact links to the existing lead. API: POST /api/Lead/CreateOrUpdate.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| first_name | string | yes | — |
| last_name | string | yes | — |
| string | yes | — | |
| phone | string | yes | — |
| postal_code | string | yes | Must be inside the company's home zones. |
| lead_id | integer | no | Existing lead id to update. |
| notes | string | no | One note to attach to the lead. |
| customer_source_id | integer | no | From maidcentral_list_customer_sources. |
| lead_tag_ids | array | no | Tag ids of category 8 (maidcentral_list_tags). |
| send_lead_email | boolean | no | Send the lead email (vendor default true). |
| add_to_campaigns | boolean | no | Add to MaidCentral campaigns (vendor default true). |
| trigger_webhook | boolean | no | Trigger Keap/Zapier webhooks (vendor default true). |
| allow_duplicates | boolean | no | Create a new lead even when contact info matches (vendor default false). |
| utm_source | string | no | — |
| utm_medium | string | no | — |
| utm_campaign | string | no | — |
| utm_term | string | no | — |
| utm_content | string | no | — |
WRITE: create a quote for a lead (or update one when quote_id is given) with service address, scopes, frequencies and question answers. Optionally emails the quote 5 minutes later (send_quote_email, default false). API: POST /api/Lead/CreateOrUpdateQuote.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| lead_id | integer | yes | Lead id (from maidcentral_create_or_update_lead). |
| quote_id | string | no | Existing quote id to update. |
| scope_group_id | integer | yes | — |
| home_address1 | string | yes | — |
| home_address2 | string | no | — |
| home_city | string | yes | — |
| home_region | string | yes | 2-letter state or region code. |
| home_postal_code | string | yes | — |
| billing_address1 | string | no | Optional billing address (default: the service address). |
| billing_address2 | string | no | — |
| billing_city | string | no | — |
| billing_region | string | no | — |
| billing_postal_code | string | no | — |
| scopes_of_work | array | yes | — |
| questions | array | yes | Answers to the scope questions (use [] if none). |
| send_quote_email | boolean | no | Email the quote to the lead after 5 minutes. |
| add_to_campaigns | boolean | no | — |
| trigger_webhook | boolean | no | — |
WRITE: convert a quote into a customer and schedule the first job on first_job_date. Check dates with maidcentral_list_available_dates first. Booking emails default to the vendor setting: set send_booked_email and send_customer_portal_invite to false to stay silent. API: POST /api/Lead/BookQuote.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| lead_id | integer | yes | — |
| quote_id | string | yes | — |
| scope_group_id | integer | yes | — |
| scopes_of_work | array | yes | — |
| billing_terms_id | integer | no | From maidcentral_list_billing_terms. |
| send_booked_email | boolean | no | — |
| send_customer_portal_invite | boolean | no | — |
| add_to_campaigns | boolean | no | — |
| trigger_webhook | boolean | no | — |
WRITE: add a note (or logged email, call, text) to a quote, customer or employee. Give entity_id with entity_type_id, or entity_contact_info (email or phone). API: POST /api/Note/Create.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| content | string | yes | Note text. |
| entity_type_id | integer | no | Quote = 0, Customer = 1, Employee = 2. |
| entity_id | integer | no | Id of the entity (needs entity_type_id). |
| entity_contact_info | string | no | Email or phone; searched in customers, leads, then employees. |
| note_type_id | integer | no | Email = 1, Note = 2 (default), PhoneCall = 3, TextMessage = 4. |
| subject | string | no | Required unless the note type is Email. |
| create_ticket | boolean | no | For communication notes: also create a ticket. |
| communication_direction_id | integer | no | InternalNote = 0 (default), Incoming = 1, Outgoing = 2. |
WRITE: attach UTM campaign data to a lead or quote. Give lead_id, email or phone. API: POST /api/Lead/Utm.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| lead_id | integer | no | — |
| string | no | — | |
| phone | string | no | — |
| utm_source | string | no | — |
| utm_medium | string | no | — |
| utm_campaign | string | no | — |
| utm_term | string | no | — |
| utm_content | string | no | — |
- 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 MaidCentral MCP by usefulapi 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.
| Term | Level | What it prices | Points |
|---|---|---|---|
| capability-exposure | moderate | capability blast radius (moderate) — client exposure if the model is manipulated | −3 |
| coverage-honesty | manifest | inspection depth (manifest) — how much of the target the scan could see | −4 |
What the scan could actually read
A grade is only as meaningful as its coverage, so the scanner publishes its own depth before it publishes its result.
The scan read each tool’s name, description, input schema and annotations exactly as the server listed them the last time it answered us; no code was reviewed. We ask the server again about once a month, and a list that changed is graded again.
The implementation source was not read — this reflects the declared tool metadata only.
Capability — what it could do if the model were manipulated
Tags derived from each tool’s schema and the implementation, not from what the tool calls itself. moderate is the level these add up to.
| Tool | Capability tags | Why the tag was assigned |
|---|---|---|
| maidcentral_list_scope_groups | no tags | |
| maidcentral_list_scopes | no tags | |
| maidcentral_list_scope_frequencies | no tags | |
| maidcentral_list_questions | no tags | |
| maidcentral_list_rate_modifications | no tags | |
| maidcentral_list_available_dates | no tags | |
| maidcentral_list_postal_codes | no tags | |
| maidcentral_list_customer_sources | no tags | |
| maidcentral_list_billing_terms | no tags | |
| maidcentral_list_teams | no tags | |
| maidcentral_list_tags | no tags | |
| maidcentral_list_note_types | no tags | |
| maidcentral_get_lead | no tags | |
| maidcentral_get_quote | no tags | |
| maidcentral_calculate_price | no tags | |
| maidcentral_create_or_update_lead | external-sinkstate-write | external-sink: keyword "webhook", parameter "webhook"; state-write: declares destructiveHint: true |
| maidcentral_create_or_update_quote | external-sinkstate-write | external-sink: parameter "webhook"; state-write: declares destructiveHint: true |
| maidcentral_book_quote | external-sinkstate-write | external-sink: parameter "webhook"; state-write: declares destructiveHint: true |
| maidcentral_create_note | state-write | state-write: declares destructiveHint: true |
| maidcentral_add_utm_data | no tags |
Toxic-flow graph
The lethal trifecta, checked as a graph rather than as a checklist: untrusted input, a sensitive source and an external sink have to meet before there is a path worth worrying about.
The public result for this release does not print the flow graph, so there is nothing to show here. That is not the same as "no paths were found": what the scan did read is above, under coverage.
Supply chain and provenance
This is the first scan of this surface here, so there is nothing yet to compare it against.
Every result on this tab comes from one deterministic pass over the published package — offline, rule by rule, and auditable line by line above. Same methodology version, same bytes, same score.
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 1.3.5.
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 MaidCentral MCP by usefulapi 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.