Figma Context MCP
Give your coding agent access to your Figma data. Implement designs in any framework in one-shot.
OneHome (CoreLogic) real-estate access for Claude — search, property details, photos, saved homes
选择你使用的 AI 应用,然后复制设置。
通过 3/3 项检查 · 在你的电脑上运行 · ✓ 命令已检查 2026年11月13日
第一步:你用哪个 AI?
选择你用的应用,步骤会显示在下方。
SettingsDeveloperEdit Config
{
"mcpServers": {
"onehome": {
"command": "npx",
"args": [
"-y",
"onehome-mcp"
],
"env": {
"ONEHOME_TOKEN": "your-value",
"ONEHOME_MAGIC_LINK": "your-value",
"ONEHOME_WS_PORT": "your-value",
"ONEHOME_COMMUNITIES_FILE": "your-value",
"FETCHPROXY_WS_HOST": "your-value",
"FETCHPROXY_IDENTITY_DIR": "your-value"
}
}
}
}只把密钥粘贴到应用的输入框里,不要粘贴到聊天中或发给任何人
用 Onehome MCP 告诉我你能帮我做什么,然后做一件给我看✓ 如果 Claude 说正在使用 Onehome MCP,或回答中出现 Onehome MCP 的工具名称,就表示连接成功
菜单名称已于 2026年11月11日 对照 Anthropic 帮助页面核实 · 你的界面可能因版本略有不同
ChatGPT 暂时无法连接 Onehome MCP
Onehome MCP 需要安装在你的电脑上,而 ChatGPT 只能连接在网上运行的服务器
A · 使用能连接 Onehome MCP 的应用
B · 设计、图片与音频 类中能连接 ChatGPT 的其他服务器
从同类中使用较多的里挑选,仅限用地址即可连接、无需密钥的
可连接 Claude Code,但需要先准备
需要 Onehome MCP 的密钥(在开发者网站创建) · 需要先在电脑上安装 Node.js(只需一次)
打开开发者网站,注册账户并创建 API 密钥,下一步要用。价格和免费方案请看开发者网站。
获取密钥的方法见下方开发者的 README
Mac:按 Command+空格,输入 Terminal · Windows:打开 PowerShell
claude mcp add --scope user onehome --env ONEHOME_TOKEN=your-value --env ONEHOME_MAGIC_LINK=your-value --env ONEHOME_WS_PORT=your-value --env ONEHOME_COMMUNITIES_FILE=your-value --env FETCHPROXY_WS_HOST=your-value --env FETCHPROXY_IDENTITY_DIR=your-value -- npx -y onehome-mcp按 Enter 前,把“your-value”改成你的密钥
只把密钥粘贴到应用的输入框里,不要粘贴到聊天中或发给任何人
应能看到 Onehome MCP 在列表中并显示已连接
用 Onehome MCP 告诉我你能帮我做什么,然后做一件给我看✓ 如果 Claude Code 说正在使用 Onehome MCP,或回答中出现 Onehome MCP 的工具名称,就表示连接成功
菜单名称已于 2026年11月11日 对照 Anthropic 帮助页面核实 · 你的界面可能因版本略有不同
可连接 Cursor,但需要先准备
需要 Onehome MCP 的密钥(在开发者网站创建) · 需要先在电脑上安装 Node.js(只需一次)
打开开发者网站,注册账户并创建 API 密钥,下一步要用。价格和免费方案请看开发者网站。
获取密钥的方法见下方开发者的 README
在 Onehome MCP 的设置中,ONEHOME_TOKEN, ONEHOME_MAGIC_LINK, ONEHOME_WS_PORT, ONEHOME_COMMUNITIES_FILE, FETCHPROXY_WS_HOST, FETCHPROXY_IDENTITY_DIR 还是空的,填入你的密钥并保存
只把密钥粘贴到应用的输入框里,不要粘贴到聊天中或发给任何人
用 Onehome MCP 告诉我你能帮我做什么,然后做一件给我看✓ 如果 Cursor 说正在使用 Onehome MCP,或回答中出现 Onehome MCP 的工具名称,就表示连接成功
菜单名称已于 2026年11月11日 对照 Cursor 帮助页面核实 · 你的界面可能因版本略有不同
可连接 VS Code,但需要先准备
需要 Onehome MCP 的密钥(在开发者网站创建) · 需要先在电脑上安装 Node.js(只需一次)
打开开发者网站,注册账户并创建 API 密钥,下一步要用。价格和免费方案请看开发者网站。
获取密钥的方法见下方开发者的 README
在 Onehome MCP 的设置中,ONEHOME_TOKEN, ONEHOME_MAGIC_LINK, ONEHOME_WS_PORT, ONEHOME_COMMUNITIES_FILE, FETCHPROXY_WS_HOST, FETCHPROXY_IDENTITY_DIR 还是空的,填入你的密钥并保存
只把密钥粘贴到应用的输入框里,不要粘贴到聊天中或发给任何人
用 Onehome MCP 告诉我你能帮我做什么,然后做一件给我看✓ 如果 VS Code 说正在使用 Onehome MCP,或回答中出现 Onehome MCP 的工具名称,就表示连接成功
菜单名称已于 2026年11月11日 对照 VS Code 帮助页面核实 · 你的界面可能因版本略有不同
Claude Code
claude mcp add --scope user onehome --env ONEHOME_TOKEN=your-value --env ONEHOME_MAGIC_LINK=your-value --env ONEHOME_WS_PORT=your-value --env ONEHOME_COMMUNITIES_FILE=your-value --env FETCHPROXY_WS_HOST=your-value --env FETCHPROXY_IDENTITY_DIR=your-value -- npx -y onehome-mcpClaude Desktop (claude_desktop_config.json)
{
"mcpServers": {
"onehome": {
"command": "npx",
"args": [
"-y",
"onehome-mcp"
],
"env": {
"ONEHOME_TOKEN": "your-value",
"ONEHOME_MAGIC_LINK": "your-value",
"ONEHOME_WS_PORT": "your-value",
"ONEHOME_COMMUNITIES_FILE": "your-value",
"FETCHPROXY_WS_HOST": "your-value",
"FETCHPROXY_IDENTITY_DIR": "your-value"
}
}
}
}Cursor (~/.cursor/mcp.json)
{
"mcpServers": {
"onehome": {
"command": "npx",
"args": [
"-y",
"onehome-mcp"
],
"env": {
"ONEHOME_TOKEN": "your-value",
"ONEHOME_MAGIC_LINK": "your-value",
"ONEHOME_WS_PORT": "your-value",
"ONEHOME_COMMUNITIES_FILE": "your-value",
"FETCHPROXY_WS_HOST": "your-value",
"FETCHPROXY_IDENTITY_DIR": "your-value"
}
}
}
}VS Code (mcp.json)
{
"servers": {
"onehome": {
"type": "stdio",
"command": "npx",
"args": [
"-y",
"onehome-mcp"
],
"env": {
"ONEHOME_TOKEN": "your-value",
"ONEHOME_MAGIC_LINK": "your-value",
"ONEHOME_WS_PORT": "your-value",
"ONEHOME_COMMUNITIES_FILE": "your-value",
"FETCHPROXY_WS_HOST": "your-value",
"FETCHPROXY_IDENTITY_DIR": "your-value"
}
}
}
}ONEHOME_TOKEN envONEHOME_MAGIC_LINK envONEHOME_WS_PORT envONEHOME_COMMUNITIES_FILE envFETCHPROXY_WS_HOST envFETCHPROXY_IDENTITY_DIR env这些设置是根据作者在注册中心的条目生成的。如果 README 的写法不同,请以 README 为准。
依据这个服务器的连接方式和各应用自己的文档,检查于 2026年11月10日。
在你的电脑上运行,适用于
ClaudeGooseLM StudioMsty StudioCherry StudioCursorVS Code + GitHub CopilotVisual StudioWindsurf (Devin Desktop)ZedKiroClineContinueJetBrains AI AssistantClaude CodeCodex CLIGemini CLIOpenCodenodecodeWarpLibreChatRaycast
它在你的电脑上运行;安装后,工具列表会显示在你的 AI 应用中。
我们检查的是任何人都能看到的信息;我们没有阅读代码。不适用的检查项不计入总数。 · 检查于 2026年11月13日
注册名称已通过 GitHub 账户 chrischall 验证,该账户拥有此仓库
代码最后更新于3天前
使用 MIT
它在你的电脑上运行,没有互联网端点
在你的电脑上运行,改用本地设置
它在你的电脑上运行;我们只能读取互联网端点的工具列表
提问、分享技巧或报告无法使用。按“有帮助”数量排序。
还没有评价
与注册中心里这个分类中所有活跃的服务器比较。只有当发布者拥有该仓库时,星标数才计入。
它在 3 项适用的基础检查中通过了 3 项。我们没有阅读代码。在添加密钥或令牌之前,请先看看这个服务器要求哪些权限,并使用只具备所需权限的密钥。
注册中心没有列出必需的密钥,不过有些服务器会在首次使用时要求你登录。
它在你的电脑上运行。你的 AI 应用会在需要时启动它,数据不会经过作者的服务器(除非它自己调用在线服务)。
GitHub 仓库最后更新于3天前,最新版本(1.2.1)于8天前进入注册中心。
支持 MCP 的应用,例如 Claude Desktop、Claude Code、Cursor 和 VS Code。你的电脑上还需要有 Node.js。
同一分类中有:Figma Context MCP, AutoClip, Next AI Draw.io
同一分类中其他作者的服务器,按星标数排序。
如何看卡片:↓ 每周下载量i★ GitHub 星标i三大支柱:评价 · 检查 · 使用情况i更新 = 最新版本发布到注册中心的时间i
Give your coding agent access to your Figma data. Implement designs in any framework in one-shot.
draw.io diagrams your AI agent draws on a live browser canvas that you can also edit by hand
按原文从作者的仓库复制。PopNx MCP 没有审查或背书其内容。HTML、图片和脚本已被移除。链接会离开本站。
MCP server for OneHome (CoreLogic) — search the listings your real-estate agent curated for you, fetch property details + photos, compare houses side-by-side, and run mortgage / affordability math from within Claude.
Sister project to zillow-mcp, redfin-mcp, compass-mcp, and homes-mcp. Same tool ergonomics — different upstream auth model.
This project was developed and is maintained by AI (Claude). Use at your own discretion.
OneHome isn't a public listings site. Buyers usually reach it through a magic link an agent emails them — https://portal.onehome.com/...?token=eyJ.... That token query param IS the per-user bearer that the portal SPA hands to every GraphQL request.
So instead of routing every fetch through your signed-in browser tab (like the other realty MCPs), onehome-mcp talks directly to services.onehome.com/graphql from Node, with Authorization: Bearer attached. We support three ways to source that bearer:
| Mode | How to enable | Notes |
|---|---|---|
env_token | ONEHOME_TOKEN= | Paste the raw bearer from devtools Network panel. Most direct. |
magic_link | ONEHOME_MAGIC_LINK=https://portal.onehome.com/...?token=... | Paste the full URL your agent sent — we extract the token param. |
fetchproxy_capture | (no env) + ContextMint Bridge browser extension installed (Chrome: load the release's chrome zip unpacked; Safari isn't available yet — it will ship inside the ContextMint app, so use Chrome for now) + signed-in portal.onehome.com tab | We wait for your tab to fire any GraphQL request, snapshot the Authorization header, and reuse it. |
ContextMint Bridge is the fetchproxy browser extension under its new name, from the same maintainer — fetchproxy's own README (fetchproxy#extension) points to it. Its source is public at nullnet-app/contextmint-bridge: build it yourself, or check a release zip against the .sha256 file published beside it (shasum -a 256 -c contextmint-bridge-chrome- .zip.sha256).
| Tool | What it does |
|---|---|
onehome_get_user | Smallest auth probe — returns your OneHome profile (name, email) and the groups your agent shared. |
onehome_get_groups | List the OneHome "groups" your agent has shared with you (each one a market / curated listing bucket). |
onehome_get_saved_search | Fetch an agent-curated saved search by id — name, filter criteria, polygon, and the OSK listing ids that compose the share. |
onehome_get_saved_search_with_listings | The "show me my saved homes" flow in one round trip — saved search plus its inflated listings. |
onehome_search_properties | Listings within a group; optionally scoped to a saved search. |
onehome_search_suggestions | Free-text suggestion search (address, MLS #) across all feeds. |
onehome_get_by_address | Resolve a single free-text street address to a listing's portal URL + id. |
onehome_resolve_addresses | Bulk-resolve up to 100 structured addresses to portal URLs + listing ids; concurrent, per-row error capture. |
onehome_get_property | Full property record by listing id or portal URL. |
onehome_bulk_get | Fetch up to N listings in one call — one structured row per id, per-row error capture. |
onehome_get_property_photos | Full media gallery — Thumbnail / Medium / Large variants + room descriptions. |
onehome_compare_properties | 2-8 listings side-by-side. Per-row error capture; calls are concurrent. |
onehome_get_schools | Local-Logic primary + high schools near a lat/lng. |
onehome_get_walk_score | Local-Logic walk / transit / bike / car friendliness scores. |
onehome_graphql | Power-user escape hatch — send a raw read-only GraphQL document (queries only; mutations and subscriptions are refused) with variables. |
onehome_calculate_mortgage | Local PITI calculator. Same math as the other realty MCPs. |
onehome_calculate_affordability | Local 28/36 DTI solver — max home price you can afford. |
onehome_set_auth | Add another authenticated session at runtime (magic link / JWT / email-token) for buyers holding shares across multiple agents. |
onehome_set_active_session | Force a specific registered session to be the active one (overrides MLS-suffix routing). |
onehome_get_session_context | List every registered session — auth mode, token expiry, and the group / saved-search / agent scope each bootstrapped. |
onehome_healthcheck | End-to-end auth + GraphQL smoke check with token-expiry diagnostics. |
The simplest path is the published Claude plugin (.mcpb install). Its settings take an optional OneHome magic link or bearer token (both stored as sensitive values); leave both blank to use browser-bridge capture instead. For local dev:
git clone https://github.com/chrischall/onehome-mcp
cd onehome-mcp npm install npm run build
Then point your MCP host at node /abs/path/to/onehome-mcp/dist/bundle.js with one of:
// claude_desktop_config.json
{ "mcpServers": { "onehome-mcp": { "command": "node", "args": ["/abs/path/to/onehome-mcp/dist/bundle.js"], "env": { "ONEHOME_MAGIC_LINK": "https://portal.onehome.com/en-US/properties/map?token=eyJ..." } } } }
npm test # vitest, mocked transport, no network
npm run test:watch npm run test:coverage npx tsc --noEmit npm run build # tsc --noEmit + esbuild → dist/bundle.js
Tests use a FakeTransport (in tests/helpers.ts) that registers per-operationName handlers — there's no live network in the test suite. The tests/index.test.ts smoke check loads the same tool registrations src/index.ts uses against an in-memory MCP client/server pair, so "I wrote the tool file but forgot to wire it up" mistakes fail loudly.
MIT.