agentcontextDownload

AGENT CONTEXT / DOCS

Get back to building.

Resolve installation paths, tokens, network errors, client setup, and website deployment.

Start with the actual error

Check node --version, npm --version, and agent-context-mcp --version. Read the first failed step as well as the final error. For a bug report, include versions, operating system, installation method, and minimal reproduction in GitHub issues. Remove tokens and private context.

Package file not found (ENOENT)

A tarball retry warning does not prove corruption. ENOENT means npm cannot find the file at the supplied path. After downloading the package, run this from its download folder:

TERMINAL
npm install -g ./agent-context-mcp-0.4.0.tgz

From the source repository, generate the ignored package first:

TERMINAL
npm ci
npm run build
npm pack --ignore-scripts --pack-destination dist/npm
npm install -g ./dist/npm/agent-context-mcp-0.4.0.tgz

If the downloaded file is incomplete, download it again and compare its SHA-256 digest with release checksums. A checksum verifies a matching file, not publisher identity.

Command not found or the wrong version starts

Use Node.js 24+. Check npm prefix -g and the executable directory in your terminal and editor PATH. Use the absolute executable path in client settings if needed. Deactivate the old Python virtual environment if it selects the Python prototype. From source, run node bin/agent-context-mcp.mjs --version after building.

Port already in use

Stop the old service or choose --port 8766, then update client URLs and any Host/Origin allowlists. A local service on port 8765 also prevents an SSH tunnel from binding that port.

Token rejected or history is different

Retrieve the token on the running host using its exact database path and credential settings. A teammate’s separate local token will not authenticate to the shared host. Relative database paths depend on the current directory. Ensure every client uses the same host or local database and the same project ID.

Use only one token source. Restart after token rotation and update clients. Reloading the dashboard clears its in-memory token.

Connection and HTTP errors

  • Timeout or refused: check service, host IP, firewall, VPN, tunnel, and Wi-Fi client isolation.
  • 401: supply the running host’s token in the Authorization header.
  • 403: add the exact browser Origin, including scheme and non-default port.
  • 421: allow the exact Host and port. Never use 0.0.0.0 as a client URL.
  • 413: split an oversized update.
  • 429 or 503: follow Retry-After when present and retry later.

Follow the team network guide for LAN, VPN, SSH, and HTTPS. Localhost reaches the client’s own machine unless you explicitly configured forwarding.

Connected agent does not record work

Enable MCP tools and start a fresh session. A subprocess setup needs the stdio action. Add the shared workflow to the instruction file the agent reads and verify actual tool calls using a test project. Local models also need compatible templates, tool use, and an MCP-capable host.

Vercel build or preset mismatch

Import the repository root (./), choose Other and Node.js 24.x, set build command npm run vercel:build and output directory site/dist. Ensure the current commit includes vercel.json and matching package/site versions. npm run site:serve is only a local preview.

The Vercel site hosts docs and downloads; the persistent MCP server runs separately. For further detail, see the repository troubleshooting guide.