WebAsk MCP

The official remote MCP server for the WebAsk survey builder plus 25 skills: surveys from a brief, pre-launch checks, answers and reports

MCP serverOfficial

High risk

We rate an entry high when the tool writes to external systems, handles money, production databases or secrets, or runs arbitrary commands. The CLI installs it only with your consent.

Why this level

  • The key acts with the workspace owner's rights, and 24 tools are irreversible: deleting surveys, answers, webhooks and roles
  • Respondents' answers, including phone numbers and emails, are third-party personal data: the agent reads them and can export and forward them to CRMs, webhooks and messengers
  • The tools change live surveys, mailings and team settings, not a draft copy
All reasons and checks
Russian stack

webaskio/webask-mcp

Install

In your terminal, with SkillFoxx CLI

npx skillfoxx add mcp/webask-mcp

Detects the agents on your machine, checks the risk and pins the version.

Other ways to install

Assembled automatically, review before installing.

This entry is high risk, so there is no one-click install. Review the code and add the config by hand.

Run in a terminal

claude mcp add --transport http webask https://mcp.webask.io/mcp/v1 --header 'Authorization: Bearer <your WEBASK_API_KEY>'

Or add to the file .mcp.json, in the project

{
  "mcpServers": {
    "webask": {
      "type": "http",
      "url": "https://mcp.webask.io/mcp/v1",
      "headers": {
        "Authorization": "Bearer <your WEBASK_API_KEY>"
      }
    }
  }
}

If the file already exists, add the server inside the mcpServers key.

Keys and settings

WEBASK_API_KEYsecret, required
WebAsk API key

Replace the values in angle brackets with your own. Keys never go into install links and are not stored by us.

Add to the file ~/.cursor/mcp.json, for all projects

{
  "mcpServers": {
    "webask": {
      "url": "https://mcp.webask.io/mcp/v1",
      "headers": {
        "Authorization": "Bearer <your WEBASK_API_KEY>"
      }
    }
  }
}

If the file already exists, add the server inside the mcpServers key. For a single project, put the same block into .cursor/mcp.json.

Keys and settings

WEBASK_API_KEYsecret, required
WebAsk API key

Replace the values in angle brackets with your own. Keys never go into install links and are not stored by us.

Run in a terminal

code --add-mcp '{"name":"webask","type":"http","url":"https://mcp.webask.io/mcp/v1","headers":{"Authorization":"Bearer <your WEBASK_API_KEY>"}}'

Or add to the file .vscode/mcp.json, in the project

{
  "servers": {
    "webask": {
      "type": "http",
      "url": "https://mcp.webask.io/mcp/v1",
      "headers": {
        "Authorization": "Bearer <your WEBASK_API_KEY>"
      }
    }
  }
}

If the file already exists, add the server inside the servers key.

Keys and settings

WEBASK_API_KEYsecret, required
WebAsk API key

Replace the values in angle brackets with your own. Keys never go into install links and are not stored by us.

Add to the file ~/.codex/config.toml, for all projects

[mcp_servers.webask]
url = "https://mcp.webask.io/mcp/v1"
http_headers = { Authorization = "Bearer <your WEBASK_API_KEY>" }

If the file already exists, append the block to the end.

Keys and settings

WEBASK_API_KEYsecret, required
WebAsk API key

Replace the values in angle brackets with your own. Keys never go into install links and are not stored by us.

Add to the file ~/.gemini/settings.json, for all projects

{
  "mcpServers": {
    "webask": {
      "httpUrl": "https://mcp.webask.io/mcp/v1",
      "headers": {
        "Authorization": "Bearer <your WEBASK_API_KEY>"
      }
    }
  }
}

If the file already exists, add the server inside the mcpServers key.

Keys and settings

WEBASK_API_KEYsecret, required
WebAsk API key

Replace the values in angle brackets with your own. Keys never go into install links and are not stored by us.

Add to the file ~/.config/devin/mcp_config.json, for all projects

{
  "mcpServers": {
    "webask": {
      "serverUrl": "https://mcp.webask.io/mcp/v1",
      "headers": {
        "Authorization": "Bearer <your WEBASK_API_KEY>"
      }
    }
  }
}

