Skip to main content

​
What are Integrations?

Nectr integrations pull live context into every PR review — linked issues, production errors, team discussions, and more. By connecting external tools via the Model Context Protocol (MCP), Nectr’s AI reviewer gains a complete picture of what’s happening across your engineering stack.

​
Available Integrations

GitHub

OAuth, webhooks, and REST API for PR data, issues, and review comments

Linear

Pull linked issues and task context via MCP during PR reviews

Sentry

Surface production errors for files changed in a PR

Slack

Fetch relevant channel messages as review context

​
How Integrations Work

Nectr uses two integration patterns:

​
1. Native REST APIs

GitHub is the only native integration. Nectr directly calls the GitHub REST API to fetch PR diffs, files, issues, and post review comments.
  • Required: GITHUB_PAT, GITHUB_CLIENT_ID, GITHUB_CLIENT_SECRET
  • Managed by: app/integrations/github/client.py

​
2. MCP Protocol (Inbound)

All other integrations (Linear, Sentry, Slack) use the Model Context Protocol. Nectr acts as an MCP client and pulls context from external MCP servers during reviews.
  • Optional: Each integration requires an _MCP_URL and API key
  • Managed by: app/mcp/client.py
  • Behavior: If an MCP server is not configured, Nectr logs a warning and continues the review without that context (graceful degradation)

​
Outbound MCP Server

Nectr also exposes its own review data as an MCP server so external tools (Linear bots, Claude Desktop, Slack apps) can pull PR verdicts, contributor stats, and repo health metrics.

Nectr MCP Server

Expose Nectr’s review data to external MCP clients

​
Configuration

All integrations are configured via environment variables in .env. See the Environment Variables reference for details.

​
Quick Start

  1. GitHub (required for all reviews): 
    GITHUB_PAT=ghp_...
GITHUB_CLIENT_ID=...
GITHUB_CLIENT_SECRET=...
  2. Linear (optional — enriches reviews with linked issues): 
    LINEAR_MCP_URL=http://linear-mcp-server:8001
LINEAR_API_KEY=lin_api_...
  3. Sentry (optional — shows production errors for changed files): 
    SENTRY_MCP_URL=http://sentry-mcp-server:8002
SENTRY_AUTH_TOKEN=...
  4. Slack (optional — includes relevant channel messages): 
    SLACK_MCP_URL=http://slack-mcp-server:8003

​
Next Steps

MCP Protocol

Understand how Nectr uses the Model Context Protocol

GitHub Setup

Configure OAuth, webhooks, and PAT tokens

Run MCP Server

Expose Nectr’s data to external MCP clients

Build docs developers (and LLMs) love

Get started for freeTalk to us