tools list.
GitHub
GitHub is connected during setup. Repository access follows the GitHub app installation. See IP allow lists and Enterprise Managed User sign-in for restricted organizations.Slack
A Slack admin needs to authorize the connection. DM Macroscope or mention@Macroscope in a channel to ask Macroscope questions. Add the Macroscope app to private channels it needs to access.
Slack subscription commands send commit summaries, PR activity, and build failures to channels.
Linear
Authorize all public teams or selected teams. Macroscope can read and create issues and track project progress. For tools beyond the native integration, see Linear MCP. Ask it to break an existing issue into sub-issues, naming the parent identifier, for example “Break ENG-431 into sub-issues, one per migration step.” Each sub-issue is a first-class issue that can be assigned, estimated, and tracked independently. It inherits the parent’s team unless you request another. Sub-issues are Linear-only; asking for one in Jira returns an error.Jira
Macroscope inherits the authorizing Jira account’s permissions. Use a dedicated account scoped to the projects the workspace should access; those projects become available to teammates with Macroscope access. Change that account’s permissions and reauthorize to update scope. Some sites require an admin to allow Macroscope under Atlassian Administration → Apps → Connected apps.LaunchDarkly
Provide an access token with the Reader role. The agent reads projects, environments, flags, and targeting rules.PostHog
Provide a personal API key, region (US or EU), and default project. Use an organization-scoped key for access across multiple projects. The agent can query analytics, trends, feature flags, recordings, and HogQL.Sentry
Provide the organization slug and an auth token withevent:read, project:read, and org:read. Select sentry.io, us.sentry.io, de.sentry.io, or a self-hosted URL. The agent reads issues and event history.
BigQuery
Provide a GCP project ID and service account JSON key with BigQuery Data Viewer and BigQuery Job User roles. Queries are read-only. Optional connection instructions can explain datasets and business terminology.GCP Cloud Logging
Provide a GCP project ID and service account JSON key with Logs Viewer. Optional instructions can explain log sources. The agent filters by severity, resource, timestamp, and payload.Amplitude
Provide a project API key, secret key, and region (US or EU). The agent queries segmentation, funnels, retention, and user event streams.MCP connectors
Workspace admins can connect MCP servers with a server URL and its required OAuth credentials or headers. Review the discovered tools and disable any the agent should not use.Access controls for workspace-scoped MCP connectors
Workspace connectors are shared by default. The connection’s Access tab restricts invocation to an allowlist of users.Personal MCP connections
Connect a personal server from Settings → Personal → MCP Connections without admin access. It is available only to you and uses your identity. Servers must use public HTTPS and OAuth 2.1; endpoint discovery and client registration are automatic. Reconnect or disconnect from the same settings page. Personal connections are separate from shared workspace connectors.MCP in automated agents
Addmcp to tools in a Check Run Agent or in .macroscope/approvability.md to give the agent your MCP connectors:
tools replaces the defaults, so also list any default tools you still need, such as modify_pr.
These agents run without a requesting user, so they use only active workspace connectors without an allowlist; personal MCP connections are not available. If none can be used, mcp is disabled for that run and the check’s details include a warning.