Wapitee Remote MCP

Give an AI Agent a typed, permission-scoped interface to Wapitee GTM: Project → Web Form lead capture → versioned Survey research → analytics. Your Workspace remains the authorization boundary.

MCP v3.0.0
Streamable HTTP endpoint
https://gtm.wapitee.io/mcp
Projects & knowledge
Create and maintain pre-launch Projects, public knowledge sources, and research context.
Surveys & Web Forms
Design versioned Surveys, conditional flows, secure lead forms, and schema-on-read mini-surveys.
Analytics
Analyze dynamic Web Form answers and flow-aware Survey results with bounded database aggregates.
Documents
Create, version, search, and reuse Project Agent Markdown artifacts.
Brand media
Let an Agent securely upload PNG or SVG logos to private R2 and apply them to Workspace, Project, or Survey branding.
What changed in v3.0.0: Web Form schema version registry removed
The Web Form schema version registry and drift detection are gone. form_version is now a free-form sender label stored on every submission, and field schemas are derived on read from stored submission payloads.
  • Breaking: wapitee_manage_web_form_version is deprecated; every operation returns a DEPRECATED error and the tool is removed in the next release.
  • Breaking: Web Form submission listings return formVersion (sender label) instead of webFormVersionId.
  • Breaking: Web Form analytics/catalog versions entries no longer expose webFormVersionId, schemaHash, or kind; entries group submissions by the formVersion label.
  • Breaking: data profile answerFields no longer return versionIds; field schemas are derived from submission payloads.
  • Analysis queries accept a new formVersion text filter; versionId keeps working against historical data.
  • No data is affected: historical submissions, answers, and raw intake rows are unchanged.

Agents can also call wapitee_get_release_notes or read wapitee://release-notes to check capability changes programmatically.

Before you connect
Create Projects and assign live MCP roles in Wapitee, then choose interactive OAuth or a headless access token.
  1. 1. Create ProjectCreate it in Wapitee and add the people who will connect.
  2. 2. Assign MCP roleSet viewer, editor, or manager in Project settings.
  3. 3. Choose identityUse OAuth for an interactive client or an Account token for a headless agent.
  4. 4. Verify accessCall wapitee_list_projects; ACL changes apply immediately.
Open Wapitee View server.json
Branding from an Agent
Use the typed media tools when an Agent needs to apply a logo. Media is never sent as Base64 through MCP.
1. Create uploadCall wapitee_create_media_upload with an explicit Project, using project_logo, survey_logo, or option_image.
2. Upload and registerPUT binary PNG, SVG, JPEG, WebP, or AVIF bytes to the returned URL, then call wapitee_register_media_upload.
3. Apply the MediaRefUse the returned reference in a Project update or Survey ChangeSet.
Client setup guide
Choose your MCP client and follow the exact connection flow. Copy buttons never include credentials.
OAuth or access token

Interactive clients use OAuth. Headless clients can use a personal MCP access token from Account settings.

Identity-only connection

OAuth confirms your identity; Project roles are maintained in Wapitee and update immediately.

Revoke at any time

Project managers control viewer, editor, and manager assignments in Project settings.

  1. 1
    Add the Streamable HTTP server

    In the ChatGPT desktop app or Codex IDE extension, open Settings → MCP servers → Add server. Choose Streamable HTTP, name it Wapitee, and paste the endpoint below.

  2. 2
    Authenticate

    Save and restart the client if prompted. Select Authenticate, or run `codex mcp login wapitee` in the CLI, then complete OmniLogin in the browser.

  3. 3
    Confirm your identity

    The browser page only confirms the Wapitee identity connection. It does not ask you to select a Workspace or business scopes.

  4. 4
    Verify Project access

    Ask Wapitee to call `wapitee_list_projects`. An empty list means authentication succeeded but no Project is assigned yet.

~/.codex/config.toml
[mcp_servers.wapitee]
url = "https://gtm.wapitee.io/mcp"
auth = "oauth"
default_tools_approval_mode = "writes"
Official Codex MCP guide
Security model

OAuth or a headless MCP access token binds a user and identity connection with the single mcp:connect transport scope. It carries no Workspace or business permission.

Every call checks current authorization. Workspace owners/admins inherit manager access to their Projects; members use explicit Project ACLs. Viewer can read and analyze; editor can update drafts/documents/media; manager can update Projects and perform sensitive operations. Role and ACL changes apply without refresh or reconnect.

Writes use revisions and create idempotency where applicable. Sensitive operations require live manager access and are always audited; MCP no longer opens a separate browser confirmation step.

Analytics execute as bounded PostgreSQL aggregates. Agents must not page through raw records or use exports to compute totals, percentages, trends, or cross-tabs.

Wapitee Remote MCP