CLI and MCP task workflows

Get ready to work on your project

joripspace start PROJECT --json
joripspace knowledge search --query "deployment and diagnostics" --json
joripspace --help

Start by connecting the project and checking its current state. The response helps you continue from the existing source and deployment. You can search for task guidance with knowledge search and look up command options in the help.

With MCP, your agent can find the same information in the available tools and manuals. Your AGENTS.md can stay focused on project rules while the agent looks up detailed instructions as needed.

Build, deploy and verify

Build the app with the command already used by your project. For a GitHub-connected project, use its configured branch or release workflow. For a direct CLI deployment, check where the build files are saved and which file starts the server.

The example below deploys a built dist folder with worker.js as the server entrypoint. Replace the folder and filename with your actual build output.

joripspace deploy --project PROJECT --dir dist --entrypoint worker.js --label "Release" --json
joripspace deployments --project PROJECT --json
joripspace events --project PROJECT --event-type error --json

When deployment finishes, open the returned service URL and try the feature you changed. Check dynamic pages and error responses as well. If the deployment response is interrupted, look at the history before trying again; the deployment may already have completed. For rollback and recovery, see Deployment and operations.

Inspect and migrate data

joripspace db schema --project PROJECT --json
joripspace db query --project PROJECT --sql "SELECT name FROM sqlite_master WHERE type = 'table'" --json
joripspace db migrate --project PROJECT --file migrations/001_init.sql --json

Before changing the database, use db schema to inspect its tables and check how the app reads and writes data. A migration records the changes needed for the new structure. Prepare one that preserves existing data, check the indexes used by your queries and apply it once. Replace the example SQL file with the migration your project needs.

A schema mismatch usually needs a migration rather than a database reset. For uploaded files, use storage list. Fixed assets such as logos and design images belong in your project source.

Connect an external service

joripspace secret list --project PROJECT --json
joripspace secret generate --project PROJECT --name SESSION_SECRET --json

Use secret list to see the key names already registered. If your app needs a random value, such as a session signing key, secret generate can create it for you. The example uses the name SESSION_SECRET; choose the name your app expects.

For a key issued by an external provider, use secret set --name KEY_NAME --value-stdin to pass the value through standard input, or enter it directly on the project Secret page. Keep the value out of agent conversations. After saving it, check the key name and status, then test the service connection.

Diagnose and submit feedback

joripspace deployments --project PROJECT --include-failure-details --json
joripspace report --help

If something goes wrong, start with the deployment history and logs. They can help you work out whether the cause is in your app or the platform. To report a problem to JoripSpace, describe what you expected, what happened and how to reproduce it. Use feedback for an improvement idea.

The report guide explains the available fields. Leave out secret values and personal data, then check the report_id in the successful response. If you are working with an agent, ask it to send the report after reviewing the content.