Skip to content
Weavz
Menu
MOCO

MOCO MCP integration

Manage MOCO projects.

Sign in, add MOCO in Apps, then choose the account your AI can use.

3 tools
Use withChatGPTClaudeClaude CodeCursorCodexMCP clientsSetup guide

Get started with MOCO

  1. Add MOCO to your Weavz workspace and connect the account you want to use.
  2. Review the available tools below and enable the actions your task needs. Check the account permissions before allowing changes.
  3. Connect a compatible AI client to your workspace, or use the actions API from your application.

Tools

Name

List Projects

list_projects

List projects for the connected account.

Get Project

get_project

Get a project by ID.

Rename Project

rename_project

Update the project name.

Quick Start

TypeScript
import { WeavzClient } from '@weavz-io/sdk'

const weavz = new WeavzClient({ apiKey: 'wvz_...' })

const result = await weavz.actions.execute('moco', 'list_projects', {
  workspaceId: '550e8400-e29b-41d4-a716-446655440000',
  integrationAlias: 'moco',
  input: { /* ... */ },
})

Related Integrations

Explore integrations in other categories

Frequently Asked Questions

Is there a MOCO MCP server through Weavz?

Yes. Add the MOCO integration to a Weavz workspace, enable the actions you need and connect any required account. Weavz provides the workspace MCP endpoint in Tool Mode or Code Mode. The catalog currently lists 3 MOCO actions.

What can an AI agent do with MOCO?

Available actions include List Projects, Get Project, Rename Project. Your workspace exposes only the actions you enable. The agent also needs the intended account access and any required input values.

How do I connect MOCO to Claude or ChatGPT?

Use a compatible remote MCP client, add the Weavz connector and choose a workspace. Add MOCO, connect the required account and review the enabled actions. Client availability and account requirements vary; adding the connector does not authorize every app automatically.

Can I use MOCO through an API or SDK?

Yes, supported actions can run through the Weavz REST API, TypeScript SDK or Python SDK. Configure a workspace and the required connections, use scoped access, and pass the intended end-user context when acting for a customer.

What authentication does MOCO require?

The catalog lists custom credentials for MOCO. Use Hosted Connect to authorize the intended account. Required permissions, provider app access and available connection methods depend on the integration.

How do I review sensitive MOCO actions?

Limit enabled actions, scope credentials to the intended user and configure Human Gates for the operations that need review. A matching policy can pause a send, record change or other sensitive action for an approver before execution.

What limits or costs apply to MOCO?

Weavz plan limits apply to the actions and resources you use. The external provider may also require an account, a paid plan, API credits or specific permissions, and may enforce its own rate limits. Check current Weavz pricing and the provider’s terms before rollout.

Connect MOCO in minutes

Get 20,000 free action executions every month. No credit card required.