IDE Setup

Greptile MCP uses OAuth for authentication.

OAuth setup

OAuth signs you in through your browser. You do not need to register an OAuth client.

Cursor
Claude Code
VS Code
Codex

Open MCP settings

Open Customize and select MCPs.

Add Greptile

Add this configuration to project-level .cursor/mcp.json or user-level ~/.cursor/mcp.json:

{
  "mcpServers": {
    "greptile": {
      "url": "https://api.greptile.com/mcp"
    }
  }
}

Ask Cursor:

List my Greptile custom context rules.

On the first protected tool call, follow the browser prompt to sign in.

Verify the connection

Run the same prompt again. A successful list_custom_context result confirms authentication. Seeing Greptile’s tools in settings confirms discovery, but not authentication.

Add Greptile

Run:

claude mcp add --transport http greptile https://api.greptile.com/mcp

Start OAuth explicitly:

claude mcp login greptile

Alternatively, open Claude Code, run /mcp, select greptile, and choose Authenticate.For an SSH or headless session, run claude mcp login greptile --no-browser. Open the printed URL, then paste the final redirect URL into the terminal when prompted.

Verify the connection

Run:

claude mcp list

Then ask Claude:

List my Greptile custom context rules.

A successful result confirms authentication.

Shared project configuration

To share the server definition with your team, create .mcp.json in the project root. Each developer authenticates separately.

{
  "mcpServers": {
    "greptile": {
      "type": "http",
      "url": "https://api.greptile.com/mcp"
    }
  }
}

Add an MCP server

Open the Command Palette and run MCP: Add Server.

Enter the server URL

Choose HTTP, enter https://api.greptile.com/mcp, then select Global or Workspace.

In chat, ask VS Code:

List my Greptile custom context rules.

On the first protected tool call, follow the browser prompt to sign in.

Verify the connection

Run the same prompt again. A successful list_custom_context result confirms authentication. A Running status in MCP: List Servers confirms discovery, but not authentication.

The equivalent mcp.json entry:

{
  "servers": {
    "greptile": {
      "type": "http",
      "url": "https://api.greptile.com/mcp"
    }
  }
}

Add Greptile

Run:

codex mcp add greptile --url https://api.greptile.com/mcp

Start OAuth explicitly:

codex mcp login greptile

In the Codex IDE extension, open MCP servers, select Greptile, then select Authenticate.

Verify the connection

Run:

codex mcp list

Then ask Codex:

List my Greptile custom context rules.

A successful result confirms authentication.

Shared project configuration

Add this entry to .codex/config.toml. Each developer runs codex mcp login greptile separately.

[mcp_servers.greptile]
url = "https://api.greptile.com/mcp"

Troubleshooting

The server connects, but tool calls are unauthorized

MCP discovery can succeed before authentication is complete. Run claude mcp login greptile or codex mcp login greptile. In Cursor or VS Code, invoke a protected tool such as list_custom_context, then finish the OAuth prompt.

OAuth is not offered

A static Authorization header or bearer-token setting from an earlier setup can prevent OAuth sign-in. Remove it from the Greptile server entry, restart the client, then invoke a protected tool such as list_custom_context to start the OAuth prompt.

The OAuth browser does not open

Claude Code users can run claude mcp login greptile --no-browser and open the printed URL manually. In Cursor or VS Code, invoke a protected tool such as list_custom_context to trigger authentication.

Tool calls return tenant_required

Your account belongs to multiple Greptile organizations. Ask your agent to call get_me to list them, then pass the organization’s handle or id as the organization argument on subsequent tool calls.

No tools are available

Restart the client, confirm Greptile is enabled, and check that the server URL is exactly https://api.greptile.com/mcp.

Tools return empty results

Confirm that your organization has repositories indexed in Greptile and that your user account can access them.

Configuration file locations

Client	Configuration file
Claude Code	`~/.claude.json` or project `.mcp.json`
Cursor	`~/.cursor/mcp.json` or project `.cursor/mcp.json`
VS Code	User-profile `mcp.json` or project `.vscode/mcp.json`
Codex	`~/.codex/config.toml` or project `.codex/config.toml`

OAuth setup

Shared project configuration

Shared project configuration

Troubleshooting

Configuration file locations

Next steps

Auto-Fix Workflow

Tools Reference

​OAuth setup

​Shared project configuration

​Shared project configuration

​Troubleshooting

​Configuration file locations

​Next steps

Auto-Fix Workflow

Tools Reference

OAuth setup

Shared project configuration

Shared project configuration

Troubleshooting

Configuration file locations

Next steps