Run any Skill in Manus with one click

gofastr-mcp-debug

Stars12

Forks1

UpdatedJuly 17, 2026 at 13:47

Live debug a running GoFastr app via its MCP endpoint — combined entry point covering both the log_* tools (battery/log) and the app_* introspection tools (framework). Use when the user wants to "debug the live app", "see what's going on right now", "tell me about the running server", or any general "go look at the running app" prompt.

Installation

Install with Codex or Claude Copy this prompt, paste it into Codex, Claude, or another assistant, and let it review the skill page and install it for you.

Run Skill in Manus

Source

DonaldMurillo

DonaldMurillo/gofastr

View GitHub Repository View Creator Repositories

Download

Run Skill in Manus

Related occupationsSOC

Based on SOC occupation classification

Software DevelopersComputer and Mathematical Occupations·SOC 15-1252

SKILL.md

readonly

name	gofastr-mcp-debug
description	Live debug a running GoFastr app via its MCP endpoint — combined entry point covering both the log_* tools (battery/log) and the app_* introspection tools (framework). Use when the user wants to "debug the live app", "see what's going on right now", "tell me about the running server", or any general "go look at the running app" prompt.

Debug a running GoFastr app live (one-page guide)

This skill is the starting point for any agent investigation of a running GoFastr app via MCP. For deep recipes, jump to:

.claude/skills/log-debug/SKILL.md — the four log_* tools (recent entries, structured filter, metrics, level mutation).
.claude/skills/app-introspect/SKILL.md — the ten introspection tools: app_routes, app_plugins, app_batteries, app_modules, app_config, app_readiness, app_routines, plus framework_docs_list / framework_docs_get / framework_docs_search for the embedded framework docs.

When to use which

User asks…	Reach for
"What just happened?" / "Why is X failing?"	`log_recent`, `log_filter` (log-debug)
"Trace request ID abc-123"	`log_filter` with `request_id` + `historical=true`
"Is the app ready?"	`app_readiness` (app-introspect)
"What endpoints exist?"	`app_routes` (app-introspect)
"What plugins / batteries are loaded?"	`app_plugins`, `app_batteries` (app-introspect)
"What modules are enabled?"	`app_modules` (app-introspect)
"Did my routine body change propagate?"	`app_routines` (app-introspect) — ledger_state=drifted flags it
"Turn module X off / back on"	`app_module_disable`, `app_module_enable` (mutating)
"How does framework feature X work?"	`framework_docs_search` → `framework_docs_get`
"Are the logs even working?"	`log_metrics` — non-zero counters = lost entries
"Crank up DEBUG for 30 seconds, then back"	`log_set_level DEBUG` → reproduce → `log_set_level INFO`

Getting started

Under gofastr dev, everything below is automatic — the framework auto-mounts /mcp and enables introspection + control, every CRUD-enabled entity serves its {entity}_* data tools (no mcp: true needed), and battery/log (if registered) auto-enables its log_* tools. Opt-out: GOFASTR_DEV_MCP=0. So for a dev-loop app there is nothing to wire — just connect.

Outside the dev loop, the app opts in explicitly:

fwApp := framework.NewApp(
    framework.WithMCP(),                    // mounts /mcp (POST + GET SSE) + discovery well-knowns
    framework.WithMCPIntrospection(),       // app_* + framework_docs_* tools (read-only)
    framework.WithMCPControl(),             // app_module_enable/disable (mutating — trusted /mcp only)
)
fwApp.RegisterPlugin(log.New(log.Config{
    EnableMCP:   true,                       // log_* tools
    MCPRingSize: 2000,
}))

(WithMCP() replaces hand-mounting /mcp — doing both panics with a route conflict.) examples/site and blueprint-generated apps already have WithMCP + WithMCPIntrospection + the log battery wired. Spin the site up with the repo's normal dev workflow:

./scripts/dev-watch.sh         # examples/site on :8082, auto-rebuild
# or
go run ./examples/site         # :8083 — plain go-run has no PORT set

