Aleph
Query live FP&A data, build reports and update dashboards from your AI assistant.
Design, build and analyse Remesh research conversations.
Opens Agent Studio, where connecting is one click. The connector URL below works in any MCP client.
Paste it into any MCP client. Setup docs
The Remesh MCP server connects a Remesh workspace — a research platform that runs structured conversations with hundreds of real participants at once — to Claude, ChatGPT and any MCP client. Anthropic's directory lists 52 tools that build discussion guides, configure audiences and analyse results. Sign-in is OAuth 2.0 with read and write scopes.
Verified connector
Listed by Anthropic as a partner connector in its Connectors Directory.
Connection checked by Agentman on .
Anthropic states this reflects the level of review a connector received, not a security audit.
Tool names from Anthropic's directory listing. This server requires sign-in, so we could not read tool descriptions or parameter schemas.
read and write is a real boundary, and it is only one. It does not fall between the routine write and the irreversible one: granting write grants update_section, delete_message and apply_recruit_audience together. There is no way to let an agent draft a guide without also letting it delete one.apply_recruit_audience commits against On Demand Recruit credits. Remesh publishes no per-participant rate, so a recruitment configuration's cost is unpredictable rather than small.Yes, and that is the most important fact on this page. Tools including get_sentiment_examples, get_top_responses_by_agreement and get_responses_by_segment_submission return the verbatim text participants wrote. Remesh states its Conversation Data export contains every response to every question asked. Participant answers, not just aggregate statistics, enter your agent's context.
No, and Remesh says so directly. Its recruiting documentation states that Remy sets recruitment up and that you publish and launch from the Build page yourself. No tool among the 52 publishes, launches, ends or moderates. create_conversation_messages writes discussion-guide items into a draft, which is authoring, not sending.
Twenty-one write and two delete. The deletes are delete_message and delete_section. The writes are the create, update, duplicate, set, upload, apply, schedule, run and continue verbs — including apply_recruit_audience and upload_participant_data. A risky-verb scan that looks only for delete would miss nineteen of them.
One tool can. apply_recruit_audience configures Remesh Recruit, and Remesh lists On Demand Recruit credits as a prerequisite for recruiting through Remy. No tool among the 52 reads a credit balance, a quota or a bill, so an agent can arrange a spend with no tool that could check the remaining balance first.
Two, read and write. Remesh's RFC 9728 resource descriptor and its authorization server both advertised scopes_supported of read and write on 2026-08-23. That is a genuine boundary between reading a study and changing one, but it is a single boundary — write covers deleting a section and configuring paid recruitment alike.
No. Remesh states the MCP server exposes only data and actions you already have access to, follows your existing Remesh permissions, and that connecting a client does not grant new permissions. A workspace admin must also enable MCP Access in Manage Workspace settings before any connection works.
A Remesh subscription and an admin who has enabled MCP access. Remesh states an admin must open Manage Workspace, then Settings, find the MCP Access tab and enable the workspace toggle. If Generative AI is disabled for the workspace, MCP access is disabled by default too.
Yes, applied by workspace and by user. Remesh states requests are limited at both levels to protect platform performance, and that large batches of requests may reach those limits. Its guidance when you see a rate-limit message or slow responses is to wait before retrying and send fewer requests at one time.
robots.txt on this host disallows only preview and sample paths. · retrieved 2026-08-23initialize returned HTTP 401 with a WWW-Authenticate Bearer challenge naming https://live.remesh.chat/.well-known/oauth-protected-resource/mcp; that RFC 9728 descriptor and https://live.remesh.chat/.well-known/oauth-authorization-server both declare scopes_supported of read and write (2026-08-23) · retrieved 2026-08-23Connect Remesh once and your agents call these tools on their own: on a schedule, in a workflow, with nobody at the keyboard.