If the file already exists, add the server inside the mcpServers key. Legacy Cascade keeps the MCP config in ~/.codeium/windsurf/mcp_config.json.

Keys and settings

WEBASK_API_KEYsecret, required
WebAsk API key

Replace the values in angle brackets with your own. Keys never go into install links and are not stored by us.

Formerly Windsurf.

Add to the file cline_mcp_settings.json, for all projects

{
  "mcpServers": {
    "webask": {
      "type": "streamableHttp",
      "url": "https://mcp.webask.io/mcp/v1",
      "headers": {
        "Authorization": "Bearer <your WEBASK_API_KEY>"
      }
    }
  }
}

If the file already exists, add the server inside the mcpServers key. Open the settings file in Cline: MCP Servers tab, Configure MCP Servers.

Keys and settings

WEBASK_API_KEYsecret, required
WebAsk API key

Replace the values in angle brackets with your own. Keys never go into install links and are not stored by us.

Add to the file .roo/mcp.json, in the project

{
  "mcpServers": {
    "webask": {
      "type": "streamable-http",
      "url": "https://mcp.webask.io/mcp/v1",
      "headers": {
        "Authorization": "Bearer <your WEBASK_API_KEY>"
      }
    }
  }
}

If the file already exists, add the server inside the mcpServers key.

Keys and settings

WEBASK_API_KEYsecret, required
WebAsk API key

Replace the values in angle brackets with your own. Keys never go into install links and are not stored by us.

A fork of Roo Code, same .roo folders.

Add to the file opencode.json, in the project

{
  "mcp": {
    "webask": {
      "type": "remote",
      "url": "https://mcp.webask.io/mcp/v1",
      "headers": {
        "Authorization": "Bearer <your WEBASK_API_KEY>"
      }
    }
  }
}

If the file already exists, add the server inside the mcp key.

Keys and settings

WEBASK_API_KEYsecret, required
WebAsk API key

Replace the values in angle brackets with your own. Keys never go into install links and are not stored by us.

Add to the file ~/.config/zed/settings.json, for all projects

{
  "context_servers": {
    "webask": {
      "url": "https://mcp.webask.io/mcp/v1",
      "headers": {
        "Authorization": "Bearer <your WEBASK_API_KEY>"
      }
    }
  }
}

If the file already exists, add the server inside the context_servers key.

Keys and settings

WEBASK_API_KEYsecret, required
WebAsk API key

Replace the values in angle brackets with your own. Keys never go into install links and are not stored by us.

Checked against the repository on Sep 30, 2026, commit e835d0f.

Text for your agent

Ask me to create an API key in my WebAsk account (Settings, API / MCP). In Claude Code install the plugin: /plugin marketplace add WebAskio/webask-mcp, then /plugin install webask-en@webask for English skills; the plugin prompts for the key. For the server only: claude mcp add --transport http webask https://mcp.webask.io/mcp/v1 --header "Authorization: Bearer <key>". Check the connection with /mcp and never delete surveys or answers without my explicit approval.

Other ways from the author
/plugin marketplace add WebAskio/webask-mcp
/plugin install webask@webask

Installs the server and 25 Russian skills; the key is requested during install and kept in the system password store. English skills: webask-en@webask.

Security check

How we review

High riskWe rate an entry high when the tool writes to external systems, handles money, production databases or secrets, or runs arbitrary commands. The CLI installs it only with your consent.

  • The key acts with the workspace owner's rights, and 24 tools are irreversible: deleting surveys, answers, webhooks and roles
  • Respondents' answers, including phone numbers and emails, are third-party personal data: the agent reads them and can export and forward them to CRMs, webhooks and messengers
  • The tools change live surveys, mailings and team settings, not a draft copy

This is third-party code. Review the repository files before installing.

What it does

The server runs on WebAsk's side at mcp.webask.io/mcp/v1 over Streamable HTTP, so there is nothing to host yourself; access is granted with an API key from your account. The agent gets 161 tools: build a survey from a description or a template, set up questions, branching and hidden fields, publish and share it by link or QR code, read answers, tag them, build a report and export it to Excel, CSV, SPSS, Word or PDF. Other tools configure notifications, webhooks and lead delivery to Bitrix24 and amoCRM, as well as workspace members, roles and branding. The same repository ships 25 skills in Russian and English: plain-text playbooks that tell the agent which calls to make for common jobs such as coding open-ended answers or removing test submissions.

