Skip to content
Weavz
Menu

Connect your own AI

Set up Weavz in Claude, ChatGPT, Codex, Cursor or another compatible client, connect your apps and complete a first task.

Use the AI client you already have with your own app accounts. You do not need to build an integration or create an API key.

Add Weavz to your client

Choose a client in the setup grid. Some clients offer a connection link; others need a command or configuration. ChatGPT account and workspace settings can affect whether a custom app is available. Follow the client-specific guide rather than assuming an app is already listed in a public directory.

The remote MCP URL is:

text
https://platform.weavz.io/mcp/weavz

Complete the browser sign-in. If you have multiple workspaces, choose the workspace during authorization. A connector belongs to that workspace and your end-user identity. To use another workspace, reconnect and choose it during authorization.

Connect an app

Ask your AI to open Weavz. In clients that support an embedded MCP app, the app view lets you find an integration and connect an account. If your client does not show the view, follow the connection link or use the dashboard.

Choose an app and complete its sign-in or credential form. Review the app's requested permissions. Use the connection form for credentials, rather than pasting passwords or access tokens into a conversation.

Complete a first task

Start with a task you can inspect:

  • Find the latest email thread about a project and summarize the next steps.
  • Read an issue and its comments, then draft a response.
  • Find the document that explains a process and link the relevant section.

Your AI can also perform actions, including sending messages or changing records, when those actions are available. New workspaces permit all configured app actions by default. Add an optional approval rule when you want a matching action to pause for review.

Use Activity in the dashboard to inspect what ran. A failed connection, rejected approval or expired session is not a completed action.

Add an approval rule only when you need one

Open Advanced → Approval rules. Choose the app and action that should require review, then choose who can review it. For example, require approval before sending a message. Other actions continue under the workspace's normal access.

If a task pauses for approval, open the request, inspect its action and inputs, and approve or reject it. The request's status shows whether execution resumed or needs another step.

Saved inputs are optional. Use them for values an action should reuse, such as a destination channel. Leave them empty when the agent should choose inputs for each task.

Recover a connection

If an app is disconnected or its authorization expired, reconnect that account and retry the task. Check Activity before repeating a write if the result was uncertain; a lost response does not prove that an action failed.

If a client sign-in no longer works, reconnect Weavz in that client. Do not change workspaces inside the embedded app. If an app view is unavailable, the standard MCP tools and dashboard links remain the fallback.

See plans and capacity for action, storage and execution allowances. Connected accounts and workspaces are unlimited on every plan.