Connect Slackbot

Slackbot can act as an MCP client: once a Slack app that declares an MCP server is installed in a workspace, members connect it and ask Slackbot to use its tools. Slack calls the server from its own infrastructure over HTTPS using Streamable HTTP, which is what the Scrive MCP uses, so no bridge is needed.

Surface	Connection	Status
Slackbot MCP client	Slack app declaring https://mcp.scrive.com/mcp	Supported, needs OAuth client credentials, see below
Slackbot with a Scrive app from the Slack Marketplace		Not available, Scrive does not publish one today

What you need

Requirement	Why
Permission to create and install a Slack app	Org and Workspace Owners and Admins, or members allowed to install apps. The Slackbot MCP client is available on all Slack plans
An OAuth client ID and secret issued by Scrive	Slack’s Manual OAuth auth type needs a client registered with Scrive’s authorization server, with Slack’s redirect URL https://oauth2.slack.com/external/auth/callback on it. See When you need a client ID and secret
Each member’s own Scrive account	Every member authorises individually and Slackbot acts as them

Choosing an auth type

Slack offers four auth types for an app’s MCP server. Use Manual OAuth: you enter the client ID and secret from Scrive and the authorization and token URLs, and each member signs in to Scrive when they connect the app. Dynamic client registration would be simpler but requires the authorization server to support it, which Scrive’s does not. Slack identity auth and No auth do not work, because the Scrive MCP requires a bearer token issued by Scrive.

Step 1: declare the MCP server in a Slack app

1. Go to api.slack.com/apps and create an app (from scratch) in your workspace, or open an existing internal app.

2. In the sidebar under Features, open MCP Servers and select Get Started.

3. Enter a Name (Scrive), the URL (https://mcp.scrive.com/mcp) and set Auth type to Manual OAuth. Fill in:

   Field	Value
   Client ID, Client Secret	Issued by Scrive
   Authorization URL	https://oauth2.scrive.com/oauth2/auth
   Token request URL	https://oauth2.scrive.com/oauth2/token
   Use HTTP Basic Authentication	On, unless Scrive tells you otherwise
   Use PKCE	On
   OAuth scopes	full (press Enter to add it)

   Leave the optional identity fields and custom headers empty and save. Slack adds the mcp:connect bot scope automatically. If you manage the app as code, declare the server under mcp_servers in the manifest with "auth_type": "manual_auth" and the OAuth settings under external_auth_providers.

4. Under OAuth & Permissions select Install to Workspace (or Install to Organization on Enterprise) and authorise the app. On Enterprise plans an Org Owner or Org Admin installs it from Organization settings → Integrations → Manage apps and adds it to workspaces.

Step 2: connect Slackbot

1. Open a DM with Slackbot and click the Apps button in the toolbar.

2. Select + next to the Scrive app. You are redirected to Scrive to sign in and approve access.

3. Ask Slackbot:

   Which of my Scrive documents are still waiting for a signature?

   Slackbot asks Allow once, Always allow or Deny before running tools. Choose Allow once for start_signing, remind_document, cancel_document, start_flow and delete_flow_draft.

Members can have at most five active MCP servers connected to Slackbot at a time. On Enterprise plans, admins can also decide which kinds of tools (read-only or write) are allowed by default and set permissions for individual tools. create_document, set_file and add_document_to_draft open a file picker panel on clients that support MCP Apps; Slackbot does not render it, so create documents from templates with create_from_template instead.

Remove

Members disconnect the app from Slackbot’s Integrations tab, under Manage. Admins remove the app from the workspace. See Revoke access.

---

Related reading

• Slack’s documentation: Connecting an MCP server to the Slackbot MCP client, Connect Slackbot to other apps with MCP
• Any MCP client
• Access & permissions