HireNimbus home services MCP

MCP其他

提供方 Hire-Nimbus

其他 HTTP · 远程 OAuth 授权 社区 / 第三方 CodexZed
查看接入方式

Home Services MCP by HireNimbus lets AI agents find, compare, and book verified local pros for handyman, renovation, HVAC, plumbing, electrical, and landscaping jobs in supported US metro markets.

一句话选型结论

按资料字段整理

HireNimbus home services MCP 属于其他类 MCP 服务器,HTTP · 远程,OAuth 授权,可直接接入 Codex、Zed,有可直接复制的远程端点配置。接入前先确认权限范围;涉及写入、删除或付款的操作,建议先在测试环境验证。

分类其他 传输方式HTTP · 远程 鉴权OAuth 授权 部署方式远程部署
GitHub 星标 未标注 仓库热度,无公开仓库时显示未标注
工具数 未标注 暴露给模型的工具数量
资源 / 提示词 0 / 0 资源与提示词模板数量
维护方 社区 / 第三方 核验等级 仅资料核对

工具与能力

其他
数量来自来源目录的标注,具体工具清单以官方文档为准
工具数量未标注暴露给模型可调用的工具个数
资源数量0可读取的资源条目
提示词数量0内置提示词模板数量

能力标签

home services local services booking ai agent tools marketplace

支持客户端

适用场景

home serviceslocal servicesbooking

安装与配置

HTTP · 远程 OAuth 授权
连远程 HTTPS 端点,通常为 Streamable HTTP
https://mcp.hirenimbus.com/mcp

把它填进客户端的 MCP 配置即可,不需要在本地安装运行时。

  1. 1
    准备运行环境

    确认你的客户端支持远程端点,并拿到服务地址。

  2. 2
    安装服务

    复制上面的安装命令执行;命令里带占位符的位置,换成自己的密钥或路径。

  3. 3
    写入客户端配置

    在客户端的 MCP 配置里填好启动命令和参数,保存后完全退出客户端再打开,让新配置生效。

  4. 4
    验证是否可用

    连接成功后随便调一个只读工具,确认能返回结果,再接入正式流程。

典型使用场景

3 类
按分类与标签整理的常见用法,具体以官方文档为准
接入外部数据

把外部系统的数据接进对话。

自动化重复操作

把固定步骤交给模型跑。

补充工具能力

给模型补上它原本没有的能力。

选择建议

选之前先看这几条
按条目字段给出的判断,不替你决定用不用

值得选的地方

  • 有现成的安装命令,不用自己找入口,照着跑就能起服务。
  • 已适配 Codex、Zed,换客户端不用重新研究配置。

先想清楚的地方

  • 远程端点依赖网络与服务方可用性,注意密钥与调用额度。
  • 使用前要准备好OAuth 授权对应的凭据,并按最小权限配置。
  • 资料没标注工具数量,实际能力要装好后确认。
  • 版本更新与行为细节以官方仓库为准。

更适合

  • 需要在其他场景里让模型直接调用外部能力的人。
  • 已经在用 Codex、Zed 的用户,接入路径最短。
  • 想先快速试一下、能接受在本地或自有环境跑服务的人。

不太适合

  • 不方便管理密钥或第三方授权的人。
  • 需要厂商级 SLA 和技术支持的生产环境。

同类对比

6 个同类
同分类里挑最接近的几条,字段以各自详情页为准
MCP 服务器工具数传输方式部署方式安装命令最后核验
HireNimbus home services MCP当前 未标注 HTTP · 远程 远程部署 有 未标注
gemini-cli 未标注 stdio · 本地进程 本地部署 有 2026-04-13
ext-apps 未标注 stdio · 本地进程 本地部署 有 2026-04-19
northcinder 未标注 stdio · 本地进程 本地部署 有 2026-08-23
fastctx 未标注 stdio · 本地进程 本地部署 有 2026-08-23
quickstart-resources 未标注 stdio · 本地进程 本地部署 有 2026-04-12

服务器档案

其他
字段来自项目仓库与公开索引,中文说明由本站标注
提供方Hire-Nimbus上游标注的维护方 Hire-Nimbus
分类其他本站按上游分类展示
连接方式HTTP · 远程连远程 HTTPS 端点,通常为 Streamable HTTP
鉴权方式OAuth 授权远程服务建议用最小权限凭据
维护方社区 / 第三方核验等级 仅资料核对
包名 / 运行时未标注 · Cross-platform本地安装时用到的包标识与运行时
部署类型远程部署上游给出的部署形态
最近核验未标注上游最后核验时间

详细介绍

