Skip to content
Weavz
Menu

Choose your Weavz experience

Connect apps to your own AI, or build customer integrations into your product with guided Project setup.

Weavz has two dashboard experiences. Choose the one that matches your task during signup, or switch from the menu at the top of the sidebar.

For your AI

Use the apps you already work with from Claude, ChatGPT, Codex, Cursor or another MCP client.

  1. Open Apps. Browse the full catalog, search by app or task, and filter by category. Connected shows ready apps; Shared shows accounts shared with your team.
  2. Open an app and review its tools. Choose For you to connect your own account, or For your team to explicitly share one account with authorized callers. Complete sign-in in the secure window.
  3. Open AI clients. Select your client and follow Guided setup, including the illustrated walkthrough and troubleshooting help. Advanced contains the configuration details.
  4. For Codex, Cursor and supported coding agents, Copy setup prompt gives your agent instructions to configure the connection. Review its proposed changes and complete OAuth yourself. The prompt preserves existing MCP configurations and asks the agent to verify available tools.
  5. Try a small task in your AI client, then inspect Activity if it needs attention.

Copying a prompt, following a walkthrough or opening an install link does not confirm that a client is connected. Verify a real tool listing or successful task in the client.

Your own account stays bound to your user. A shared account lets authorized callers use that account and its permissions. Choosing a shared account does not enable an automatic fallback to another person’s credentials. Advanced fallback routing is a separate, explicit setting.

Skills lets you save reusable task instructions for your AI. Approval rules and saved inputs are optional controls under Advanced.

For your product

Build apps and agents that use your customers’ connected accounts.

  1. Start in Getting started. Create an API key for your backend, or copy setup instructions for your coding agent. Keep the API key out of browser and mobile client code.
  2. Open Apps and choose an integration. Create an Auth configuration to define how customers connect. New configurations use each customer’s own account.
  3. Open Auth configurations to copy the configuration ID, edit its name or find advanced settings. Configurations and connected customer accounts are separate objects.
  4. Open Users to add the same external user ID your application uses. Your backend can create users through the SDK. A customer’s detail page shows their connections and can create a scoped, temporary app sign-in link.
  5. Use Testing to make a first call, then inspect Logs & activity. Connect the same setup through MCP, the SDK or API.

Project Members are your teammates. Users are the customer identities your product connects for; the directory labels any Project-member identities separately. Another person cannot connect an account on behalf of an authenticated teammate.

The Users directory supports paging and server-side search by user ID, display name or email. The SDK exposes the same search:

typescript
const { endUsers, total } = await client.endUsers.list({
  workspaceId,
  search: 'customer_123',
  limit: 50,
  offset: 0,
})
python
result = client.end_users.list(
    workspace_id, search="customer_123", limit=50, offset=0,
)

Search is case-insensitive and treats characters such as % and _ literally. The returned total matches the search. See managing end users for connection flows.

Projects and advanced setups

A Project groups your team, billing and app setup. Weavz prepares an execution workspace behind the main flows, so you do not need to create a separate MCP server before choosing an app. Existing API and SDK calls continue to use the workspace ID.

If you have one Project, Weavz can resume it after confirming your membership. If you belong to several, choose the Project you want. Existing Projects with several execution setups require an owner or admin to choose the default explicitly. Accounts, data and existing client grants stay in their original setup.

Advanced → MCP Workspaces retains detailed workspace management and existing links. Older account-setup links ask you to continue explicitly in advanced setup, keeping the requested workspace and account configuration. They do not silently use a different default. Open a workspace’s Connect your AI tab to choose Code Mode or Tool Mode. Owners and admins can save this setting; the URL stays the same. Refresh tools in your client after switching, and reconnect if Code Mode needs additional authorization.

A saved setup that was removed or suspended is not silently replaced. An owner or admin chooses an available replacement. Changing the dashboard default does not move credentials or retarget existing MCP grants.

For help with your first app or product integration, talk to our engineers.