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

# Connect an MCP Server

## Overview

MCP servers enable deeper and more flexible integrations beyond standard Apps. MCP stands for Model Context Protocol and provides a standardized way to connect external systems. Agents can then access data and run more complex, granular actions across systems.

MCP servers suit advanced use cases, custom integrations, and technical workflows. A curated list of common MCP servers is available, and custom servers can be added manually when needed.

## Connect an MCP server

Any MCP server can be connected from the workspace settings, whether it comes from the catalog or is a custom server you host yourself. A short wizard inspects the server, handles authentication, and enables selection of the exact tools available to agents.

### Step by step

1. Open the workspace settings, select *MCP Servers*, and choose *Add server*.
2. Enter the server URL and, optionally, a display name, then select *Verify*. nuwacom inspects the server and detects its transport type (StreamableHTTP or SSE), whether authentication is required, and which authentication method applies.
3. Name the connection and provide the credentials for the detected authentication method (see Authentication methods).
4. Select *Test connection*. nuwacom connects to the server and discovers the available tools. If the connection fails, the error returned by the server is displayed so the settings can be adjusted.
5. Select the tools to enable for agents, then confirm to create the connection.

<Info>
  Enabled tools, the connection name, sharing, and removal can be changed at any time under Connectors in the workspace settings.
</Info>

## Authentication methods

nuwacom auto-detects how a server expects authentication and displays only the relevant fields:

* No authentication: Public servers that require no credentials. The URL is verified and setup continues.
* API key / token: The server is protected by a static API key or bearer token. A stored credential is selected for the connection. For OAuth servers, this method is also available via *Use API key / token instead* in the advanced options.
* OAuth: The server uses OAuth 2.0. nuwacom suggests the best mode based on the server's discovery metadata (see the OAuth modes below).

## OAuth modes

When a server uses OAuth, the method for obtaining a token can be selected:

* **Automatic (recommended):** Sign-in runs through the browser. The client registers itself automatically with the provider via Dynamic Client Registration (DCR), so no credentials are entered. This works for most servers.
* **Browser login with your own credentials:** Sign-in runs through the browser using a Client ID and Secret from an OAuth app registered with the provider. Use this when the server does not support automatic registration.
* **Client Credentials (M2M):** The connection uses a Client ID and Secret directly, without browser login. This covers machine-to-machine (M2M) access such as CI/CD pipelines, server-to-server integrations, and automated workflows. It is available only for servers that support the OAuth client credentials grant.
* **Manual configuration:** The Authorization URL, Token URL, Client ID, and Secret are entered manually. Use this when a server does not expose its OAuth discovery metadata.

> **Tip:** To limit access, open *Advanced settings* in the connection step and specify custom OAuth scopes (space- or comma-separated). Leaving the field empty requests the scopes the server advertises.

<Info>
  Not every server supports every mode. Many hosted MCP servers offer only browser-based login. Machine-to-machine (M2M) access requires the server to support the OAuth client credentials grant.
</Info>


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.