Caseproof Ground Level MCP

Documentation

← Back to Home

IDE/CLI MCP Client Configuration

Any team member with an `@caseproof.com` email address can utilize the MCP. Requests to the MCP must be authenticated with a `Bearer` token which can be obtained by following these steps:

  1. Visit grdlvl-mcp.cspf.co
  2. Click the "Continue with Google" button
  3. Signin with your `@caseproof.com` Google Workspace account
  4. Authorize the application with the requested scopes
  5. Copy the MCP configuration JSON data and add it to your IDE/CLI's MCP configuration file

Available Prompts

This MCP server provides 6 pre-constructed prompts to help streamline common development workflows. Each prompt is designed to provide structured guidance and best practices for specific tasks.

You can use these prompts through any MCP-compatible client by referencing their name and providing the required arguments.

code-review
Get a structured code review checklist and guidelines
Arguments
language Optional
Programming language (php, typescript, javascript, etc.)
focus Optional
Specific focus area (security, performance, maintainability, etc.)
debug-session
Guide through a systematic debugging session
Arguments
issue Required
Description of the bug or issue
context Optional
Additional context (error messages, logs, etc.)
coding-standards
Run coding standards checks and optionally fix them
Arguments
language Required
Programming language (php, js, or ts)
fix Optional
Whether to fix the coding standards checks (y/n, default: y)
commit
Create well-structured commits for uncommitted changes
Arguments
No arguments required
report-issue
Report a GitHub issue
Arguments
description Required
Brief description of the issue to report
repository Optional
Repository to report the issue to (format: owner/repo)
open-pull-request
Open a GitHub pull request from a brief description
Arguments
description Required
Brief description of the changes for the pull request
base Optional
Base branch to merge into (e.g., main, develop)
head Optional
Head branch containing the changes (default: current branch)