JoripSpace

Showing 25 of 48 from the live probe.

• Get Realtime V2

  Read realtime v2 activation and key operation status. Read manual://realtime/v2 before integration.

• Manage Realtime V2

  Explicitly activate, rotate, disable or revoke a realtime v2 signing key. Private key values are never returned. When the user requests v2 development, include first-time activation in that development task after checking get_realtime_v2. Do not require a separate dashboard action. Do not activate unrelated projects or automatically migrate existing realtime integrations.

• Start Login

  Start JoripSpace MCP onboarding when the user has no connect_token. Use this before get_project for short requests like "JoripSpace MCP 온보딩 시작". Do not ask for email or any other user info. Return the browser connect link only, wait for the copied 5-minute connection code, call exchange_connection_code, then call start_project_session with the returned token.

• Browser Connect

  Return the browser connection link. The user opens it in a logged-in browser, approves connection, and copies the 5-minute connection code.

• Exchange Connection Code

  Exchange the 5-minute one-time code pasted by the user for a JoripSpace connect_token. Call this immediately when the user provides a standalone connection code. Never echo the returned token in chat; pass it to start_project_session and preserve it through the returned local_file_operations.

• Search Knowledge

  Search active DB-managed JoripSpace operating knowledge and community guidance. Call this once at the start of each new distinct user task with the user's plain request before planning or asking questions, even when the beginner request is very short. Reuse the result during follow-ups unless the topic changes.

• Start Project Session

  Preferred first tool after receiving a connection token. After the user provides connect_token, call this before get_project even if a project_id is already known. It checks projects and handles one-project auto-selection or multi-project choice. A completely new project returns published templates embedded in onboarding.template_choice. A project with connected GitHub source or a restorable deployment returns template_choice.status=auto_selected_existing_project with selected_option=0; do not s

• Get Session Context

  Compatibility tool for reading the linked account id and project list. Prefer start_project_session for new flows because it also returns workspace file operations and first questions.

• List My Projects

  Compatibility tool for listing projects accessible to the linked account. Prefer start_project_session for new flows.

• Select Project

  Compatibility tool for selecting one project and returning workspace_setup.files. Prefer start_project_session; when using this tool, immediately write files using local_file_operations, then start service questions.

• List Templates

  List published JoripSpace templates during initial onboarding after the project workspace/source baseline is ready. Show available templates plus the explicit "템플릿 없이 시작" option, then wait for the user choice before service questions. Free or already-owned templates are selectable; direct paid purchase remains on the web templates page.

• Prepare Project Workspace

  Return the minimal local workspace connection files and workflow_enforcement for linking or refreshing an agent project. Agents must call this at the start of every new distinct JoripSpace task. Reuse the source-bound JORIPSPACE_API_TOKEN from ignored .env.joripspace; do not ask the user to reconnect for each task. Preserve user-authored AGENTS.md and CLAUDE.md content while applying the returned minimal block and first-line import, validate the one-line .joripspace/project slug, migrate verifie

• Deploy Code

  Deploy small server source files to an existing JoripSpace project only after completing the shared deployment verification gate. Inline deploy_code is rejected when any source file exceeds 16,000 characters or combined source exceeds 64,000 characters. Never print a generated bundle or large source through shell/tool output and copy it into files: tool output can be truncated. For generated bundles, large files, or large multi-file projects, automatically run the installed JoripSpace CLI absolu

• Get Project

  Get status and URLs only after JoripSpace onboarding/session connection exists. Do not use this as the first onboarding tool and do not call it by project_id alone. For short onboarding requests, call start_login when no connect_token exists, then start_project_session after the user provides the token.

• Prepare Github Workflow

  Generate the connection-specific managed GitHub Actions workflow for a project whose connected repository is waiting for its first source. Inspect the local project first, pass its actual Worker entrypoint, set package_build only when package.json has a build script, then immediately apply the returned local_file_operations, commit the application source and workflow, push the connected branch, and verify GitHub Actions and JoripSpace deployment. This tool returns trusted workflow content and re

• Describe Db

  List tables, indexes, views, and triggers in the project DB. Use this before changing schema. Use the project slug as project_id.

• Query Db

  Run one read-only SELECT query against the project DB and return rows. Use run_db_migration for CREATE, ALTER, INSERT, UPDATE, or DELETE.

• Run Db Migration

  Run a project DB migration such as CREATE TABLE, CREATE INDEX, ALTER TABLE, INSERT, UPDATE, or DELETE. This operates only on the selected project DB.

• List Storage Objects

  List files in the project storage. Use prefix to browse a folder-like path.

• Read Storage Object

  Read one project storage file by key. Text files return text; binary files return base64. Large files should be handled in app code instead.

• Write Storage Object

  Write one project storage file by key using text or base64 content. This modifies only the selected project storage.

• Delete Storage Object

  Delete one project storage file by key. Use only when the user asked to remove that file.

• List Deployments

  List recent deployments and rollback availability. Use include_failure_details=true to inspect build, GitHub Actions, policy, and deployment errors before fixing the failed commit and pushing a correction.

• Get Deployment Source

  Get source files for a successful deployment artifact. During initial onboarding, call this automatically with deployment_restore.latest_artifact.deployment_id from start_project_session; do not ask the user to choose a version. Apply the returned local_file_operations immediately to establish the latest deployed source as the local workspace baseline, while preserving all current connection tokens and session files.

• Rollback Deployment

  Rollback a project to a previous successful deployment bundle.