# Path

Path MCP for SlackConnection guide

# Bring Slack context to Scout.

Find the conversations that matter and turn them into useful answers, with your Slack account’s permissions.

[Read the setup guide](https://path.dev/connect/slack#setup)[Contact support](https://path.dev/support)

![](/path-app-icon.png)+![](/logos/slack.svg)

Availability

## Customer access is not open yet.

Path MCP must complete Slack’s Marketplace review before it can connect customer workspaces. Creating a Path account does not unlock this connection.

The steps below describe setup once access is available. Contact support for the current status.

## Connect from your Scout chat.

Once available, installation starts in Path and continues through Slack’s permission screen.

1.  01
    
    ### Open a private Scout chat
    
    Sign in to Path and open your own private conversation with Scout. You need a Path account and a Slack account in the workspace you want to connect.
    
2.  02
    
    ### Ask to connect Slack
    
    Ask Scout: “Connect my Slack account using Path MCP.” Follow the connection link Scout provides. If the connection is not available, contact Path support.
    
3.  03
    
    ### Review access in Slack
    
    Check that the app is named Path MCP and that you have selected the right Slack workspace. Review the permissions before approving. Your workspace may require an administrator to approve the app first.
    
4.  04
    
    ### Return to Scout
    
    Start with a search or a summary of a channel you can access. If you connect more than one account, tell Scout which one to use. Review and confirm any proposed action that changes Slack content.
    

[Sign in to Path](https://console.path.dev/login)

Signing in does not install Slack or grant access.

## Know what you’re connecting.

Path MCP connects your Slack account to Scout. You choose whether to authorize the requested access.

### Search and read context

Permissions cover searching and reading conversations, files, profiles, channel information, canvases, and lists. Private channels and direct messages require the relevant permission and access through your Slack account.

### Review actions before they run

Requested permissions also include sending messages, creating conversations, adding reactions, and working with files, canvases, and lists. Scout asks for confirmation before running actions that change Slack. Available tools depend on your connection and granted permissions.

### A connection for your private chat

This connection belongs to you and is for your private, attended Scout conversations. It is separate from the Slack Connector used by customer apps. Connecting here does not share your Slack account with an App or other Path users.

[Looking for the Slack Connector for an App?](https://path.dev/guides/integrations/slack)

### Disconnect when you need to

Open your personal connections in Path, choose your Slack MCP connection, and select Disconnect. You can also revoke authorization in Slack. Disconnecting does not delete information already saved in a conversation. Contact support to request deletion of data held by Path.

## Questions before connecting?

Contact Path support for availability, workspace approval, connection issues, or data requests. You do not need a Path account to get help.

[support@path.dev](mailto:support@path.dev)

Relevant Slack content may be processed by Path’s AI providers to answer your requests. Read how connected data is used, retained, and deleted before authorizing access.

[Privacy policy](https://path.dev/legal/privacy)[Connector privacy](https://path.dev/legal/privacy/integrations)[Terms of service](https://path.dev/legal/terms)[Support](https://path.dev/support)[Path plans](https://path.dev/pricing)

Source: https://path.dev/connect/slack