8.3 KB
来自项目仓库与上游目录的原文,未做删改

Home Services MCP Server

An open-source, self-hostable Model Context Protocol server for home-service
discovery, provider profiles and reviews, homeowner identity, booking
requests, and booking follow-up. The server supplies the workflow and MCP
interface; each operator supplies the APIs, data, credentials, branding, and
deployment environment.

This repository contains no customer data, provider data, API keys, or private
production endpoints. It includes one documented public hosted MCP fallback
for convenience; operators can replace it with their own endpoint and
credentials for a fully self-hosted deployment.

What is included

  • Streamable HTTP MCP transport at /mcp (the root endpoint is also mapped for
    clients that require it).
  • OAuth 2.0 authorization-code flow with PKCE, when OAuth credentials are
    configured.
  • Provider search, details, reviews, homeowner profile, booking, previous-job,
    booking-status, and rebooking workflows.
  • Optional category-specific find/book tool aliases.
  • Input validation, PII-aware logging, outbound host allowlisting, rate
    limiting, and circuit-breaker behavior.
  • Local ASGI development, a generic Docker image, and AWS SAM/Lambda
    deployment configuration.

The public MCP contract is intentionally stable. Operators can replace the
backends without changing the client-facing tool names or workflow semantics.

Quick start```bash

python3.10 -m venv .venv
source .venv/bin/activate
pip install -r requirements.txt
cp .env.example .env

The default setup uses the hosted MCP relay. For self-hosting, edit .env

with your own upstream MCP endpoint, API URLs, and credentials.

uvicorn src.main:app --reload --port 8000


The server is then available at `http://localhost:8000/mcp`.

Before opening a release or marketplace review, run the checks in
docs/RELEASE_CHECKLIST.md, including:

    python3 scripts/audit_public_release.py

