Guide library · 42 real routes
Implementation guides that lead to the next right step.
For MCP operators, agent builders, and runtime troubleshooters—choose a setup, fix, comparison, or workflow guide without scanning an unrelated directory.
SETUP 23 · TROUBLESHOOTING 1 · COMPARISON 5 · WORKFLOW 13
Recommended first
Check the MCP security boundary before connecting a new server.
Verify source identity, permission scope, exact-client behavior, credentials, logs, and rollback before enabling writes.
Open security checklistThis checklist verifies
- 01Source identity and the exact package route
- 02Permission scope, credentials, and data exposure
- 03Read-only proof, logs, and a bounded rollback path
Full guide library
Browse all 42 guides without opening 42 tabs.
Every real route is visible below. Filter by outcome or search the title, stage, summary, and best-use guidance.
Showing 42 of 42 guides
23 guides
Setup
Install, configure, and validate a new agent or MCP environment.
1 guide
Troubleshooting
Recover a broken or drifting environment without resetting blindly.
5 guides
Comparison
Choose a stack, framework, coding surface, or operating model.
13 guides
Workflow
Turn useful agent patterns into repeatable team operations.
One job, one next guide
Open the guide that matches the decision in front of you.
All eight existing decision routes are retained below, so the richer page does not hide useful operator guidance.
Common implementation questions
Answers that help you choose the right next guide.
What is the difference between the guides hub and the main skills directory?
The skills directory helps you discover tools and capabilities quickly. The guides hub is for implementation detail, rollout decisions, troubleshooting, and operating patterns after discovery.
Which guide should I read first for Neon MCP onboarding?
Start with the npx neonctl@latest init guide if you need the exact CLI setup path. Move to the NeonCtl MCP init guide when you need the broader rollout policy and team baseline.
Are these pages only for one editor or one agent runtime?
No. The hub is organized by outcome: setup, troubleshooting, comparison, and workflow. Most guides call out where editor-specific or runtime-specific behavior matters.
How should teams use this hub during implementation?
Use the start-here paths first, open one guide that matches the current bottleneck, and only add a second guide when the problem changes from setup to troubleshooting or from implementation to operating model.
When should I leave the guides hub and go back to skills pages?
Return to the skills directory when you are exploring tooling options. Stay in the guides hub when you already know the tool and need steps, guardrails, validation, or workflow decisions.
Where should I start for MCP server discovery or browser automation?
Start with the MCP Apps directory when source verification matters, the Best MCP Servers guide when you need a shortlist, and the MCP browser automation scenario when the work involves page rendering, screenshots, or web task execution.
Need a safer first step?
Open the MCP security checklist before connecting a new server.
Review permissions, credentials, transport, data exposure, and rollback before installation.