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

# Set up the Trello MCP server

> Create a Trello API key and token, then register the Trello MCP server in C1 and govern the tools it exposes.

<Note>
  **Activation required.** AI access management must be enabled for your tenant before you can use it. To get started, [contact the C1 support team](mailto:support@c1.ai) for a walkthrough.
</Note>

The Trello MCP server lets you govern access to Trello — boards, lists, cards, members, and organizations — as tools your AI clients call through C1.

Trello authenticates with an API key paired with a token. The token is authorized against a single Trello account, so all tool calls reach Trello as one shared identity.

## How C1 connects to Trello

C1 hosts the Trello MCP server, so your users' AI clients only ever see MCP tools — they never call Trello directly. When an AI client calls one of these tools, C1 makes the matching request to the Trello API using the credentials you configure here, then returns the result to the AI client.

The credentials you set up below are what C1 uses to call Trello on your users' behalf.

## Before you begin

* AI access management must be enabled for your tenant. See [Enable AI access management](/product/admin/enable-ai-access-management).
* A Trello account that can create a Power-Up to obtain an API key, and that can authorize a token carrying the access you want to govern.

<Note>
  If you don't see **Trello** in your MCP server catalog, [contact the C1 support team](mailto:support@c1.ai) to enable it for your tenant.
</Note>

## Create a Trello API key and token

Create an API key and authorize a token so C1 can call Trello on your account's behalf.

<Steps>
  <Step>
    Sign in to Trello and create a new Power-Up, then open it to generate an **API key**. For the full procedure, see Trello's [Get started with Trello's REST API](https://support.atlassian.com/trello/docs/getting-started-with-trello-rest-api/) documentation.
  </Step>

  <Step>
    Copy the **API key**.
  </Step>

  <Step>
    From the same page, use the **Token** link to authorize a token for your account. Grant the token the access you want to govern, then copy the **token**. Trello shows the token only once.
  </Step>
</Steps>

For a shared production setup, authorize the token from a dedicated service-account user so activity is attributable to C1 rather than a person.

## How Trello credentials are shared

Every user's tool calls use the one API key and token you provided, so Trello sees a single shared identity. C1 still attributes each call to the individual user in the [AI tool usage audit log](/product/admin/audit-ai-tool-usage). For a shared setup, authorize the token from a dedicated service-account user so activity is attributable to C1 rather than a person.

For how shared and per-user credentials work across MCP servers, see [Configure authentication](/product/admin/mcp-servers#configure-authentication).

## Register the Trello MCP server in C1

With your API key and token ready, register the server and provide your credentials.

<Steps>
  <Step>
    Follow [Register an MCP server](/product/admin/mcp-servers#register-an-mcp-server) and select **Trello** from the catalog.
  </Step>

  <Step>
    When you [configure authentication](/product/admin/mcp-servers#configure-authentication), choose **Custom header** and enter your Trello **API key** and **token** in the fields provided.
  </Step>

  <Step>
    Save your changes. C1 starts a sync that discovers the tools the Trello server exposes.
  </Step>
</Steps>

## Discover and govern tools

After you register the server, C1 runs tool discovery against Trello. Discovered tools appear on the server's **Tools** tab.

Each tool starts as either **Pending review** or automatically **Approved**, depending on the option chosen when the server was set up or your tenant's default tool settings in **Settings** > **AI Connections**. See [Require tool approval](/product/admin/enable-ai-access-management#require-tool-approval) and [Default tool classification](/product/admin/enable-ai-access-management#default-tool-classification).

Before anyone can call a Trello tool, it must be approved, added to a toolset, and bound to an access profile. Continue to [Govern tools and toolsets](/product/admin/tools-and-toolsets) to set this up.

<Note>
  Tool discovery runs even if your credentials are incorrect, so seeing discovered tools doesn't confirm that authentication is working. You confirm your Trello credentials when an approved user successfully calls a Trello tool from their AI client.
</Note>

## Manage your Trello credentials

* **Rotate the token** by authorizing a new token in Trello, updating it in C1, then revoking the old token from the account's connected apps.
* **Adjust access** by authorizing the token under an account that has the boards and organizations you want to govern.