Then point curl at http://localhost:8082/mcp (or :8083 for go-run) and use the log-debug + app-introspect skills' recipes.

The JSON-RPC envelope

All tool calls are POST /mcp with body:

{
  "jsonrpc": "2.0",
  "id": 1,
  "method": "tools/call",
  "params": {
    "name": "<tool_name>",
    "arguments": { ... }
  }
}

Response wraps the tool's return value as a JSON-encoded string in .result.content[0].text — pipe through jq -r '.result.content[0].text' | jq . to get back to structured JSON. List available tools via "method": "tools/list" (no params).

Anti-patterns

Don't reach for MCP when grepping the file directly is easier. If the user knows exactly what they're looking for and has shell access, tail -f ~/.local/state/<app>/server.log | grep … may be the right move. MCP wins when the agent (not the user) is the consumer.
Don't curl tools you don't know the shape of. tools/list first if you're not sure what's registered; the descriptions are written for agents.
Don't forget to revert state mutations. log_set_level is the only mutating tool right now, but treat it like a temporary debug toggle: flip on, reproduce, flip off.

More from this repository

same repository

plain-words

DonaldMurillo/gofastr

Write GoFastr-facing copy in plain, concrete words. Auto-load before writing or editing ANY user-facing sentence — taglines, README prose, site/UI text, headlines, docs, changelogs, marketing. Kills jargon, marketing adjectives, abstract nouns, and AI-slop phrasing. Triggers on writing/editing copy, tagline, hero, headline, lede, positioning, README prose, landing page, UI microcopy.

2026-07-1912

gofastr-host

DonaldMurillo/gofastr

Auto-loads when working on a *host application* that imports the GoFastr framework (not the framework itself). Encodes the "don't reinvent — reach for the battery first" rule and the import paths an agent needs. Triggers on edits to Go files in repos that import `github.com/DonaldMurillo/gofastr/...`, on `main.go` files calling `framework.NewApp`, and on phrases like "login", "signup", "session", "user table", "log out", "magic link", "forgot password", "reset password", "add admin page", "back office", "audit log", "audit trail", "compliance log", "send email", "transactional email", "welcome email", "send a notification", "notify the user", "background job", "async task", "schedule", "cron", "run every hour", "retry on failure", "upload", "store images", "store files", "S3", "MinIO", "attachments", "avatar", "full-text search", "find records containing", "outbound webhook", "signed callback", "POST to a customer URL", "cache", "memoize", "remember for N seconds", "CSRF", "RBAC", "require admin", "roles", "r

2026-07-1812

app-introspect

DonaldMurillo/gofastr

Inspect a running GoFastr app's shape via MCP introspection tools. Use when the user asks "what routes exist", "is the app ready", "what plugins are loaded", "what's the current config", "what batteries depend on what", "what does this framework doc say", or any "describe the running server" question where the app was built with framework.WithMCPIntrospection().

2026-07-1712

gofastr-docs

DonaldMurillo/gofastr

