98 lines
5.6 KiB
Markdown
98 lines
5.6 KiB
Markdown
# Connect this project through MCP
|
|
|
|
VCC Plus shares a selected project through its supported local Model Context
|
|
Protocol connection. Use the official downloaded app, this checkout and your own
|
|
connection. Create a scoped connection for the project you selected and verify
|
|
its current identity before building or testing.
|
|
|
|
## Prepare the C-project connection
|
|
|
|
1. Open this existing game project in **Develop → C Development…** and select
|
|
**Release**. Check that `main.c`, the supplied Makefile and project resources
|
|
belong to this checkout.
|
|
2. In **Assistant…**, review the files and permissions to share. Select **Use
|
|
Project Makefile** for its declared recipe. Select **Allow Disposable
|
|
Playtests** only when you want the assistant to run isolated copies of the disk.
|
|
3. Save a fresh private connection and add it to ChatGPT through the supported
|
|
workflow described by the installed manuals. Keep VCC Plus and the shared
|
|
workspace open while using it.
|
|
4. Discover the tools currently exposed. Make a real project/capabilities request
|
|
before changing files or building. Verify project identity, revision, input
|
|
files, recipe, Release configuration and the declared disk action.
|
|
|
|
A configured server, a displayed tool list and successful project access are
|
|
three different checks. Tool discovery alone does not establish that the editor
|
|
is still open or the connection still authorizes its current project.
|
|
|
|
## Check three kinds of access separately
|
|
|
|
| Access | What to verify | What it is for |
|
|
| --- | --- | --- |
|
|
| C project | The intended project and current source/build identity | Read/edit proposals, declared Make builds and any approved owned tests |
|
|
| Manual Library | A real search followed by reading a returned topic | Installed CMOC API contracts and VCC Plus usage guidance |
|
|
| Archive Library | Its own read-only connection and a successful search/citation | Historical CoCo manuals, publications and hardware references |
|
|
|
|
Project connections include manual access; Archive Search has its own connection
|
|
exported from the Archive Library panel. Do not infer that Archive access is
|
|
missing just because it is absent from a C connection's tool list. Keep a
|
|
publication/page citation when using an archived source.
|
|
|
|
Common public project tools include `get_capabilities`, `read_project_inputs`,
|
|
`refresh_project`, `build_project` and `get_build`; owned-run and capture tools
|
|
are present only for supported, granted capabilities. Manual and Archive tools
|
|
have their own returned schemas. These names are discovery examples, not an
|
|
instruction to assume a tool exists or hardcode its arguments.
|
|
|
|
## Build and test the selected revision
|
|
|
|
Ask the assistant to identify what it can actually do, then:
|
|
|
|
1. Review or refresh changed project inputs through the supported native flow.
|
|
Keep the ordinary helper connected while a review is awaiting a decision.
|
|
2. Build the current revision's declared **Release** disk action. Poll the build
|
|
result, inspect diagnostics/memory bounds and retain the artifact identity.
|
|
3. Start an approved disposable run from that exact artifact. Poll startup and
|
|
check its actual RAM/CPU/disk configuration before making a test claim.
|
|
4. Apply ordinary guest input with release intervals, inspect real frames and
|
|
save behavior, and capture bounded audio when available. Stop the owned run
|
|
and retain its disk receipt when finished.
|
|
|
|
Do not copy mutation request IDs from older runs, use another project's grant,
|
|
or assume a past screenshot came from the current build. Keep observations bound
|
|
to the project revision, build/artifact and test configuration.
|
|
|
|
## If access stops working
|
|
|
|
Check whether the app and the intended C workspace remain open, whether sharing
|
|
is enabled for that project, and whether the private export is still current.
|
|
Changing projects, closing the shared workspace, revoking access or exporting a
|
|
replacement connection can end an earlier connection. Reconnect through the
|
|
native panel and repeat discovery instead of guessing a private endpoint.
|
|
|
|
A tool list can be available while a live request fails. If the environment blocks
|
|
access to the app's local service, check the supported connection and applicable
|
|
local app/service permission. An actual permission block is different from a
|
|
missing tool. Report the observed error; do not replace the app or weaken system
|
|
security to hide it. Continue source/documentation work that does not need the
|
|
connection until access is restored.
|
|
|
|
Capabilities vary between public app releases. If joystick injection, a CPU/RAM
|
|
choice, graphics inspection or audio capture is absent, use the supported native
|
|
workflow or a clearly identified user-controlled test for that part. Never treat
|
|
keyboard input as analog joystick evidence or a worker's 512 KB configuration as
|
|
an additional 128 KB test.
|
|
|
|
## Keep sharing private and scoped
|
|
|
|
Keep connection exports, tokens and credentials outside the repository and out of
|
|
chat text. Do not add them to commits, screenshots, public issues or manuals.
|
|
Use only the ordinary official helper/client procedure in the installed manual;
|
|
no replacement server, private endpoint or emulator-source inspection is needed.
|
|
Revoke a connection when its work is finished, and preserve writable test disks
|
|
and personal media independently of the connection's lifetime.
|
|
|
|
The public [connection lesson](https://vccplus.brianholman.com/manuals/vibe-coding-with-chatgpt/01-first-connection/)
|
|
and [existing C-project example](https://vccplus.brianholman.com/manuals/vibe-coding-with-chatgpt/06-capitals/)
|
|
provide the supported user-facing setup steps. For the game-specific build and
|
|
media rules, use [VCC_PLUS_WORKFLOW.md](VCC_PLUS_WORKFLOW.md).
|