Skills vs MCP
Reusable instructions and executable tools solve different parts of the same task.
| Capability | Skills | MCP servers |
|---|---|---|
| Purpose | How to approach the task | Tools that retrieve data or perform actions |
| Contents | Instructions and supporting material | Tool descriptions, inputs and runtime |
| Setup | Install or assign a skill package | Select engine account, source and scope |
| Availability | Instructions can be read as context | Server startup and authentication are required |
| Combine them | Guide a repeatable workflow | Provide actions for that workflow |
How to decide
Start with the job you want to complete, then select the surface and permission level that make the result easiest to review. Provider access, model availability and charges remain governed by your selected accounts.
Instructions and tools have different jobs
A skill packages instructions for how to approach a task. An MCP server exposes tools that can perform actions or retrieve information. Installing instructions does not start a server, and seeing a configured server does not prove that it is connected.
Select the right account and scope
Connections discovers the selected engines’ redacted MCP configuration. The same server name can exist in several accounts or in user and project scope. Inspect the exact binding before changing it; a user binding can apply to more than one workspace.
- Check engine, account, source and scope.
- Inspect in the provider runtime before assuming connectivity.
- Review mutation confirmation and keep backups.
Browser tools through MCP
A compatible browser server can provide navigation, clicks, accessibility snapshots, screenshots and form filling. Firstbeam provides a Playwright configuration preset; the selected engine still starts and owns the server. Choose the account and project scope deliberately before saving the preset.
browser_navigate
browser_click
browser_snapshot
browser_take_screenshot
browser_fill_formIf a tool does not appear
Check whether the engine is reading the intended configuration, whether the command is installed and whether the server reports an authentication or startup error. Refreshing the inventory rereads configuration; it does not silently log you in or turn an unavailable tool into a connected one.
A browser check that stays bounded
For a local page, start the development server, navigate to its URL, inspect the accessibility snapshot, then click or fill the specific control you want to verify. Capture a screenshot of the resulting state. A screenshot alone does not prove the button action saved data; check the state or response that the action is supposed to change.
Diagnose configuration before changing it
If the same server name appears twice, compare account, source and scope rather than deleting one at random. If a server process cannot start, inspect its command and environment in the provider. If it starts but a tool is missing, inspect the exposed tool list and authentication state. Keep any credentials out of exported diagnostics.
Compare side by side
Choose a guide for the full table and practical setup steps.