Getting-started Prompts
Once your MCP server is connected, you can dive right in.
Here are a few prompts to try. They work out of the box with agents like Cursor, Claude, or VS Code:
💡 Starting your request with “Use groundcover” is a helpful nudge - it pushes the agent toward MCP tools and context.
Basic Prompts to Try
MCP supports complex, multi-step flows, but starting simple is the best way to ramp up.
Pull Logs
Prompt:
Expected behavior:
The agent should call query_logs
and show recent logs for that workload.
Get K8s Resource Specs
Prompt:
Expected behavior:
The agent should call get_k8s_object_yaml
and return the YAML or a summary of it.
Find Slow Workloads
Prompt:
Expected behavior:
The agent should call get_workloads
and return the relevant workloads with their P95 latency.
Investigate Issues
When something breaks, your agent can help investigate and make sense of it.
Paste an Issue Link
Prompt:
Expected behavior:
The agent should use query_monitors_issues
, pull issue details, and kick off a relevant investigation using logs, traces, and metadata.
Investigate Multiple Issues
Prompt:
Expected behavior:
The agent should use query_monitors_issues
to pull all related issues and start going through them one by one.
Automate Coding & Debugging
groundcover’s MCP can also be your coding sidekick. Instead of digging through tests and logs manually, deploy your changes and let the agent take over.
Iterate Over Test Results
Prompt:
Expected behavior:
The agent should update the code with log statements, deploy it, and use query_logs
to trace and debug.
Deploy & Verify
Prompt:
Expected behavior: The agent should assist with deployment, then check for issues, error logs, and traces via groundcover.
Last updated