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.
You can start from the connector flow first; Weavz creates or signs in the account during authorization.
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.
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.
- Add to Claude
Claude
- Setup guide
ChatGPT
Codex
Cursor
Claude Code
OpenCode 1.x
- Open V2 MCP guide
OpenCode 2.x
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.
Claude
Open the prefilled connector setup, confirm Weavz Agent Workspace, and complete the Weavz authorization flow. You can create the account and workspace during setup.
Try in ClaudeChatGPT
ChatGPT does not currently provide a reliable prefilled custom connector link. Use the fields below when creating a connector in ChatGPT settings.
Coding agents
Remote and local coding agents can connect through MCP. Add the hosted Weavz URL to Codex, Claude Code, Cursor, OpenCode, VS Code, Gemini CLI, or any HTTP MCP client.
Set up in coding agentsThe 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.
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 mcp add weavz --url 'https://platform.weavz.io/mcp/weavz'
codex mcp login weavz{
"mcpServers": {
"weavz": {
"type": "http",
"url": "https://platform.weavz.io/mcp/weavz"
}
}
}claude mcp add --transport http weavz 'https://platform.weavz.io/mcp/weavz'
claude mcp login weavz
claude mcp listgemini mcp add --transport http weavz 'https://platform.weavz.io/mcp/weavz'{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"weavz": {
"type": "remote",
"url": "https://platform.weavz.io/mcp/weavz",
"enabled": true
}
}
}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.
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 loginBefore 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.