Files
Quadrapassel/docs/MCP_SETUP.md
T

99 lines
6.2 KiB
Markdown
Raw Blame History

This file contains ambiguous Unicode characters
This file contains Unicode characters that might be confused with other characters. If you think that this is intentional, you can safely ignore this warning. Use the Escape button to reveal them.
# MCP kickoff and connection inventory
Verified November 10, 2026 against installed official VCC Plus **3.5.5 (48)**.
Keep private grant files and tokens outside Git. This is a connection record,
not permission to inspect emulator implementation or another game's project.
| Connection | Live tools used | Verification |
| --- | --- | --- |
| Quadrapassel C project | `get_capabilities`, `read_project_inputs`, `refresh_project`, `build_project`, `get_build`, owned-playtest tools | Project `A1AFAA7E-C427-4437-8D1C-EB68D8C225EF`; this repository's root Makefile, files and hashes |
| Installed manuals/API (through the C connection) | `search_help`, `read_topic` | Read HSCREEN/HSET, keyboard, joystick, timer, SOUND, beep and PCLEAR topics |
| Archive Library (separate connection) | `search_archive`, `get_archive_citation` | Both succeeded; found Tandy's Color Computer 3 Extended Basic, PDF pages 152–153 |
At this chat's start no VCC Plus tools appeared in its tool catalog. Connections
were exported through the installed app's normal native interface. Its public
manual, `vibe-coding-with-chatgpt/01-first-connection.html`, explicitly permits
ordinary STDIO MCP through `/Applications/VCC Plus.app/Contents/Helpers/vcc-mcp`
with the two arguments `--grant` and the private grant filename. The unmodified
installed helper is used by a small MCP client; no alternative server, private
bridge or integration endpoint is used.
Archive Library has its own link button and **Save Archive Search Connection…**
flow. Brian explicitly approved this connection on November 10. Its advertised
build-48 tools return citations/locations, rather than full page text. Use the
Archive Library native reader for the original page when needed. Do not infer
that Archive MCP is unavailable from the C connection's tool inventory.
For future kickoff checks, distinguish **configured**, **tools discovered**, and
**successful request**. Inventory each required connection separately before
implementation or web fallback. Confirm the intended project and current revision
before builds. Connection identity and advertised tools may change after a new
export; discover them again, rather than inventing tool names or endpoints.
Example verified Archive reference:
- Title: *Color Computer 3 Extended Basic (Tandy)*.
- Citation: `sha256:26d4ca51f3477263f3e85269091104079ae88ad83c842cef0e3bc531324e7f5e:pdf_page:152`.
- Read in Archive Library: printed page 143, “Adding Pages (The PCLEAR Command)”.
It describes the default four PMODE pages and reserving fewer pages.
Initial hardware-reference web lookups occurred before discovering the separate
Archive connection. That was a discovery error, not a demonstrated Archive gap.
Brian asked that the kickoff feedback be sent to **Deploy VCC Plus Gitea**; the
approved concise feedback was delivered there. No emulator update is requested.
## November 11 reconnection
Brian approved installed official VCC Plus 3.6.0 (51) and an idle desktop window.
The same repository was opened through C Development and its private project
connection renewed outside Git. A successful `get_capabilities` returned project
`84772EFC-B651-4A98-B09E-932247575EA7`, session
`185C8449-CB9B-4A38-81C8-D43CDA4A3ABE`, app build 51, approved Make recipe,
and the expected Quadrapassel files. This connection still advertises fixed
512 KB disposable workers, MC6809/HD6309, graphics and audio captures.
Archive access is separate and was not needed for this local font adaptation.
After Brian's November 11 restart, the old private grant expired. The same
project connection was renewed through the supported interface. Current project
`3D6A502C-E06D-46BC-9D19-191D741A16B9`, revision 2, built and ran successfully
on official build 51. get_machine_status read normal-session configuration;
no writable disks or peripherals were removed to satisfy native-run blockers.
The new candidate used only disposable playtests.
Brian approved official VCC Plus 3.6.1 (53) and an idle desktop window for the
joystick investigation. The renewed connection verified project
7D6E1D9C-DF7C-4B15-B64D-6B30732417CB, revision 2, built successfully and ran the
frozen artifact. Its playtest_input schema still supports only keyboard keys,
not analog axes/fire injection. No native joystick pass is inferred from it.
Build 03 used that project at revision 3 on official build 53. Keep the official
STDIO helper connected while a refresh awaits native review: with the one-shot
helper disconnected the review window was not presented. Closing C Development
invalidated this private grant after all owned runs stopped. Reconnect through
the official interface when more MCP work is needed.
Only real result folders belong in outputDirectories. An attempt to exclude
numbered DSK files there was accepted by MCP inventory but broke native project
opening (reported as missing assets/ui-text.tsv). File exclusions were removed;
explicit resourceInputs names the two real text inputs. Native project loading
and Release disk build then passed. Root delivery disks remain project resources:
freeze them during owned tests and create/update delivery filenames after the run
stops. Personal media/backups are never reset to satisfy source identity.
Build04 was built and qualified through the native installed build53 C Development
workflow after the grant ended. Native builds FC462D93 / A7A18927 succeeded.
Launch Disk mounted a separate working copy; explicit cold restart plus DOS was
required because the prior graphics game was still in RAM. A new mounted filename
or C workspace's latest-build badge alone does not prove the guest reloaded it.
Build05 final checks use official build54's newly exported native connection,
project273E195B-8BFC-495F-A1F8-E1469759B910 revision0. Discovery returned29 tools,
playtest_joystick_input and input_diagnostics; actual standard port/axis/fire2
steps and get_playtest_input were used successfully. The official local helper
required local-service execution permission; without that permission it returned
host_unavailable despite local tools/list succeeding. This was resolved without
replacing the grant or changing the emulator. All owned runs stopped; the native
workspace was released to Core for the next project's scoped connection. Private
grant files remain outside Git. See SECONDARY_BUTTON.md for exact evidence.