Figma Context MCP
Give your coding agent access to your Figma data. Implement designs in any framework in one-shot.
Descripción del creador (original en inglés)
OneHome (CoreLogic) real-estate access for Claude — search, property details, photos, saved homes
Estos tres nunca se combinan en una sola puntuación: las opiniones, las mediciones y la popularidad son cosas distintas.
Todavía no escribimos un resumen sencillo para este. Abajo están los datos que leímos del registro.
Elige la app de IA que usas y copia la configuración.
ONEHOME_TOKEN, ONEHOME_MAGIC_LINK, ONEHOME_WS_PORT, ONEHOME_COMMUNITIES_FILE, FETCHPROXY_WS_HOST, FETCHPROXY_IDENTITY_DIRNecesitas
¿Qué app usas?
Elige tu app arriba. La recordamos, así que la próxima vez el botón dirá “Instalar en …”.
Abre Claude Desktop → Settings → Developer → Edit Config y pega esto en 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"
}
}
}
}Ejecuta esto en tu terminal
claude mcp add 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-mcpCompleta los valores vacíos antes de ejecutarlo.
Pégalo en .cursor/mcp.json de tu proyecto, o en ~/.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"
}
}
}
}Tu navegador te pide permiso para abrir la app; luego la app muestra la configuración y te pide confirmar. Los valores de las claves quedan vacíos para que los completes tú.
Pégalo en .vscode/mcp.json de tu proyecto
{
"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"
}
}
}
}Tu navegador te pide permiso para abrir la app; luego la app muestra la configuración y te pide confirmar. Los valores de las claves quedan vacíos para que los completes tú.
Este se ejecuta en tu computadora, y ChatGPT solo puede conectarse a servidores en internet. Elige otra app.
Tu elección se guarda en una cookie en este dispositivo; no necesitas cuenta.
ONEHOME_TOKEN envONEHOME_MAGIC_LINK envONEHOME_WS_PORT envONEHOME_COMMUNITIES_FILE envFETCHPROXY_WS_HOST envFETCHPROXY_IDENTITY_DIR envEsta configuración se genera a partir de la ficha del creador en el registro. Si el README dice otra cosa, sigue el README.
Se ejecuta en tu computadora; la lista de herramientas aparece en tu app de IA después de instalarlo.
Revisamos información que cualquiera puede ver; no hemos leído el código. Las revisiones que no aplican no se cuentan. · Revisado el 8 nov 2026
El nombre en el registro se verificó con la cuenta de GitHub chrischall, dueña del repo
Todavía no hemos leído este repo en GitHub
Todavía no hemos leído este repo en GitHub
Este se ejecuta en tu computadora; no hay endpoint en internet
Se ejecuta en tu computadora y usa ajustes locales en su lugar
Se ejecuta en tu computadora; solo podemos leer listas de herramientas de endpoints en internet
Comparado con todos los servidores activos de esta categoría en el registro. Las estrellas solo cuentan cuando quien lo publica es dueño del repo.
Superó 1 de 1 revisiones básicas aplicables. No hemos leído el código. Antes de agregar una clave o un token, revisa qué acceso pide el servidor y usa una clave que tenga solo los permisos que necesitas.
El registro no indica ninguna clave obligatoria, aunque algunos servidores te piden iniciar sesión la primera vez que los usas.
Se ejecuta en tu computadora. Tu app de IA lo inicia cuando hace falta, y los datos no pasan por los servidores del creador (a menos que el propio servidor llame a un servicio en línea).
El repo de GitHub cambió por última vez –, y la última versión (1.2.1) llegó al registro hace 4 días.
Las apps compatibles con MCP, como Claude Desktop, Claude Code, Cursor y VS Code. También necesitas Node.js en tu computadora.
En la misma categoría: Figma Context MCP, Claude Real Video, Figma MCP Server
Servidores de la misma categoría hechos por otros creadores, ordenados por estrellas.
Cómo leer una tarjeta:↓ Descargas por semanai★ Estrellas de GitHubiTres pilares: reseñas · revisiones · usoiActualizado = fecha en que se publicó la última versión en el registroi
Give your coding agent access to your Figma data. Implement designs in any framework in one-shot.
Let any LLM watch a video locally — and search everything it has ever watched.
The Figma MCP server brings Figma design context directly into your AI workflow.
Copiado tal cual del repo del creador. PopNx MCP no lo ha revisado ni lo respalda. Se quitaron HTML, imágenes y scripts. Los enlaces llevan fuera de este sitio.
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.