CursorAI-powered code editor
OAuth
ClaudeDesktop, Claude.ai & Claude Code
OAuth
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
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, this MCP server receives an OAuth 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.
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, and (for MSP tenants) onboard customers and cloud integrations—within your existing permissions.
Transports. The service supports Streamable HTTP at /mcp (recommended) and SSE at /sse. OAuth 2.0 with PKCE is used for sign-in; dynamic client registration is available for compatible clients.
Capabilities (high level).
- Workflows: list, get, update
- Executions: start, stop, list, status
- Cases: search, summaries, filters, MSP-scoped queries
- Spaces & folders: organization of workflows and resources
- Datastores: list, schema, query, create/update/delete records
- MSP: customer creation, AWS onboarding links, integrations, user invites
Available tools
Each tool is annotated for hosts that require hints: READ read-only / non-mutating · WRITE may change data or start side effects.
Workflows
wiv_list_workflowsList all workflowswiv_get_workflowGet workflow detailswiv_update_workflowUpdate an existing workflowSpaces & folders
wiv_list_spacesList spaceswiv_get_spaceGet space detailswiv_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 statusCases
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_query_datastore_recordsQuery recordswiv_create_datastore_recordsCreate recordswiv_update_datastore_recordUpdate a recordwiv_delete_datastore_recordDelete a recordMSP customer onboarding
wiv_create_msp_customerCreate MSP customer orgwiv_generate_aws_onboarding_linkAWS CloudFormation onboarding linkwiv_create_customer_integrationCreate cloud integrationwiv_add_customer_usersAdd users to customer orgQuick-start prompts
Pre-built prompts for common workflows. Select these from your MCP client to jumpstart tasks without typing full instructions.
Available prompts (5)
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 ratesPrivacy & 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