For a container build:```bash
docker build -t home-services-mcp .
docker run --env-file .env -p 8000:8080 home-services-mcp

For AWS SAM, provide deployment-specific values through parameter overrides
or your secret manager. Do not place secrets in template.yaml, samconfig
files, container layers, or source control.

Configuration

Start with .env.example. Empty optional endpoint variables
disable the related capability. The upstream MCP relay is the exception: it
defaults to the documented public hosted service and can be overridden.

Core operator-owned endpoints:

Variable Purpose
PROVIDERS_API Provider search endpoint
COORDS_RESOLVE_API Text/coordinate location resolver
ZIP_RESOLVE_API Postal-code location resolver
GEOCODING_API / GEOCODING_API_KEY Optional address enrichment integration
REVIEWS_API Provider profile and review endpoint
BOOKING_API Booking/request creation endpoint
SERVICE_REQUESTS_URL Booking history/status endpoint
SERVICE_REQUESTS_METADATA_URL Optional endpoint for notification metadata
PROFILE_LOOKUP_API Optional phone/profile lookup endpoint
AUTH_WEBHOOK_URL Optional OTP send/verify endpoint
HOMEOWNER_PROFILE_API Optional profile-by-token endpoint
CANCEL_BOOKING_API Optional authenticated, ownership-enforcing cancellation endpoint

Optional integrations include notification endpoints, operator persistence,
monitoring webhooks, OAuth, and the OpenAI app verification challenge. All
URLs and secrets must be supplied by the operator.

OAuth interoperability

When OAuth is enabled, access and refresh tokens use separate ES256 signing
keys; the access-token public verification key
is exposed through the metadata jwks_uri. Set
OAUTH_ALLOWED_REDIRECT_URIS to the exact hosted or claimed-scheme callbacks
your clients use. Native clients may register HTTP loopback callbacks on
localhost, 127.0.0.1, or [::1] with any explicit port; these do not need
to be enumerated because native apps commonly bind an ephemeral port. Other
custom schemes (including arbitrary cursor:// or vscode:// callbacks) are
rejected unless their complete URI is explicitly configured, since dynamic
registration alone does not prove ownership of a private scheme. Enable
OAUTH_DYNAMIC_CLIENT_REGISTRATION_ENABLED to let public PKCE clients obtain
unique persisted client ids from /oauth/register; the legacy configured
client id and unregistered PKCE clients remain supported.

Use at least 32 cryptographically random bytes for OAUTH_CLIENT_SECRET. The
server derives domain-separated ES256 keys from that secret so stateless
instances publish and verify the same access-token key without reusing it for
refresh-token signatures. OAuth tokens carry an opaque homeowner session id;
profile PII and upstream bearer credentials remain in the server-side state
store.

Upstream MCP relay

By default, the server relays requests from /upstream/mcp to
https://mcp.hirenimbus.com/mcp. Set UPSTREAM_MCP_URL to use an
operator-controlled MCP service instead. If the selected upstream requires
authentication, set UPSTREAM_MCP_AUTH_TOKEN; no token is bundled, and
inbound client authorization is never forwarded automatically.

Review the selected upstream's data handling, retention, terms, and access
policy before sending user requests to it. For a fully self-hosted deployment,
replace the default upstream and configure the operator-owned business APIs.

Security and data ownership

The server is a programmable integration layer, not a data processor with a
built-in tenant. Operators are responsible for:

  • API authorization, tenant isolation, data retention, backups, and deletion;
  • secret storage, rotation, least-privilege scopes, and production network
    policy;
  • privacy notices, terms, support contacts, regional/legal requirements, and
    any third-party processing disclosures;
  • confirming that configured APIs do not return more personal information than
    the MCP client needs.

The default development configuration leaves external business APIs empty.
Production deployments should fail closed when a required capability is not
configured, use durable shared state for OAuth and idempotency, and keep
monitoring disabled unless its endpoint is explicitly configured. Set
AUTH_STATE_TABLE_NAME to a shared DynamoDB table and
REQUIRE_DURABLE_STATE=true for multi-instance OAuth or booking workloads.
Without those settings, the development fallback is process-local and does
not provide cross-instance replay protection.

Confirmed booking calls accept an optional client-generated
idempotency_key. Clients should reuse that key after a timeout. The
configured booking API should also honor the same field; the server never
retries an ambiguous booking request automatically.

Testing

Install the development dependencies and run:bash pytest -q ruff check .

Tests must use mocks or local fixtures for external integrations. They must
not call a live operator endpoint.

Marketplace package

The server and portable workflow skills are independent of any hosted
deployment. A first-party distribution can add a separate marketplace
manifest that points to its own hosted MCP URL and branded app, without
putting those values in this repository.

The portable home-service workflow is available at
skills/home-service-concierge/SKILL.md.
Its app handoff uses the operator-configured APP_LINK value.

Tools

  • get_my_profile — Load saved homeowner profile/address when already signed in
  • search_providers — Search verified pros outside dedicated find_* categories
  • get_provider_details — Full provider profile by slug
  • get_provider_reviews — Reviews for a provider
  • create_booking — Preview/submit booking after a pro is chosen
  • get_previous_jobs — Past/active jobs (auth)
  • get_booking_status — Booking status by id (auth)
  • book_same_pro_again — Rebook a previous pro (auth)
  • cancel_booking — Cancel a booking (auth)
  • find_handyman / book_handyman
  • find_hvac / book_hvac
  • find_plumber / book_plumber
  • find_electrician / book_electrician
  • find_renovation / book_renovation
  • get_more_tools — Discover additional specialized tools

License

Licensed under the Apache License 2.0. Product names, trademarks,
private services, and operator integrations are not included as defaults by
this codebase. The documented public hosted MCP fallback is an intentional
exception and does not include credentials or customer data.

常见问题

8 问
答案由本站依据条目字段整理,不引用上游原文
HireNimbus home services MCP 怎么安装?

在客户端按下面的安装命令接入:https://mcp.hirenimbus.com/mcp。装完在客户端配置里引用同一个包或端点。

HireNimbus home services MCP 怎么在 Codex、Zed 里配置?

它的传输方式是HTTP · 远程,在客户端的 MCP 配置里填好启动命令和参数,保存后完全退出客户端再打开,配置才会生效。

HireNimbus home services MCP 收费吗?

本站不代收费用,也没有标注具体价格。是否收费取决于服务本身和背后的接口额度,正式使用前按官方说明确认。

HireNimbus home services MCP 需要 API Key 吗?

资料标注需要OAuth 授权认证,使用前准备好对应凭据,并按最小权限配置。

HireNimbus home services MCP 支持哪些客户端?

资料标注支持 Codex、Zed;其他客户端只要能配置 MCP Server,也能用同样的命令或地址接入。

HireNimbus home services MCP 能提供哪些能力?

资料显示能力标签包括 home services、local services、booking、ai agent tools、marketplace。具体工具清单以官方文档为准。

HireNimbus home services MCP 需要什么运行环境?

运行时为 Cross-platform;属于远程端点,不需要在本地装运行时。

HireNimbus home services MCP 是本地还是远程?

它是远程端点,连服务地址即可。传输方式为HTTP · 远程。

热门专题

按标签挑服务器
全部专题 →

服务器信息以作者仓库与官方文档为准;分类、传输方式与鉴权方式的中文说明为中文整理,最近核验 未标注。