Agent setup

​

Order of operations

1. Start stacknext dev.
2. Install the skill and managed instructions.
3. Configure MCP.
4. Ask the agent to call get_project_summary before investigating.

​

Managed AGENTS.md instructions

pnpm exec stacknext init --agents

1. Read the local documentation entry point listed in the block.
2. Read the docs for each StackNext package involved in the task, listing only packages that are actually installed.
3. Confirm the installed version in the adjacent package.json.
4. Prefer local docs over external docs or model memory.
5. Not assume undocumented APIs, configuration or internal packages exist.
6. Use the read-only MCP tools for runtime investigation.
7. Follow the stacknext-debugging skill for deeper workflows.
8. Treat diagnostics and comparisons as evidence, not confirmed causes.
9. Verify against the installed implementation and tests.

• A missing AGENTS.md is created.
• An existing file is never overwritten.
• Content outside the markers is preserved byte-for-byte, including CRLF.
• The block is replaced in place on later runs.
• Duplicate or partial markers cause a clear error; the file is not modified.
• No client config or global instruction file is touched.

​

Agent Skill

pnpm exec stacknext skill install --client opencode
pnpm exec stacknext skill install --client codex
pnpm exec stacknext skill install --client claude-code

​

MCP server configuration

pnpm --dir /absolute/path/to/your-app exec stacknext mcp

​

OpenCode

{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "servers": {
      "stacknext": {
        "type": "local",
        "command": [
          "pnpm",
          "--dir",
          "/absolute/path/to/your-app",
          "exec",
          "stacknext",
          "mcp"
        ],
        "codemode": false
      }
    }
  }
}

opencode mcp add stacknext -- \
  pnpm --dir /absolute/path/to/your-app exec stacknext mcp

​

Codex

[mcp_servers.stacknext]
command = "pnpm"
args = ["--dir", "/absolute/path/to/your-app", "exec", "stacknext", "mcp"]

​

Claude Code

claude mcp add stacknext -- \
  pnpm --dir /absolute/path/to/your-app exec stacknext mcp

{
  "mcpServers": {
    "stacknext": {
      "command": "pnpm",
      "args": [
        "--dir",
        "/absolute/path/to/your-app",
        "exec",
        "stacknext",
        "mcp"
      ]
    }
  }
}

​

Supported clients

​

Verify

Call the StackNext get_project_summary tool and tell me whether instrumentation
is connected. Then list the three slowest requests.

​

Boundaries

• Every MCP tool is read-only. The server cannot capture, save, compare, delete or edit anything.
• The skill shapes an investigation but cannot bypass redaction or add capabilities.
• The connected client may log or transmit tool results under its own policy. StackNext does not control the client. Review that policy before using a hosted model with project telemetry.
• A client is listed as supported only after a recorded end-to-end check. See agent compatibility testing.

​

Related

• MCP server
• MCP tools
• Agent workflows
• Local documentation