CursorAI-powered code editor
OAuth
ClaudeOfficial connector for Claude.ai, Desktop & mobile
OAuth
Official Claude connector
- Open the Wiv listing in the Claude Connectors Directory
- Choose “Add to Claude” and complete the Wiv OAuth sign-in
Claude Desktop
- Open Settings → Connectors
- Click “Add connector” and paste the server URL
- Complete the OAuth sign-in when prompted
Claude.ai
- Go to Settings → Connectors → Add custom connector
- Paste the server URL and complete the sign-in
VS CodeVisual Studio Code with Copilot
OAuth
ChatGPTOpenAI ChatGPT with MCP
OAuth
- Open Settings → Connected apps
- Click “Add MCP server”
- Paste the server URL and complete the sign-in flow
Gemini CLIGoogle Gemini command line
OAuth
Add to your settings.json:
WindsurfCodeium Windsurf editor
OAuth
Amazon Quick & API key clientsHeader-based auth when OAuth is unavailable
API key
Prefer User authentication (OAuth) in Amazon Quick when discovery works. If your client only supports custom headers:
- Create a Wiv organization API key in the Wiv app (Avatar → API Keys).
- Add a remote MCP server with URL
. - Add header
x-api-keywith your API key value (use the secret/locked field when available). - Test the connection — invalid keys are rejected with
401 Unauthorized.
Docs: API key authentication
Before you connect
Prerequisites. You need an active WIV account and membership in a WIV organization. Your org admin can invite you if you do not have access yet.
What you are granting. When you sign in with OAuth, this MCP server receives an authorization from WIV (via PropelAuth). The server exchanges that for a short-lived context and creates or uses a WIV API key scoped to your organization so tools can call the WIV API on your behalf—workflows, cases, executions, spaces, datastores, and related resources your role is allowed to access.
OAuth flow (summary).
- You add the MCP URL (shown above) in your AI client and start the connection.
- Your browser opens WIV sign-in (PropelAuth).
- After success, the client receives credentials to call this server; the server forwards requests to
api.wiv.ai(or the configured API base) with your API key.
API key alternative. Clients that cannot complete OAuth (for example Amazon Quick with custom headers only) may send a Wiv organization API key as X-API-Key / x-api-key. The server validates the key against the Wiv API at connect time. Prefer OAuth when your client supports it.
Revoking access. Remove the connector in your AI client settings. You can also rotate or revoke API keys from your WIV / PropelAuth account settings as your organization allows.
About this connector
WIV is a workflow automation platform for operations teams. This remote MCP server exposes the WIV Workflow API through the Model Context Protocol so assistants like Claude can list and run workflows, inspect executions, work with cases, manage spaces and folders, query datastores, create and edit dashboards, and (for MSP tenants) onboard customers and cloud integrations—within your existing permissions.
Transports. The service supports Streamable HTTP at /mcp (recommended for new clients; protocol 2026-07-28 with legacy client fallback) and SSE at /sse (still supported for legacy clients). OAuth 2.0 with PKCE is used for sign-in; dynamic client registration and client ID metadata documents (CIMD) are supported. OAuth scopes: mcp:tools, mcp:resources. You can also authenticate with a Wiv organization API key via the X-API-Key header.
Capabilities (high level).
- 63 tools — workflows, executions, cases, spaces, integrations, datastores, dashboards, MSP
- 341 MCP resources — step/widget catalogs and authoring guides (see Resources)
- 6 prompts — quick-start templates for common assistant tasks
- MCP Tasks — async AI workflow generation via
wiv_generate_workflow(Tasks-capable clients poll withtasks/getandtasks/result)
- Workflows: list, get, create, update, patch, step catalog, AI generate + poll
- Step templates: browse catalog or read
wiv://catalog/stepsresources - Executions: start, stop, list, status, step output
- Cases: search, summaries, filters, MSP-scoped queries
- Spaces & folders: list, create, update, archive, move resources
- Integrations: list, get, create, update, delete (tenant and MSP customer)
- Datastores: list, create, delete, schema, query, create/update/delete records
- Dashboards: list, get, create, update, patch, delete; widget template catalog
- MSP: list customers, cross-tenant cases, customer onboarding, AWS links, integrations, user invites
Workflow authoring. Prefer MCP resources wiv://catalog/steps and wiv://guides/workflow-authoring (or tools wiv_list_step_templates / wiv_get_step_template), then wiv_create_workflow or wiv_update_workflow to publish. For metadata-only edits use wiv_patch_workflow. For AI drafts use wiv_generate_workflow — Tasks-capable clients pass task metadata and poll via MCP Tasks; otherwise poll with wiv_get_generated_workflow. The create_or_edit_workflow prompt guides assistants through the full flow.
Dashboard authoring. Prefer wiv://catalog/widgets resources (or wiv_list_widget_templates / wiv_get_widget_template), then wiv_update_dashboard (full PUT) to write widgets into layout. Create may omit dashboard_id — list dashboards by space/name to find it. Filter Group is dashboard-level filters, not a layout widget. Filtering is supported only for Workflow and Datastore widgets when supports_filter_bindings is true; dropdown options use static options and/or optional datastoreId (not a workflow).
Multiple organizations. If your account belongs to more than one org, sign-in shows a searchable org picker with every membership (MSP parent and customer orgs). Connect as the MSP parent for read-only customer_id access across tenants, or select a customer org to write with that org's permissions. Reconnect at /connect to switch orgs.
MSP customer access. After connecting as your MSP org, use wiv_list_msp_customers to list child tenants. Pass optional customer_id on regular tools (workflows, cases, spaces, executions, datastores, dashboards) to operate in a customer's tenant.
Available tools
63 tools — each annotated for hosts that require hints: READ read-only (idempotent) · WRITE may create/update data or start side effects (destructive ops always prompt in Claude).
Workflows
wiv_list_workflowsList workflows (paginated, searchable)wiv_get_workflowGet workflow detailswiv_create_workflowCreate a new workflowwiv_update_workflowReplace workflow (full update including steps)wiv_patch_workflowPatch workflow metadata onlywiv_list_step_templatesBrowse step template catalogwiv_get_step_templateGet step parameter schemawiv_generate_workflowStart async AI workflow generation (MCP Tasks or poll wiv_get_generated_workflow)wiv_get_generated_workflowPoll AI generation statusSpaces & folders
wiv_list_spacesList spaceswiv_get_spaceGet space detailswiv_create_spaceCreate a spacewiv_patch_spaceUpdate space metadatawiv_delete_spaceDelete a spacewiv_archive_spaceArchive a spacewiv_unarchive_spaceRestore an archived spacewiv_move_space_resourcesMove resources into a spacewiv_get_space_resourcesResources in a spacewiv_list_foldersList workflow folderswiv_get_folderGet a folderExecutions
wiv_start_executionStart / run a workflowwiv_stop_executionStop a running executionwiv_list_all_executionsList executions (all workflows)wiv_list_workflow_executionsList executions for one workflowwiv_get_execution_statusExecution statuswiv_get_step_outputStep output for an executionCases
wiv_list_casesList caseswiv_search_casesSearch caseswiv_get_cases_summaryCase statisticswiv_get_cases_filtersAvailable filterswiv_get_cases_filter_valuesFilter valueswiv_cases_queryFlexible OpenSearch querywiv_search_msp_casesMSP: search child-tenant caseswiv_get_msp_cases_summaryMSP: case summarieswiv_get_msp_cases_filter_valuesMSP: filter valueswiv_list_msp_cases_typesMSP: case typeswiv_msp_cases_queryMSP: OpenSearch queryDatastores
wiv_list_datastoresList datastoreswiv_get_datastoreSchema and detailswiv_create_datastoreCreate a datastorewiv_delete_datastoreDelete a datastorewiv_query_datastore_recordsQuery recordswiv_create_datastore_recordsCreate recordswiv_update_datastore_recordUpdate a recordwiv_delete_datastore_recordDelete a recordDashboards
wiv_list_dashboardsList dashboardswiv_get_dashboardGet dashboard (layout, filters, colors)wiv_create_dashboardCreate dashboardwiv_update_dashboardReplace dashboard (full PUT including widgets)wiv_patch_dashboardPatch dashboard metadata onlywiv_delete_dashboardDelete dashboardwiv_list_widget_templatesBrowse widget template catalogwiv_get_widget_templateGet widget schema and example panelIntegrations
wiv_list_integrationsList integrations (searchable, paginated)wiv_get_integrationGet integration details (no secrets)wiv_create_integrationCreate tenant integrationwiv_update_integrationUpdate integration metadatawiv_delete_integrationDelete integrationMSP customer onboarding
wiv_list_msp_customersList MSP child tenant IDs and nameswiv_create_msp_customerCreate MSP customer orgwiv_generate_aws_onboarding_linkAWS CloudFormation onboarding linkwiv_create_customer_integrationCreate cloud integration for a customerwiv_add_customer_usersAdd users to customer orgMCP resources
341 resources — static catalogs and authoring guides exposed via resources/list and resources/read. Prefer these over tool calls when discovering step or widget schemas.
Catalog & guides
wiv://catalog/stepsStep template index (308 templates) — JSONwiv://catalog/steps/{step_template_id}Full parameter schema for one step (e.g. TRIGGER) — JSONwiv://catalog/widgetsWidget template index (29 templates) — JSONwiv://catalog/widgets/{widget_template_id}Widget schema and example panel — JSONwiv://guides/workflow-authoringWorkflow JSON rules (TRIGGER/EXIT, linking) — Markdownwiv://guides/dashboard-authoringDashboard layout, widgets, filters — MarkdownClients that support MCP resources will list per-template URIs automatically (e.g. every step and widget ID). Server instructions on connect also reference these URIs.
Quick-start prompts
Pre-built prompts for common workflows. Select these from your MCP client to jumpstart tasks without typing full instructions.
Available prompts (6)
workflow_overviewGet a summary of all workflows and their purposescheck_recent_executionsCheck status of recent workflow executions (optional: hours parameter)triage_open_casesReview and prioritize open cases needing attentionrun_workflowStart a workflow with guided parameter input (requires: workflow_name_or_id)workflow_health_reportGenerate health report for all workflows with execution success ratescreate_or_edit_workflowCreate or edit a workflow with step catalog guidance (requires: goal; optional: workflow_id)Privacy & security
This page is served over HTTPS. For directory and compliance, link to this section as:
What we collect
- Authentication data: OAuth authorization codes and tokens during sign-in; temporary mapping between tokens and WIV API keys in server memory.
- Account context: Organization identifiers and user identifiers as returned by PropelAuth / WIV when you sign in, to scope API keys and requests.
- Tool usage: Requests your AI client sends to this MCP server (tool names and parameters) are forwarded to the WIV API; they are not stored by this MCP service for analytics.
How we use it
- To authenticate you and authorize calls to the WIV API on your behalf.
- To maintain your MCP session while connected (including short-lived caching of resolved credentials to reduce repeated token exchange).
Storage & retention
- In-process caches (e.g. token-to-key mapping) are bounded and time-limited (on the order of one hour unless configured otherwise).
- Authorization codes used in the OAuth code flow expire within minutes.
- Long-lived API keys are issued and revoked through WIV / PropelAuth; this server does not define separate retention beyond what your identity provider stores.
Third parties
- PropelAuth — authentication, OAuth, and API key management for WIV.
- WIV API — source of truth for workflows, cases, and tenant data.
- AWS — hosting (e.g. App Runner) for this MCP service.
Security measures
- TLS (HTTPS) for client-to-server traffic.
- OAuth 2.0 with PKCE for compatible clients; optional API key header for trusted configurations.
- Token introspection for opaque tokens before issuing WIV API keys.
Your choices
- Disconnect the connector in your AI product settings at any time.
- Use org and identity settings in WIV / PropelAuth to manage users, roles, and API keys.
Contact
Questions about this connector or your data: support@wiv.ai · wiv.ai