> ## Documentation Index
> Fetch the complete documentation index at: https://docs.macroscope.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Integrations

> Connect your tools to give the agent more context and capabilities

Each integration gives the agent access to new data and actions. All integrations are configured in **Settings → Connections**. For a full list of what the agent can do with each tool, see the [tools reference](/agent#tools).

## GitHub

Connected automatically during setup. No additional configuration needed.

## Slack

The primary way most teams interact with Macroscope. DM Macroscope or tag `@Macroscope` in any channel to query the agent.

Macroscope also streams real-time code activity into Slack channels via `/macroscope` commands. Use `/macroscope subscriptions` to view a channel's subscriptions, or `/macroscope help` for the full command list.

<Accordion title="Slack Subscription Commands">
  <a id="slack-subscription-commands" />

  * `/macroscope subscribe <repo>`: all activity from a repo
  * `/macroscope subscribe-commits <repo>`: commit summaries (includes linked Jira and Linear tickets)
  * `/macroscope subscribe-prs <repo>`: PR activity, with live emoji reactions as PRs are ✅ approved, 💬 commented, or 🚀 merged
  * `/macroscope subscribe-build-failures <repo>`: build failures

  <Tip>
    Add `--paths=` to any command to filter to specific parts of a repo (e.g. `--paths=/frontend`).
  </Tip>
</Accordion>

<Info>
  A Slack admin can connect Slack in **Settings → Connections → Slack**.
</Info>

## Linear

The agent can look up issues, track project progress, and create new issues. When you connect Linear, you choose which teams Macroscope can access.

<Accordion title="Linear Setup Instructions">
  <Steps>
    <Step title="Go to Settings → Connections">
      Scroll down to the **Linear** section.
    </Step>

    <Step title="Sign in to Linear">
      Click **Connect Linear** and sign in with your Linear account.
    </Step>

    <Step title="Choose Team Access">
      Linear will prompt you to choose which teams Macroscope can access. Select **all public teams** or **only select teams**.

      <img src="https://mintcdn.com/macroscope/0PeyCrC3lZQzg_YJ/images/linear-permissions.png?fit=max&auto=format&n=0PeyCrC3lZQzg_YJ&q=85&s=0e86492ae0ed815c5e27de832bbfa9de" alt="Linear permissions selection example" width="936" height="794" data-path="images/linear-permissions.png" />

      Click **Authorize** to complete.
    </Step>
  </Steps>
</Accordion>

## Jira

The agent can look up tickets, track project progress, and create new issues. Macroscope inherits the permissions of the Jira account that authorizes the integration.

<Tip>
  We recommend creating a dedicated Jira user for Macroscope, scoped to the specific Projects you want Macroscope to access. For Google Workspace teams, create an email alias like `linda+macroscope@yourcompany.com` and use it for the Jira account.
</Tip>

<Accordion title="Jira Setup Instructions">
  <Steps>
    <Step title="Go to Settings → Connections">
      Scroll down to the **Jira** section.
    </Step>

    <Step title="Sign in to Jira">
      Make sure you are logged out of any personal Jira accounts first. Click **Connect Jira** and sign in with the account you want to authorize for Macroscope.

      <Info>
        In some cases, a Jira site admin may need to manually authorize the connection:

        1. Go to Atlassian Administration → Apps → \[your-site].atlassian.net → Connected apps
        2. Find Macroscope and click Authorize/Allow for the site.
      </Info>
    </Step>

    <Step title="Review Project List">
      You'll see a list of Projects that Macroscope has been granted access to. These will be accessible to anyone on your team with Macroscope access.

      To modify the list, update the permissions of the authorizing Jira account and re-authorize.

      Click **Confirm Access** to complete.
    </Step>
  </Steps>
</Accordion>

## LaunchDarkly

The agent can list feature flags, projects, and environments, and check flag status and targeting rules.

<Accordion title="LaunchDarkly Setup Instructions">
  <Steps>
    <Step title="Go to Settings → Connections">
      Scroll down to the **LaunchDarkly** section.
    </Step>

    <Step title="Generate an Access Token">
      In LaunchDarkly, go to **Settings → Authorization → Create Token**. Assign the **Reader** role.
    </Step>

    <Step title="Paste Token">
      Copy the token and paste it into the Macroscope connection modal. Click **Connect**.
    </Step>
  </Steps>
</Accordion>

## PostHog

The agent can query product analytics events, analyze trends, and inspect feature flags.

<Accordion title="PostHog Setup Instructions">
  <Steps>
    <Step title="Go to Settings → Connections">
      Scroll down to the **PostHog** section.
    </Step>

    <Step title="Create a Personal API Key">
      In PostHog, go to **Settings → Personal API Keys → Create**. Copy the key.

      <Tip>
        Use an organization-scoped API key for flexibility across multiple projects.
      </Tip>
    </Step>

    <Step title="Connect to Macroscope">
      Select your region (US or EU), paste your API key, and click **Next**.
    </Step>

    <Step title="Select a Project">
      Macroscope will auto-fetch your projects. Select a default project and click **Connect**.
    </Step>
  </Steps>
</Accordion>

## Sentry

The agent can search error issues across projects, view issue details and event history, and investigate crashes and exceptions.

<Accordion title="Sentry Setup Instructions">
  <Steps>
    <Step title="Go to Settings → Connections">
      Scroll down to the **Sentry** section.
    </Step>

    <Step title="Select Your Instance">
      Choose your Sentry region: **sentry.io**, **us.sentry.io**, **de.sentry.io**, or enter a custom URL for self-hosted instances.
    </Step>

    <Step title="Generate an Auth Token">
      In Sentry, go to **Settings → Auth Tokens** and create a token with the following scopes: `event:read`, `project:read`, `org:read`.
    </Step>

    <Step title="Connect">
      Paste the auth token, enter your organization slug, and click **Connect**. Macroscope will validate your credentials automatically.
    </Step>
  </Steps>
</Accordion>

## BigQuery

The agent can browse datasets, inspect table schemas, and run read-only SQL queries. Answers include a methodology summary so you can verify the analysis.

<Accordion title="BigQuery Setup Instructions">
  <Steps>
    <Step title="Go to Settings → Connections">
      Scroll down to the **BigQuery** section.
    </Step>

    <Step title="Create a GCP Service Account">
      In Google Cloud Console, create a service account with **BigQuery Data Viewer** and **BigQuery Job User** roles. Generate a JSON key file.
    </Step>

    <Step title="Connect to Macroscope">
      Enter a connection name, your GCP Project ID, and upload the service account JSON key (or paste it directly). Optionally add prompt instructions to give the agent context about your data.

      Click **Create** to complete.
    </Step>
  </Steps>
</Accordion>

## GCP Cloud Logging

The agent can search and filter application logs across connected GCP projects.

<Accordion title="GCP Cloud Logging Setup Instructions">
  <Steps>
    <Step title="Go to Settings → Connections">
      Scroll down to the **GCP Cloud Logging** section.
    </Step>

    <Step title="Create a GCP Service Account">
      In Google Cloud Console, create a service account with **Logs Viewer** role. Generate a JSON key file.
    </Step>

    <Step title="Connect to Macroscope">
      Enter a connection name, your GCP Project ID, and upload the service account JSON key (or paste it directly). Optionally add prompt instructions to give the agent context about your logs.

      Click **Create** to complete.
    </Step>
  </Steps>
</Accordion>

## Amplitude

The agent can run event segmentation queries, analyze conversion funnels and retention, and inspect individual user event streams.

<Accordion title="Amplitude Setup Instructions">
  <Steps>
    <Step title="Go to Settings → Connections">
      Scroll down to the **Amplitude** section.
    </Step>

    <Step title="Get Your API Credentials">
      In Amplitude, find your **API Key** and **Secret Key** in your project settings.
    </Step>

    <Step title="Connect to Macroscope">
      Enter a connection name, select your region (US or EU), paste your API Key and Secret Key, and optionally add prompt instructions.

      Click **Create** to complete.
    </Step>
  </Steps>
</Accordion>

## MCP Connectors

Connect any [MCP-compatible server](https://modelcontextprotocol.io/) to extend the agent with custom tools (e.g. Datadog, PagerDuty, or your own internal APIs). Configure MCP Connectors from **Settings → Connections → MCP Servers** (admin only).

<Accordion title="MCP Setup Instructions">
  <Steps>
    <Step title="Go to Settings → Connections">
      Scroll down to the **MCP Connectors** section.
    </Step>

    <Step title="Enter Server URL">
      Paste the MCP server URL and click **Discover**. Macroscope will auto-detect the server's authentication method.
    </Step>

    <Step title="Configure Authentication">
      Depending on the server, you may need to provide OAuth credentials (Client ID and Secret), custom headers, or no authentication.
    </Step>

    <Step title="Select Tools">
      Review the tools the server provides. Toggle off any tools you don't want the agent to use. Click **Connect**.
    </Step>
  </Steps>
</Accordion>

### Access Controls

By default, all workspace members can use an MCP connector's tools. To restrict access to specific users:

1. Open the MCP connection in edit mode.
2. Switch to the **Access** tab.
3. Add users to the allow list.

Only users on the allow list can invoke the connector's tools. Connections with restricted access display a badge and tooltip in the connection list so admins can see which connectors are limited at a glance.