> For the complete documentation index, see [llms.txt](https://help.tahua.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://help.tahua.io/product-news/2026/september/mcp-form-answers-opt-in.md).

# Optional MCP access to form and assessment answers

## What it does

Until now the hosted admin MCP exposed summary data only: an AI assistant could see that an application exists, its state, scores and decision, but never what the applicant actually wrote. For many of the questions admins want to ask ("summarise what applicants said about community impact"), the form answers are the value. This feature adds an organisation-level opt-in that lets connected AI assistants read form answers, while keeping the safe-by-default posture.

## What's new

A new **Form answers** setting on **Settings → Organisation → API & MCP**, shown beneath "Hosted MCP access" once MCP is enabled. It defaults to **Disabled**; an administrator with the *Manage Integrations* permission can enable it. Toggling it is recorded as a security event (`mcp_form_answers_toggled`).

When enabled, four new read-only MCP tools become usable:

* `get_application_answers` — a funding application's form answers
* `get_applicant_answers` — an applicant's registration form answers
* `get_milestone_answers` — a milestone's deliverable/report form answers
* `get_assessment_answers` — an assessment's form answers plus per-criterion scores (question, score, weight) and the overall score

Each returns question/answer pairs for a single record by ID. When the setting is disabled the tools return a clear error telling the assistant the organisation has not enabled form answers.

## What stays excluded

Regardless of the setting:

* Uploaded files and images (the file's content and name are never returned)
* Bank account inputs inside forms
* Layout-only fields (headers, labels) and verifier-select fields
* Everything else already excluded from MCP (documents, accounting identifiers, applicant emails)

## Performance / design notes

* Answers are **pull-on-demand, per record** — list tools are unchanged and never embed answers. This keeps list payloads small (both for the database and for the assistant's context window); the assistant fetches answers only for records it is actually analysing.
* Each call is the record lookup through the admin's existing `accessible_by` read scope plus one inputs query with eager-loaded fields/translations (the API v2 pattern), under the existing 10s statement timeout and per-connection rate limiting.
* Multi-choice answers are mapped to their option labels; table/repeatable answers carry a row number; question labels are HTML-stripped.
* Data-policy scoping applies unchanged: an admin only gets answers for records they can already see.

## UI changes

The **API & MCP** settings page gains a "Form answers" section (Enabled/Disabled radio cards + Save changes) between "Hosted MCP access" and "Connection details".
