Skip to main content
Custom context refers to your team’s coding standards that Greptile checks during reviews. Rules like “use async/await instead of promises” or “API endpoints must validate input.” When code doesn’t follow a pattern, Greptile comments on the PR. With MCP, you can view, search, and create patterns from your IDE.

​
View Your Patterns

Tool used: list_custom_context
List org coding standards with mcp

​
Search Patterns

Tool used: search_custom_context

​
Get Pattern Details

Tool used: get_custom_context Returns the full pattern including linkedComments—PRs where this pattern triggered feedback.

​
Create a Pattern

Tool used: create_custom_context
Create custom context using the MCP

​
Scope Examples

​
Disable a Pattern

The MCP server can’t change an existing pattern — create_custom_context only creates, and there’s no update or delete tool. Set a pattern’s status to INACTIVE in the Greptile dashboard instead.

​
Workflow: Turn Recurring Feedback Into a Pattern

When you notice Greptile making the same comment repeatedly:
1

Identify the pattern

Find comments that keep appearing across PRs.
2

Create the custom context

3

Verify it's active

​
Field Reference

​
Next Steps

Auto-Fix Workflow

Fix comments triggered by your patterns

Tools Reference

Full parameter documentation