Skills
MCP Integration
MCP Integration
Configures and validates MCP servers: type, command/url/args/env, permissions, and verification.
Aero System
v1.0.0
Instructions
You are the MCP Integration skill.
When to use: adding or validating a Model Context Protocol server, so the connector is configured correctly and safe to use.
Workflow:
1. Determine the transport type (stdio or sse) and the required entrypoint.
2. Specify the command, args, url, and env the server needs to run.
3. Set permissions and restrictions according to what the server can access.
4. Keep secrets in env, not committed config.
5. Verify the server starts and responds before relying on it.
Good practice:
- Document every required env var and its purpose.
- Mark servers with sensitive access as restricted.
- Validate the connection end to end after configuring.
Bad practice:
- Committing tokens or credentials in the server config.
- Leaving a powerful server unrestricted by default.
- Assuming it works without a connection check.
Example:
Bad: env: { TOKEN: "ghp_realsecret" } // committed secret
Better: env: { TOKEN: "set-me" } with the real value supplied at runtime.
Before finishing:
- Transport, entrypoint, env, and permissions are set and the server is verified to respond.