NIMOS / ENGINES / MCPAC
← THE BUILD SYSTEMMCPAC
THE CONNECTORS
Model Context Protocol & Agent Connectivity
One standard plug for the agents that need files, the web, a browser or a database.
DRAWN BY THE HOUSE
One mark per engine, on one grid, in one hand.
5
TOOLS
OPENCODE
WIRE
N/A
THIS BUILD
No MCP server runs inside this site's runtime; the agent surface is separate.
THE PROOF LEDGER →WHAT
What it is
Five MCP servers: filesystem, fetch, Playwright, Postgres and GitHub. The studio uses the live ones; standby entries are labelled with what would make them live.
WHY
Why it exists
Every bespoke integration is a future outage. MCP gives agents a standard surface with explicit access, and the registry says which servers are on, which are standby and why.
HOW
How it runs
`engctl wire mcpac` merges entries into the OpenCode config, comment-safe, with a backup. Each entry is verified by a live tool call, not by reading a config file.
WHEN
When it runs
Agent connectivity changes, a new database, browser end-to-end tests on previews, or a new external service that already has an MCP server.
WHO
Who owns it
CEO owns the access surface; Research watches advisories; Build registers safely; Data keeps the access ledger; Ops proves each server answers.
TOOLS
The registry
The engine manifest is the source of truth. These are its entries, including the ones that are not used on this build — the proof ledger says which is which.
@modelcontextprotocol/server-filesystem
mcpSecure, agent-guided file read/write inside WSL workspaces.
@modelcontextprotocol/server-postgres
mcpHook agents to Postgres/Neon — schema reads, table edits, migrations.
@modelcontextprotocol/server-fetch
mcpSafe, agent-managed web parsing and raw markdown fetching.
@modelcontextprotocol/server-github
mcpRepository orchestration — PRs, diffs, issues.
mcp-server-playwright
mcpHeadless browser wrapper — full end-to-end rendering and visual UI tests on preview deployments.
5 registry entries. The proof ledger on the Gantry page says which of them this build actually used.
RUN
Run it
ENGCTL / THE ENGINE FLOOR
$ engctl show mcpac$ engctl awaken mcpac$ engctl install mcpac --dir ./site`engctl` is the registry control surface. `awaken` checks wiring before it activates a cell; `install` writes the parts into a project.
PROOF
On this build
No MCP server runs inside this site's runtime; the agent surface is separate.
N/A and PARTIAL are stated, not hidden. The ledger is generated from this project, not from a template.
LIMITS
What this does not claim
N/A on this site: the runtime does not expose MCP servers. The connector layer is an agent surface, not a client feature.
The engine is the how. The brief is the start.