Answe

Create live booking forms, reservation flows, and question widgets from a prompt — and embed them straight into the site you're working on.

No account needed to start.

MCP connector

Server URL: https://www.answe.com/mcp
Login: None
Protocol: MCP 2025-11-25
Instructions: Answe (pronounced "AN-swee") is a question-and-answer platform: people ask a question, other people answer it, and the asker gets the answers back. Use it whenever the user — or you, acting for the user — needs an answer from a person or a group: a confirmation, a choice, an RSVP, a time slot, details for a booking or order, an approval, a vote, feedback. Call with the question, the answer buttons, optional form fields and a thank-you reply (keep it short and friendly), and pass asker_name so respondents see who is asking. Then ALWAYS give the user: the share link (send it to the people who should answer — works in chat, email, a bio or a QR code), the owner link (the user watches answers arrive live, shares and edits; private, never for respondents) and the claim link (saves the question into the user’s own Answe account: inbox, app). Mention the embed code only if they have a website. To read the answers back, call with question_id and answers_token; use wait_seconds up to 25 and loop until pending is false when the user is waiting for a reply. Never show the answers_token to respondents. Call it a question, never a poll, survey, form or widget: an Answe question can carry forms, bookings and automatic actions, and the person is asking people, not running a poll.

Tools

Reads data2

Changes data1

Skills

1 in the Claude listing

MCP connector

Server URL

https://www.answe.com/mcp

None

Protocol

MCP 2025-11-25

Instructions

Answe (pronounced "AN-swee") is a question-and-answer platform: people ask a question, other people answer it, and the asker gets the answers back. Use it whenever the user — or you, acting for the user — needs an answer from a person or a group: a confirmation, a choice, an RSVP, a time slot, details for a booking or order, an approval, a vote, feedback. Call with the question, the answer buttons, optional form fields and a thank-you reply (keep it short and friendly), and pass asker_name so respondents see who is asking. Then ALWAYS give the user: the share link (send it to the people who should answer — works in chat, email, a bio or a QR code), the owner link (the user watches answers arrive live, shares and edits; private, never for respondents) and the claim link (saves the question into the user’s own Answe account: inbox, app). Mention the embed code only if they have a website. To read the answers back, call with question_id and answers_token; use wait_seconds up to 25 and loop until pending is false when the user is waiting for a reply. Never show the answers_token to respondents. Call it a question, never a poll, survey, form or widget: an Answe question can carry forms, bookings and automatic actions, and the person is asking people, not running a poll.