Skip to content
Weavz
Menu

Your AI. Your apps. Ready to work.

Bring Gmail, Slack, Notion and your other apps into the AI you already use. Connect your accounts once, ask for the work you need, and see what your agent did. Add approval rules whenever you need them.

Try in Claude

You can start from the connector flow first; Weavz creates or signs in the account during authorization.

Connector details

Connect ChatGPT, Claude, or a coding agent to a Weavz workspace. The workspace decides which apps, credentials, files, state, browser tools, and approvals the agent can use.

ChatGPT
Claude
Coding agents
Weavz workspace
scoped tools, users, approvals, state, and audit
Connected apps
Connector name
Weavz MCP Workspace
Connector URL
https://platform.weavz.io/mcp/weavz
No Weavz account required before setup; the connector signs the user in during authorization.
One hosted MCP URL works in Claude, ChatGPT, and remote-MCP clients.
Your AI client uses the workspace you authorize. Reconnect it to use another workspace.
Connected app accounts stay behind Weavz approvals, aliases, state, files, and audit.
Full MCP availability depends on your plan. ChatGPT Pro custom MCP is read/fetch-only and cannot use the full Weavz offering.

Works with the AI you already use.

Choose your client. Sign in to Weavz and connect the apps you want to use. See the setup guides.

  • Claude

    Add to Claude
  • ChatGPT

    Setup guide
  • Codex

  • Cursor

  • Claude Code

  • OpenCode 1.x

  • OpenCode 2.x

    Open V2 MCP guide
  • Hermes

  • OpenClaw

  • Other HTTP MCP clients

Remote MCP with OAuth is required. Setup and embedded UI availability depend on your client and plan.

Start from the client in front of you.

What happens next

The connector is just the door. The workspace carries the control.

Authorize a workspace

Your AI client uses the workspace you authorize. Reconnect it to use another workspace.

Connect apps as yourself

Gmail, Slack, GitHub, Sheets, CRM, files, state, browser, and other aliases stay tied to the right user.

Review risky actions

Approval rules can pause external sends, shared writes, exports, spend, and customer-facing changes.

Coding agents

Use the same remote MCP resource from code-first clients.

Remote and local coding agents can connect to Weavz over MCP. Add the stable connector URL, complete Weavz sign-in, and the agent gets governed access to approved tools, files, state, and Human Gates through scoped app connections. Builders creating custom harnesses can provision MCP Workspaces with included endpoints and per-user tokens from the API or SDKs.

Codex
Use your connected apps from Codex, alongside your coding work.
codex mcp add weavz --url 'https://platform.weavz.io/mcp/weavz'
codex mcp login weavz
Cursor
Let Cursor Agent work with the apps in your MCP Workspace.
{
  "mcpServers": {
    "weavz": {
      "type": "http",
      "url": "https://platform.weavz.io/mcp/weavz"
    }
  }
}
Claude Code
Give Claude Code access to your connected apps while you work.
claude mcp add --transport http weavz 'https://platform.weavz.io/mcp/weavz'
claude mcp login weavz
claude mcp list
Gemini CLI
Add Weavz as a remote MCP server in Gemini CLI.
gemini mcp add --transport http weavz 'https://platform.weavz.io/mcp/weavz'
OpenCode 1.x
For OpenCode 1.x. Add Weavz to the project config, then authenticate from the CLI.
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "weavz": {
      "type": "remote",
      "url": "https://platform.weavz.io/mcp/weavz",
      "enabled": true
    }
  }
}
Running agents locally?

You can also use the Weavz CLI for terminal workflows: inspect workspace context, connect apps, search actions, run actions, and execute Code Mode from the same governed workspace.

CLI page
bash
brew install weavz/tap/weavz
weavz login

# or use npm
npm install -g @weavz-io/cli
weavz login

# no persistent install
npx -y @weavz-io/cli login

Before you connect your AI client

Choose one workspace and connect only the accounts you want that client to use.

Can I connect Claude, ChatGPT or Cursor to Gmail and Slack?

Use a client that supports remote MCP, add Weavz, sign in and choose your workspace. Connect the Gmail or Slack accounts you intend to use and enable the relevant actions. Client availability and plan requirements vary.

Does adding Weavz authorize every integration?

No. The catalog describes available integrations. Your workspace exposes its configured integrations and enabled actions, and account-based tools require their own connected credentials and permissions.

How do I change the workspace connected to my client?

Reconnect or reauthorize the Weavz connector and choose the other workspace. A connector token is scoped to the workspace and end user selected during authorization.