How to create polls and check results with Claude

What Claude can do with your onetapvote account

MCP (Model Context Protocol) is the standard way for AI assistants to use outside tools. onetapvote runs an MCP server, so once Claude is connected it can look at your account and act on it, the same way it reads files or searches the web.

Everything happens on the account that owns the API key you connect. Claude sees the same polls you see on your dashboard, and nothing else.

Step 1: create an API key

1. 1

   Open the API settings

   Sign in to onetapvote and go to Settings → API (/app/configure?tab=api). Any plan can create a key.

2. 2

   Create and name the key

   Click New key and give it a name you'll recognise later, such as "Claude on my laptop". One key per device or tool makes it easy to switch one off without breaking the others.

3. 3

   Copy it straight away

   The key starts with otv_live_ and is shown only once. Paste it into the setup below. If you lose it, revoke it and create a new one.

Step 2a: connect Claude Code

In Claude Code, the whole setup is one command. Run it in your terminal with your own key in place of otv_live_YOUR_KEY:

claude mcp add --transport http onetapvote \
  https://onetapvote.com/api/mcp \
  --header "Authorization: Bearer otv_live_YOUR_KEY"

Step 2b: connect Claude Desktop

Claude Desktop reaches online MCP servers through a small helper called mcp-remote, which runs with Node.js. If you don't have Node.js, install the LTS version from nodejs.org first.

1. 1

   Open the config file

   In Claude Desktop, open Settings → Developer → Edit Config. The file is claude_desktop_config.json (on a Mac in ~/Library/Application Support/Claude/, on Windows in %APPDATA%\Claude\).

2. 2

   Add onetapvote

   Paste the block below. If the file already has an mcpServers section, add only the onetapvote entry inside it. Replace otv_live_YOUR_KEY with your key.

3. 3

   Restart Claude Desktop

   Quit it fully and open it again. onetapvote now appears in the tools menu of a new chat.

{
  "mcpServers": {
    "onetapvote": {
      "command": "npx",
      "args": [
        "mcp-remote",
        "https://onetapvote.com/api/mcp",
        "--header",
        "Authorization:${AUTH}"
      ],
      "env": { "AUTH": "Bearer otv_live_YOUR_KEY" }
    }
  }
}

Step 3: prompts to try

Talk to Claude the way you'd talk to a colleague who has your dashboard open. It picks the right tool on its own.

Ideas: ask about your numbers

Claude reads the same numbers as your dashboard: polls by status, votes in total and in the last 30 days, and the votes for each option. The useful part is what it does with them: compare, rank, sum up and put into words you can paste somewhere.

Ideas: ask for advice and next steps

Because Claude can see the results, it can do more than report them. Ask it what the numbers mean and what to do next. It bases the answer on your polls, not on guesswork.

Ideas: make it a routine

The setup pays off when the same question comes back every week or month. A few routines that work well:

1. 1

   Monday team pulse

   "Create this week's pulse poll: 'How is your workload this week?' with Light, About right, Too much. Then compare it with last week's results." One poll a week, and Claude reads the trend across them for you.

2. 2

   After every meeting

   "Make a yes/no poll: 'Was this meeting useful?' and give me the link to paste in the chat." Ask Claude for the result the next morning.

3. 3

   Monthly customer check

   "Create a rating poll: 'How was your visit today?' and give me the QR code to print." At the end of the month: "How did the rating poll do, and what should I ask next month?"

4. 4

   Before a decision

   "I need to choose between two suppliers. Draft a poll for my staff, show it to me, and create it when I say go." Then let Claude write up the result for the decision log.

What Claude can and can't touch

• Claude asks for your permission before it uses a tool, unless you've told it to always allow that tool. Reading tools are marked read-only, so allowing them is safe.
• A new poll goes live the moment it's created. Ask Claude to show you the question and options first, then say "go".
• There is no delete tool. Claude can't remove polls or votes.
• Results are vote counts per option. Claude never sees who voted, their email or their IP address.
• Treat the key like a password. Don't paste it into a chat; put it in the config as shown above. If it leaks, revoke it in Settings → API and the old key stops working at once.