Auto-loads when adding, changing, or removing any GoFastr feature or exported API. Encodes the doc topology (README + ARCHITECTURE + framework/docs/content/*.md) and the change→doc mapping. Docs are embedded in the gofastr binary at build time — `gofastr docs` browses them and the MCP `framework_docs_*` tools expose them to agents. Triggers on edits to framework/*.go, core/, battery/, cmd/, kiln/, core-ui/ — and on phrases like "add", "implement", "build", "refactor", "rename", "remove", "deprecate", "new feature", "new endpoint", "new field type", "API change", "expose", "wire up". Goal: docs ship in the same commit as the code, not "later".

2026-07-1712

kiln

DonaldMurillo/gofastr

Build a GoFastr web app live by calling Kiln over HTTP. Use ONLY on explicit Kiln signals — $KILN_URL env var set, the user names Kiln ("kiln serve", "the kiln world", "kiln freeze"), or IR-mutation phrasing against a running Kiln. Do NOT trigger on "GoFastr" alone or on generic "build me an app" requests: a user building with the framework directly writes Go against `framework/` and this skill would mis-route them into HTTP IR mutations.

2026-07-1612

adversarial-tests

DonaldMurillo/gofastr

How to run (or commission) an adversarial security-test pass against this codebase without producing 3000 lines of repetitive matrix tests. Auto-loads when the user mentions "red tests", "adversarial tests", "security test pass", "find security gaps", or is about to spawn a sub-agent to author *_security_test.go files. Encodes the "property × surface, not case × file" rule, the naming + triage policy, and a ready-to-paste prompt template for the next pass.

2026-07-1612

name	gofastr-mcp-debug
description	Live debug a running GoFastr app via its MCP endpoint — combined entry point covering both the log_* tools (battery/log) and the app_* introspection tools (framework). Use when the user wants to "debug the live app", "see what's going on right now", "tell me about the running server", or any general "go look at the running app" prompt.

Debug a running GoFastr app live (one-page guide)

This skill is the starting point for any agent investigation of a running GoFastr app via MCP. For deep recipes, jump to:

.claude/skills/log-debug/SKILL.md — the four log_* tools (recent entries, structured filter, metrics, level mutation).
.claude/skills/app-introspect/SKILL.md — the ten introspection tools: app_routes, app_plugins, app_batteries, app_modules, app_config, app_readiness, app_routines, plus framework_docs_list / framework_docs_get / framework_docs_search for the embedded framework docs.

When to use which

User asks…	Reach for
"What just happened?" / "Why is X failing?"	`log_recent`, `log_filter` (log-debug)
"Trace request ID abc-123"	`log_filter` with `request_id` + `historical=true`
"Is the app ready?"	`app_readiness` (app-introspect)
"What endpoints exist?"	`app_routes` (app-introspect)
"What plugins / batteries are loaded?"	`app_plugins`, `app_batteries` (app-introspect)
"What modules are enabled?"	`app_modules` (app-introspect)
"Did my routine body change propagate?"	`app_routines` (app-introspect) — ledger_state=drifted flags it
"Turn module X off / back on"	`app_module_disable`, `app_module_enable` (mutating)
"How does framework feature X work?"	`framework_docs_search` → `framework_docs_get`
"Are the logs even working?"	`log_metrics` — non-zero counters = lost entries
"Crank up DEBUG for 30 seconds, then back"	`log_set_level DEBUG` → reproduce → `log_set_level INFO`

Getting started

Outside the dev loop, the app opts in explicitly:

fwApp := framework.NewApp(
    framework.WithMCP(),                    // mounts /mcp (POST + GET SSE) + discovery well-knowns
    framework.WithMCPIntrospection(),       // app_* + framework_docs_* tools (read-only)
    framework.WithMCPControl(),             // app_module_enable/disable (mutating — trusted /mcp only)
)
fwApp.RegisterPlugin(log.New(log.Config{
    EnableMCP:   true,                       // log_* tools
    MCPRingSize: 2000,
}))

./scripts/dev-watch.sh         # examples/site on :8082, auto-rebuild
# or
go run ./examples/site         # :8083 — plain go-run has no PORT set

Then point curl at http://localhost:8082/mcp (or :8083 for go-run) and use the log-debug + app-introspect skills' recipes.

The JSON-RPC envelope

All tool calls are POST /mcp with body:

{
  "jsonrpc": "2.0",
  "id": 1,
  "method": "tools/call",
  "params": {
    "name": "<tool_name>",
    "arguments": { ... }
  }
}

Anti-patterns

Don't reach for MCP when grepping the file directly is easier. If the user knows exactly what they're looking for and has shell access, tail -f ~/.local/state/<app>/server.log | grep … may be the right move. MCP wins when the agent (not the user) is the consumer.
Don't curl tools you don't know the shape of. tools/list first if you're not sure what's registered; the descriptions are written for agents.
Don't forget to revert state mutations. log_set_level is the only mutating tool right now, but treat it like a temporary debug toggle: flip on, reproduce, flip off.