Quick Start

Connect Slack, send a message, and serve MCP tools quickly.

This guide walks you through connecting Slack, executing an action, and setting up an MCP server. By the end, you'll have a working integration that AI agents can use.

Want the fastest path? Open Templates in the dashboard and choose a starter pack. Templates create a workspace, add per-user integrations, and can create an OAuth CODE-mode MCP server in one flow.

Before using the setup in production, test it in Playground and add a Human Gates policy for actions that send external messages, change customer data, spend money, or use end-user credentials.

Prerequisites

  • A Weavz account with an API key (Installation)
  • A Slack workspace you can connect (Weavz provides the OAuth app — no setup needed)
1

Create a Workspace

Workspaces scope your integrations, connections, and MCP servers. Create one to get started.

  1. Navigate to Workspaces in the sidebar
  2. Click Create Workspace
  3. Enter the name "My Workspace" and slug my-workspace
  4. Click Create
2

Connect Slack

Weavz provides platform OAuth apps for services like Slack, so you don't need to create your own. Just open the hosted connect popup, log in to Slack, and authorize.

  1. Open your workspace and go to the Connections tab
  2. Click Create Connection
  3. Select Slack from the integration picker
  4. Click Authorize — a popup opens with Slack's consent screen
  5. Approve access — the popup closes and your connection appears in the list
3

Add Slack to the Workspace

Register the connected Slack account as a workspace integration. This gives it a stable alias and lets actions, MCP servers, partials, approvals, and Playground use the same workspace-level configuration.

  1. Open your workspace and go to the Integrations tab
  2. Click Add Integration
  3. Select Slack
  4. Set the alias to slack_bot
  5. Choose Fixed connection and select the Slack connection you just created
  6. Save the workspace integration
4

Send a Slack Message

Now execute through the workspace integration alias. This keeps the same connection strategy and guardrails available to API calls, SDK calls, Playground, and MCP servers.

  1. Open the Playground from the sidebar
  2. Select your workspace from the dropdown
  3. Pick the Slack integration
  4. Choose the Send Channel Message action
  5. Enter a channel name and message text
  6. Click Execute and view the result

The response contains the Slack API result:

json
{
  "success": true,
  "output": {
    "ok": true,
    "channel": "C01234567",
    "ts": "1234567890.123456",
    "message": {
      "text": "Hello from Weavz!",
      "type": "message"
    }
  }
}
5

Create an MCP Server

MCP servers let AI agents use your integrations as tools. Start with Code Mode for agents: it exposes three meta-tools so the agent can search available actions, read typed APIs, and execute multi-step workflows without loading every tool schema upfront.

  1. Navigate to MCP Servers in the sidebar
  2. Click Create Server
  3. Enter the name "My AI Tools", select CODE mode, and pick your workspace
  4. Click Create
  5. Copy the MCP endpoint from the server details. New servers use MCP OAuth by default, and workspace integrations such as slack_bot sync automatically.
6

Connect an AI Client

Use the MCP server endpoint to connect an OAuth-capable AI client. Weavz handles MCP OAuth sign-in when the client connects.

In Claude, open Customize > Connectors, add a custom connector, and paste the MCP endpoint:

text
https://api.weavz.io/mcp/srv_{serverId}

For Claude Code:

bash
claude mcp add --transport http weavz https://api.weavz.io/mcp/srv_{serverId}

Now ask Claude or Cursor to "send a message to #general in Slack" and watch it search, read the Slack API shape, and execute the action through Code Mode.

What's Next

You've connected Slack via OAuth, sent a message, and set up a Code Mode MCP server. Here's where to go from here:

  • Connections — learn about auth types, multi-tenant scoping, and the hosted connect flow
  • Actions — explore action execution patterns and input schemas
  • MCP Servers — configure CODE and TOOLS modes
  • Input Partials — save parameter presets and enforce values
  • Triggers — receive real-time events from integrations
  • Integrations — browse all 500+ available integrations