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

# Working with Connectors

> Alloy’s MCP server integrates with hundreds of SaaS platforms. Each integration is represented by a **connector**. Connectors expose **resources** (e.g., channels, users, contacts) and **actions** (e.g., create a task, send a message). This guide explains how to work with them using the MCP tools.

## Discover Available Connectors

Call the `list_connectors` tool to retrieve all connectors.

* Optionally filter by category: `communication`, `crm`, `marketing`, `storage`, etc.
* The response includes connector IDs and descriptive names.
* Use these IDs when calling other tools.

## Inspect Resources and Actions

Use `get_connector_resources` to discover what a connector supports:

* Pass the `connectorId` (e.g., `slack`, `hubspot`).
* The server returns supported **resources** and **actions**.

Use `get_action_details` to retrieve:

* Required and optional parameters.
* Descriptions, data types, and sample values.

## Execute an Action

To invoke an action, call `execute_action` with:

* `connectorId`: Which platform to use (e.g., `slack`).
* `actionId`: Action identifier (e.g., `chat_postMessage`).
* `parameters`: JSON object containing input values (e.g., channel ID, message text).
* `credentialId` (optional): Specify which credential to use if multiple exist.

The MCP server forwards the request and returns the platform’s response.

Example: Slack MCP lets assistants read messages, post replies, search conversations, and list users or channels.

## Manage Credentials

Most connectors require credentials (OAuth or API keys):

* Use `create_credential` to initiate an OAuth flow.
  * Include `connectorId`, `authenticationType`, and `redirectUri`.
* For key-based auth, include fields directly in the `fields` object.
* Call `get_credentials` to list existing credentials.
* Use `get_credential_metadata` to check supported auth methods and required fields.