Space Context MCP server
2026년 10월 28일 커밋AI 어시스턴트가 촬영된 물리적 공간에 접근하여 검색 및 분석을 수행하며, 스캔 데이터를 비교하거나 사진 증거를 확인할 수 있도록 지원합니다.
다른 이름 finikoslab/spacecontext, spacecontext
- 스타
- 0
- Tools
- 13
- 다운로드, 30일
- —
- 최신 버전
- 0.2.1
- 마지막 커밋
- 2026년 10월 28일
- 라이선스
- MIT
Space Context MCP란?
AI 어시스턴트가 촬영된 물리적 공간에 접근하여 검색 및 분석을 수행하며, 스캔 데이터를 비교하거나 사진 증거를 확인할 수 있도록 지원합니다. 13개 도구를 제공합니다. 예: list_spaces, search_spaces, get_space.
프로젝트 README에서 생성된 요약
Space Context MCP server 정보
Space Context는 AI 어시스턴트를 통해 촬영된 물리적 환경을 분석할 수 있게 해줍니다. 이 원격 MCP server는 Claude, ChatGPT, Cursor, VS Code와 같은 클라이언트를 사용자의 기록된 공간에 연결하여, 어시스턴트가 시각적 데이터를 나열, 검색 및 쿼리할 수 있도록 합니다. 아이템, 문제 및 위치에 대한 상세 정보를 제공하며, 발견된 사항이 독립적인 사진 확인을 통해 검증되었는지 여부도 명시합니다.
사용자는 OAuth 2.1을 통해 연결하며, Google, Apple 또는 이메일로 로그인하여 원본 키를 공유하지 않고도 접근 권한을 승인할 수 있습니다. 기본 연결은 읽기 전용이지만, 어시스턴트가 새로운 공간을 스캔하거나 Wi-Fi 비밀번호 및 알람 코드와 같은 민감한 정보에 접근할 수 있도록 권한을 부여할 수 있습니다. 이 서버는 streamable HTTP를 사용하며, 데이터를 안전하게 관리하기 위해 Cloudflare Workers에 배포할 수 있습니다.
단순한 쿼리를 넘어, 이 서버는 서로 다른 스캔 데이터를 비교하여 변경 사항을 식별하고, 사진 증거로서 원본 비디오 프레임을 가져오는 기능을 제공합니다. 스캔 기록 관리, 스캔 상태 확인, 그리고 보트나 가전제품과 같은 특정 환경 촬영을 위한 체크리스트 준비를 위한 전문 도구도 포함되어 있습니다.
활용 사례
- 1시각적 증거와 함께 특정 아이템 찾기물체의 위치를 요청하고 어시스턴트에게 원본 사진 증거를 보여달라고 요청할 수 있습니다.
프로젝트의 README를 바탕으로 작성되었습니다. 모든 활용 사례는 해당 내용의 인용문과 대조하여 확인합니다.
Space Context MCP 설치 방법
형식 확인: 2026년 11월 10일Cursor에 추가Goose에 추가Claude Code에 Space Context MCP 설치
$ claude mcp add --transport http spacecontext https://mcp.spacecontext.app/mcpCursor에 Space Context MCP 설치
~/.cursor/mcp.json
{
"mcpServers": {
"spacecontext": {
"url": "https://mcp.spacecontext.app/mcp"
}
}
}VS Code에 Space Context MCP 설치
.vscode/mcp.json
{
"servers": {
"spacecontext": {
"type": "http",
"url": "https://mcp.spacecontext.app/mcp"
}
}
}VS Code CLI에 Space Context MCP 설치
$ code --add-mcp '{"name":"spacecontext","type":"http","url":"https://mcp.spacecontext.app/mcp"}'Codex에 Space Context MCP 설치
$ codex mcp add spacecontext --url https://mcp.spacecontext.app/mcpCodex config.toml에 Space Context MCP 설치
~/.codex/config.toml
[mcp_servers.spacecontext] url = "https://mcp.spacecontext.app/mcp"
Gemini CLI에 Space Context MCP 설치
$ gemini mcp add -s user --transport http spacecontext https://mcp.spacecontext.app/mcpGemini settings.json에 Space Context MCP 설치
~/.gemini/settings.json
{
"mcpServers": {
"spacecontext": {
"url": "https://mcp.spacecontext.app/mcp",
"type": "http"
}
}
}Space Context MCP 도구 13
README에서 감지됨list_spacessearch_spacesget_spaceget_space_markdownask_spaceget_evidence_photowalletcapture_checklistcheck_framecreate_scanupload_framestart_scan
| list_spaces | — | |
| search_spaces | — | |
| get_space | — | |
| get_space_markdown | — | |
| ask_space | — | |
| get_evidence_photo | — | |
| wallet | — | |
| capture_checklist | — | |
| check_frame | — | |
| create_scan | — | |
| upload_frame | — | |
| start_scan | — |
도구 13개 모두 보기도구 수 줄이기
cancel_scan
| cancel_scan | — |
자동 검사
2026년 11월 14일에 실행됨전체 보고서 →아직 인증되지 않았습니다. 서버는 80점 이상의 점수, 심각한 결함 없음, 그리고 검사에 충분한 데이터를 갖추어야 합니다. 검사 방식 · 점수를 높이기 위해 수정할 항목
- 소스 저장소 연결 및 접근 가능finikoslab/spacecontext is public and reachablegithub.com/finikoslab/spacecontext ↗통과
- 패키지가 이 저장소를 소스로 명시검사되지 않음
- 빌드 출처(Sigstore 증명)검사되지 않음
- 오픈 소스 라이선스 (OSI)MITspdx.org/licenses/MIT.html ↗통과
- 최근 1년 내 커밋 또는 릴리스Last commit or release 2026-10-28github.com/finikoslab/spacecontext ↗통과
- OpenSSF Scorecard검사되지 않음
- 패키지 이름이 인기 패키지와 유사하지 않음검사되지 않음
- 패키지 및 해당 종속성에 중요한 보안 권고 없음검사되지 않음
- 모델에 대한 숨겨진 지침 없음13 tool descriptions and the README read; no override phrases, credential paths or hidden characters통과
- 파괴적인 도구에 라벨 표시됨No tool named like delete, drop or exec통과
- 원격 엔드포인트가 MCP 핸드셰이크에 응답HTTPS endpoint answered 401 (sign-in required)통과
README
GitHub에서 보기Space Context MCP server
A remote MCP server that gives Claude, ChatGPT, Codex, Cursor, VS Code or any MCP client access to your Space Context spaces. The assistant can list spaces, search them, read them by section or as one page, ask them questions, compare scans and show the photo evidence. Every item, issue and key location says whether a second, independent check found it on its own photo (verified, unconfirmed or from the narration), so the assistant knows what to state and what to hedge. If you allow it, it can also scan spaces for you.
https://mcp.spacecontext.app/mcp
It speaks MCP over Streamable HTTP and authorizes with OAuth 2.1 (dynamic client registration and client ID metadata documents). It's stateless (createMcpHandler from agents, MCP SDK v2) behind @cloudflare/workers-oauth-provider. This package isn't published to npm. Use the hosted server above, or deploy your own.
Connect an assistant
| Client | How |
|---|---|
| Claude (claude.ai, Desktop) | Settings → Connectors → Add custom connector, paste the URL, Connect |
| Claude Code | claude mcp add --transport http --scope user spacecontext https://mcp.spacecontext.app/mcp, then /mcp → Authenticate |
| Codex | codex mcp add spacecontext --url https://mcp.spacecontext.app/mcp, then codex mcp login spacecontext |
| ChatGPT | Settings → Apps & Connectors → Advanced → Developer mode, then create a connector with the URL and OAuth |
| Cursor | "spacecontext": { "url": "https://mcp.spacecontext.app/mcp" } under mcpServers in ~/.cursor/mcp.json, then Login in Cursor's MCP settings |
| VS Code | code --add-mcp '{"name":"spacecontext","type":"http","url":"https://mcp.spacecontext.app/mcp"}' (or servers in a workspace's .vscode/mcp.json), then MCP: List Servers → start it and sign in |
You never paste a key. Connecting works like this:
- Your assistant opens a Space Context page. You sign in with Apple, Google or a code sent to your email, using the same account as the iPhone app.
- You choose whether the assistant may see sensitive values (Wi-Fi passwords, door and alarm codes, the narration) and whether it may scan spaces for you. By default it can do neither. Scanning needs a card on file in your account (added in the console, nothing charged): without one, the page offers to connect read-only instead, or to try again once the card is added.
- The server creates an API key for this connection only, listed as
MCP · <assistant>in the console. Its scopes arespaces:readandscans:read, plusspaces:sensitiveandscans:writeif you ticked them.
Revoking that key in the console ends the connection, and the assistant asks you to sign in again. Connecting the same assistant again replaces its previous key. The assistant sees your live spaces, including the ones scanned with the iPhone app. A space from the app becomes readable once it has been screened for sensitive values: the first read starts the screening, which takes a minute or two. Full guide: Connect an assistant.
Tools
Reading tools, on every connection (annotated read-only and idempotent):
| Tool | |
|---|---|
list_spaces |
Spaces with their latest scan, 50 per page |
search_spaces |
The records that best answer a question, across all spaces or one, in any language |
get_space |
A space by section (areas, items, issues, key locations, instructions, facts, Q&A, coverage), optionally with evidence |
get_space_markdown |
The whole space as one Markdown page, to load it as context in one call |
ask_space |
A short answer with citations, or documented: false |
list_scans, compare_scans |
The scan history, and what changed between two scans, with evidence from both |
get_evidence_photo |
The original video frame behind a record, as an image |
get_scan_status, follow_scan |
Where a scan is; follow_scan waits on the event stream and reports progress |
wallet |
Balance, free scans left, price of a scan |
capture_checklist |
What to film for a type of space (a flat, a car, a boat, an appliance…), before a scan |
These tools work only on a connection where the user ticked let it scan spaces. On any other connection the API refuses them with INSUFFICIENT_SCOPE:
| Tool | |
|---|---|
check_frame |
Is this photo usable, and which key locations does it show (with space_type, those of that type and the area); nothing is stored or charged |
create_scan |
Declares a scan of an existing or a new space and returns the upload instructions |
upload_frame |
Sends one image of a frames scan through the server, which holds the key |
start_scan |
Starts and charges a scan: the free scan first, then $1.00 from the balance; refunded if it fails |
cancel_scan |
Cancels a scan that hasn't started; nothing is charged |
Resources: spacecontext://spaces (the list, JSON) and spacecontext://spaces/{space_id} (a space as Markdown). Prompts: check_out_report (compare two scans and write a report that keeps confirmed changes apart from what may be missing) and where_is (find one thing, with its area and evidence photo).
No tool reaches the open web. Space content is returned as data, never as instructions: the server's instructions say so, and so does a note in every result that carries space content. The server card at /.well-known/mcp/server-card.json lists tools, resources and prompts before sign-in. Arguments and results: MCP tools.
Deploy your own
The server is a Cloudflare Worker that talks to a Space Context API (…/v1, with API_V1_ENABLED = "true"). It signs people in through the API's own sign-in endpoints and creates one API key per connection. Everything it keeps is in KV: OAuth clients, grants and tokens (grants carry the connection's API key and are encrypted by the OAuth library), and sign-ins in progress, for ten minutes, encrypted with a key that only the user's browser holds.
1. Install and build the SDK (the server imports it), from the repository root:
npm install
npm run build -w @spacecontext/sdk
2. Create the KV namespace for OAuth clients, grants and tokens, and put its id in kv_namespaces in wrangler.jsonc. This and the next steps run in packages/mcp:
cd packages/mcp
npx wrangler kv namespace create OAUTH_KV
3. Set the configuration in wrangler.jsonc (name, the custom domain in routes, and vars):
API_BASE_URL |
The API base, for example https://api.spacecontext.app/v1 |
PUBLIC_URL |
This server's origin. It names the protected resource (/.well-known/oauth-protected-resource/mcp) and is the only origin the consent forms accept posts from |
GOOGLE_WEB_CLIENT_ID |
Optional: the Google web OAuth client for "Continue with Google" |
APPLE_SERVICES_ID |
Optional: the Services ID for "Sign in with Apple" |
BACKEND (services) |
Optional: a service binding to the API Worker. Through it, the API sees each user's own IP for its rate limits and sign-in protection. Without it, the server calls API_BASE_URL over the internet and every user shares the Worker's IP. Remove the entry if the API isn't a Worker in your account |
4. Add the secret for Google sign-in:
npx wrangler secret put GOOGLE_WEB_CLIENT_SECRET
5. Register the callback URLs with the providers:
- Google: add
${PUBLIC_URL}/authorize/google/callbackas an authorized redirect URI of the web OAuth client. - Apple: add
${PUBLIC_URL}/authorize/apple/callbackas a return URL of the Services ID.
Without both GOOGLE_WEB_CLIENT_ID and the secret, the Google button isn't shown, and the same goes for Apple without APPLE_SERVICES_ID. Email sign-in is always offered. The API checks Google and Apple tokens against its own web client ID and Services ID, so use the same ones the API is configured with.
6. Deploy:
npm run deploy # wrangler deploy of the top-level environment
Keep these settings from wrangler.jsonc:
global_fetch_strictly_publicstays on. The server fetches client metadata documents from URLs that clients choose, so a plainfetchmust never reach private addresses. The API is reached through theBACKENDbinding.- With
workers_devandpreview_urlsoff, the server answers only on its custom domain. ratelimitslimit each client IP to 10 registrations (/register) and 60 sign-in page requests (/authorize…) a minute, answered with429andRetry-After: 60beyond. Rate limits aren't inherited by environments, and eachnamespace_idmust be unique in your Cloudflare account. Without the bindings (as indev) nothing is limited.- Access tokens last one hour. A grant lives for 90 days after its last refresh. A client registered dynamically is deleted after 180 days without a token request.
wrangler.jsonc also defines dev (local, see below) and staging (Space Context's own staging deployment).
Develop
npm run dev -w @spacecontext/mcp # http://localhost:8788, against an API on 127.0.0.1:8787
npm test -w @spacecontext/mcp # the full OAuth flow and MCP calls in workerd, against a fake API
The API isn't part of this repository. The tests don't need it: they drive registration, PKCE, consent, token and real MCP calls against a fake API. The dev environment sets no Google or Apple client, so local sign-in uses the emailed code. Read CONTRIBUTING.md before adding a tool: any tool that writes or spends must sit behind scans:write and be annotated honestly.
MIT © Finikos S.r.l.
Space Context MCP 질문
Space Context MCP를 Claude Code에 추가하려면 어떻게 하나요?
터미널에서 claude mcp add --transport http spacecontext https://mcp.spacecontext.app/mcp를 실행합니다. 모든 프로젝트에서 사용할 수 있게 하려면 --scope user를 추가합니다.
Space Context MCP를 Cursor에 추가하려면 어떻게 하나요?
~/.cursor/mcp.json를 열고 mcpServers 아래에 서버를 추가합니다. 위 설치 섹션에 표시된 Cursor 구성을 사용합니다.
Space Context MCP는 어떤 도구를 제공하나요?
13개 도구를 제공합니다. 예: list_spaces, search_spaces, get_space, get_space_markdown, ask_space.
AI 어시스턴트가 Wi-Fi 비밀번호와 같은 민감한 정보를 볼 수 있나요?
연결 과정에서 명시적으로 권한을 부여하지 않는 한, 어시스턴트는 Wi-Fi 비밀번호나 도어 코드와 같은 민감한 값을 기본적으로 볼 수 없습니다.