Who it is for. For marketers, researchers, HR and product teams who run surveys and forms in WebAsk and want to build them and analyze answers right inside an agent.

Good fit when

  • You need to build a survey from a plain description and check it before sending it out
  • You need to analyze answers: group free text into themes, compare channels or A/B variants
  • Form leads stopped reaching your CRM, Telegram or webhook and you need to find out why
  • You need a report or a public results link for a client

Not a fit when

  • You have no WebAsk account: the server only works with surveys inside that service
  • You need to connect through a claude.ai or ChatGPT cloud connector: the server has no OAuth, only a key in a header
  • You are not ready to give an agent a key with the workspace owner's full rights

Example request

Show my surveys and how many answers came in this week, then group the open-ended answers in the customer survey into themes with quotes

MCP

Transport
http
Authentication
API key

Environment variables

WEBASK_API_KEY required, secret
The WebAsk API key from Settings, API / MCP. Codex and Gemini CLI read it from this variable; other clients put it into the Authorization: Bearer header.

Limitations

You need a WebAsk account and an API key from Settings, API / MCP; some tools depend on the workspace plan, and the server refuses when a feature is not included. The key acts with its owner's rights, and the README does not describe restricted keys. Authentication is only via the Authorization header with no OAuth, so cloud connectors that cannot send a persistent header will not work. Claude Desktop connects through the third-party mcp-remote proxy and needs Node.js. The limit is 180 requests per minute per user, and export links expire after an hour. The server code itself is closed; the repository holds only configs, docs, the plugin and the skills.

How to disable. In Claude Code remove the plugin with /plugin uninstall webask@webask or the server with claude mcp remove webask; in other clients delete the webask block from the config. Revoke the key in your WebAsk account under Settings, API / MCP.

FAQ

Do I need to run anything locally?

No, the server is remote: you only need the https://mcp.webask.io/mcp/v1 address and a key in the Authorization header. Claude Desktop is the exception, since it needs Node.js for the mcp-remote proxy.

How is the plugin different from claude mcp add?

The plugin installs the server and all 25 skills at once and keeps the key in the system password store. claude mcp add connects the server only.

Can data be deleted by accident?

Yes, 24 tools are irreversible, such as deleting surveys and answers. The server marks them with the destructiveHint annotation, and the skills tell the agent to ask a person before such actions.

Official

A self-hosted knowledge base with block-level references and a built-in MCP server for connecting AI agents to your notes

MCP serverMedium risk46.6KRepository stars
Editors’ pick

A CLI for every Google Workspace API with JSON output and agent skills: Drive, Gmail, Calendar, Sheets and more

CLIHigh risk31.2KRepository stars
Editors’ pick

Local search over Markdown notes, docs and meeting transcripts: keywords, semantic search and reranking, with an MCP server

CLIMedium risk30.1KRepository stars
Editors’ pick

A task manager for AI-driven development: breaks a PRD into dependent tasks and guides the agent through them via MCP or CLI

MCP serverMedium risk28.1KRepository stars

README in short

A Russian README with an English copy in the en folder: a three-step quick start, a Claude Code plugin, one-click install for VS Code and Cursor, a Gemini CLI extension and ready configs for Claude Desktop, Cursor, VS Code and Codex, also duplicated in the clients folder. A table lists the address, transport, auth, tool count and limits, followed by an overview of capabilities by area and tables of the 25 skills with links to ZIP archives. It also covers installing skills without the plugin via npx skills add and a security section: key permissions, marking irreversible tools and keeping keys out of the repository. The full tool list lives in docs/tools.md and sample requests in docs/prompts.md.

README badge

Are you the author? Show in your README that the project is reviewed in the SkillFoxx catalog. The badge updates itself.

SkillFoxx badge for this project
[![Проверено SkillFoxx](https://skillfoxx.ru/badges/mcp/webask-mcp.svg)](https://skillfoxx.ru/mcp/webask-mcp?utm_source=github&utm_medium=badge&utm_campaign=readme)
Foxx AIWebAsk MCP

I am Foxx AI and I have already vetted this tool. Ask about install, setup or anything else, and I will keep it simple.