> For the complete documentation index, see [llms.txt](https://docs.feathery.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.feathery.io/develop/mcp-server/supported-tools.md).

# Supported Tools

Every tool Feathery MCP gives your AI assistant, what each one does, and which ones change data.

The assistant picks a tool based on your prompt. Which tools it can use depends on how you connected:

| Connection                                | Tools available                                                                                                    |
| ----------------------------------------- | ------------------------------------------------------------------------------------------------------------------ |
| Signed in with **Work in your workspace** | Every tool except the meeting tools. Viewers can't use tools that change data, and team tools need the Admin role. |
| Signed in with **Read your meetings**     | The meeting tools. Your organization needs the AI Notetaker.                                                       |
| API key                                   | Every tool except the meeting tools.                                                                               |

### Forms

| Tool          | What it does                                                                             | Changes data |
| ------------- | ---------------------------------------------------------------------------------------- | ------------ |
| `list_forms`  | List forms in your account.                                                              | No           |
| `get_form`    | Review a form's steps, fields, rules, integrations, and translations.                    | No           |
| `create_form` | Create a new form from a template.                                                       | Yes          |
| `update_form` | Rename, enable, disable, translate, or update supported integration settings for a form. | Yes          |
| `delete_form` | Delete a form after confirmation.                                                        | Yes          |
| `copy_form`   | Copy an existing form.                                                                   | Yes          |

<details>

<summary>Example prompts</summary>

* "List active onboarding forms."
* "Summarize the setup of this form."
* "Copy this form and name the copy `Renewal Flow - Test`."
* "Disable this form."

</details>

### Submissions

| Tool                    | What it does                                                              | Changes data |
| ----------------------- | ------------------------------------------------------------------------- | ------------ |
| `list_submissions`      | Find submissions by form, date range, completion status, or field values. | No           |
| `create_submission`     | Create or update a submission.                                            | Yes          |
| `export_submission_pdf` | Export one submission or a group of submissions as PDFs.                  | Yes          |

<details>

<summary>Example prompts</summary>

* "Show completed submissions for this form since Monday."
* "Find submissions where `Email` is `person@example.com`."
* "Create a test submission and mark it complete."
* "Export a PDF for this user's submission."

</details>

### Users

| Tool                      | What it does                                                     | Changes data |
| ------------------------- | ---------------------------------------------------------------- | ------------ |
| `list_users`              | List users and optionally filter by created date or field value. | No           |
| `get_submitted_user_data` | Review a user's submitted field and hidden field data.           | No           |
| `get_user_session`        | Check a user's progress across forms.                            | No           |
| `create_user`             | Create a new user or find an existing one.                       | Yes          |
| `delete_user`             | Delete a user and their submission data after confirmation.      | Yes          |

<details>

<summary>Example prompts</summary>

* "Find users created yesterday with status `Approved`."
* "Show this user's submitted data."
* "What step is this user currently on?"

</details>

### Fields and Hidden Fields

| Tool                   | What it does                                           | Changes data |
| ---------------------- | ------------------------------------------------------ | ------------ |
| `list_fields`          | List field data, including values for a specific user. | No           |
| `list_hidden_fields`   | List hidden fields in your account.                    | No           |
| `create_hidden_fields` | Create hidden fields.                                  | Yes          |
| `edit_hidden_fields`   | Edit hidden fields.                                    | Yes          |
| `delete_hidden_fields` | Delete hidden fields after confirmation.               | Yes          |

<details>

<summary>Example prompts</summary>

* "List hidden fields and tell me whether `crm_status` exists."
* "Create a hidden field called `internal_review_state`."
* "Delete these old hidden fields."

</details>

### Team Accounts

When you sign in with your Feathery account, these tools need the Admin role.

| Tool            | What it does                             | Changes data |
| --------------- | ---------------------------------------- | ------------ |
| `get_account`   | List team members and roles.             | No           |
| `edit_account`  | Update a team member's role.             | Yes          |
| `invite_member` | Invite one or more team members.         | Yes          |
| `remove_member` | Remove a team member after confirmation. | Yes          |

<details>

<summary>Example prompts</summary>

* "List team members and group them by role."
* "Invite `new.member@example.com` as an editor."
* "Remove this team member."

</details>

### AI Document Extractions

These tools need Document Intelligence.

| Tool                   | What it does                                                               | Changes data |
| ---------------------- | -------------------------------------------------------------------------- | ------------ |
| `list_extractions`     | List AI document extraction configurations.                                | No           |
| `get_extraction`       | Review an extraction's fields, queries, variants, rules, and integrations. | No           |
| `run_extraction`       | Run an extraction on files.                                                | Yes          |
| `list_extraction_runs` | Review previous extraction runs.                                           | No           |

<details>

<summary>Example prompts</summary>

* "List my document extractions and summarize what each one extracts."
* "Show which fields this extraction saves to."
* "Run this extraction on the attached PDF."
* "Show extraction runs from the last 24 hours."

</details>

### Document Templates

| Tool                      | What it does                                                      | Changes data |
| ------------------------- | ----------------------------------------------------------------- | ------------ |
| `list_document_templates` | List uploaded document templates and filter them by name or tags. | No           |

<details>

<summary>Example prompts</summary>

* "Find document templates with `claims` in the name."
* "List templates tagged `insurance`."

</details>

### Logs

| Tool                         | What it does                                   | Changes data |
| ---------------------------- | ---------------------------------------------- | ------------ |
| `list_api_connector_errors`  | Review recent API connector errors for a form. | No           |
| `list_form_email_logs`       | Review recent emails sent from a form.         | No           |
| `list_extraction_email_logs` | Review emails that triggered an AI extraction. | No           |
| `list_email_issues`          | Review email bounces and complaints.           | No           |
| `list_quik_requests`         | Review recent Quik integration requests.       | No           |

<details>

<summary>Example prompts</summary>

* "Show API connector errors for this form from the last week."
* "List email bounces since yesterday."
* "Summarize failed Quik requests for this form."

</details>

### Meetings

These tools need you to sign in with your Feathery account and allow **Read your meetings**. Your organization needs the AI Notetaker. The assistant only sees meetings you can see in Feathery.

| Tool                     | What it does                                                                                           | Changes data |
| ------------------------ | ------------------------------------------------------------------------------------------------------ | ------------ |
| `list_meetings`          | List meetings you can access, newest first. Filter by title, status, meeting type, or date.            | No           |
| `get_meeting`            | Review a meeting's participants, AI summary, action items, and a link to it in Feathery.               | No           |
| `get_meeting_transcript` | Read a meeting's transcript with timestamps and speaker names. Long transcripts are returned in pages. | No           |

<details>

<summary>Example prompts</summary>

* "List my meetings from last week."
* "Summarize the action items from my call with Acme."
* "Find where pricing came up in this meeting's transcript."

</details>


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.feathery.io/develop/mcp-server/supported-tools.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.