Quick Start

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

This guide walks you through connecting Slack, adding it to a workspace, creating an MCP server, and connecting an AI client. It includes a direct action execution smoke test, but the main path is the MCP server your agents will 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.

Building an app-owned agent harness? Use the AI-Native SaaS Path after this walkthrough. It covers end-user auth, MCP bearer tokens, and the production provisioning loop.

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.

Choose the connection model

Most production apps use workspace integrations as the stable layer and let the connection strategy decide whose credentials are used at runtime.

ModelUse whenRuntime selector
Fixed/shared connectionOne bot, team account, or service credential should serve the whole workspaceworkspaceId + integrationAlias
Per-user connectionEach signed-in user must act through their own connected accountworkspaceId + integrationAlias + endUserId
Per-user with fallbackUse a user's account when connected, otherwise fall back to a shared accountworkspaceId + integrationAlias + optional endUserId
Direct connection external IDYour backend needs to target one specific credential set outside the workspace integration strategyworkspaceId + connectionExternalId

This quick start uses a simple shared Slack connection first. For customer-facing agents, read Managing End Users after the first loop and switch the workspace integration to per_user or per_user_with_fallback.

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 office_slack
  5. Choose Fixed connection and select the Slack connection you just created
  6. Save the workspace integration
4

Optional: Smoke Test Direct Execution

Before connecting an AI client, you can smoke test the workspace integration directly. This is useful for validation, but production agent flows should usually continue through the MCP server created in the next step.

  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 office_slack sync automatically.

This quick-start uses the minimum useful payload. New servers default to authMode: "oauth", endUserAccess: "restricted", and settings.codeMode.approvalWaitSeconds: 0. For Code Mode approval waits or bearer-provisioned clients, pass optional server fields:

json
{
  "settings": { "codeMode": { "approvalWaitSeconds": 30 } },
  "authMode": "oauth_and_bearer",
  "endUserAccess": "restricted"
}

See MCP Servers for every create field, and MCP Code Mode for the agent-focused setup.

Sandbox execution policy, such as timeout and persistence, is configured on the advanced-code workspace integration, not on the MCP server itself.

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, configured a workspace integration, created a Code Mode MCP server, and connected an AI client. Here's where to go from here:

  • AI-Native SaaS Path — provision workspaces, end-user auth, MCP servers, and per-user MCP tokens for app-owned agent harnesses
  • 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 Mode and Tool Mode
  • Input Partials — save parameter presets and enforce values
  • Triggers — receive real-time events from integrations
  • Integrations — browse all 500+ available integrations