---
title: "Connecting MCP servers"
description: "Connect Indent to hundreds of tools from Integrations, or register your own server, at organization or personal scope."
---

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

# Connecting MCP servers

import { McpDirectory } from "@/components/mdx";

An MCP server gives Indent a set of tools it can use during a session. Indent ships a catalog of
hundreds of them, so most of the tools your team already uses are a click away. Start with one or
two that match your most common workflows, and add more as you go.

## Browse integrations

Browse and connect servers from [**Integrations**](https://app.indent.com/integrations). The catalog
spans the categories teams reach for most, including issue tracking, docs, CRMs, observability,
analytics, and payments:

- **Issue tracking and docs** — Linear, Notion.
- **Observability** — Datadog, Sentry.
- **CRM and support** — HubSpot, Plain.
- **Analytics and experimentation** — Amplitude, Statsig.
- **Payments** — Stripe, PayPal.

A few have dedicated setup pages — [Linear](/connecting/linear), [Notion](/connecting/notion),
[Datadog](/connecting/datadog), and [Sentry](/connecting/sentry) — but the rest connect the same way
from Integrations.

## Custom MCP servers

When a tool has no listing in Integrations, register its MCP server and Indent uses it like any
other, including internal APIs and documentation systems.

In [**Integrations**](https://app.indent.com/integrations), select **Create custom integration**.
The form asks for:

- **Endpoint URL** — the server's address.
- **Display name** — how the integration appears in Indent.
- **Connect for** — whether the connection is for your organization or your personal account.
- **Transport** — Streamable HTTP or SSE, under **Advanced**.
- **Authentication** — OAuth, API token, Basic auth, custom headers, or none, under **Advanced**.
- **Description** — an optional explanation of what the server provides, under **Advanced**.

## Change or remove a connection

For an organization connection, open the connected server from
[**Integrations**](https://app.indent.com/integrations) and select **Edit connection**. For a
personal connection, select **View details**. On the connection page, select **Edit config** to
replace static credentials or change other editable settings. Saved tokens and headers are hidden,
so re-enter them to save any change. **Test connection** checks the settings before you select
**Save changes**. OAuth connections also use **Reconnect** to renew authorization. If an OAuth
connection exposes editable configuration, **Edit config** remains available and reconnects when you
save.

For a custom MCP server, an admin can select **Rename** to change its display name. Its endpoint,
transport, authentication method, and description cannot be changed after registration. Delete and
register the custom integration again to change those fields.

**Disconnect** removes the selected organization or personal connection. Where the server supports
revocation, Indent also revokes its access.

Admins can choose **Delete integration** on a custom server, which disconnects everyone using it.

Indent keeps its own copy of each server's tool list, refreshed every few minutes. A server that's
slow or briefly unreachable doesn't stall a session; when a call does fail, Indent reports what the
server returned and decides whether to retry.

## Reconnect a connection that needs attention

A connection marked **Needs attention** means one of two things: its sign-in has expired, or Indent
has started asking for a permission that connection was never granted. In the second case the
connection keeps working for everything it could already do, and only the new capability fails.

Open the connection and select **Reconnect** to authorize the permissions Indent asks for today.
Reconnecting updates the connection you already have, at the same scope, rather than adding a second
one.

## Scopes

Every integration connects at one of two scopes:

- **Organization** — the connection is shared with your team, and anyone in the organization can use
  it.
- **Personal** — the connection is owned by you, and only you can use it. Open
  [**Integrations**](https://app.indent.com/integrations), select the server, and select **Connect
  personal account**. Personal integration tools work only in a
  [private session](/collaborating/personal-and-private).

Teammates can see whether you have connected a personal account, but they cannot use it.

When a server authorizes a person rather than an application — as Notion's hosted MCP server does —
an organization-scoped connection inherits the permissions of whoever completed the flow. Authorize
those as a service account your team owns, not from a personal account; see
[Connecting Notion](/connecting/notion#use-a-service-account-for-organization-scope) for the
pattern.

Listed and custom MCP servers can support personal connections. Database connections, GitHub App
installations, and the Slack workspace app are organization-scoped. GitHub and Slack also offer
personal account connections.

Source: https://docs.indent.com/connecting/mcp-servers/index.mdx