# Affinda — how to use (mcp.ai)

Connect your Affinda account and use 119 tools for artificial intelligence straight from your AI agent. Connect with your own API key. Affinda provides an AI-powered document processing platform that automates data extraction from various document types.

## Option A — via MCP (recommended)
Remote MCP endpoint (HTTP, streamable): `https://api.mcp.ai/p_affinda?ms=1787296020000`
Add it as a custom/remote MCP connector in your client (Claude, Cursor, VS Code…), then authenticate when prompted. Once connected, ask the agent to use the server's tools (e.g. `affinda_add_tag_to_documents`).

## Option B — via direct REST API
Base URL: `https://api.mcp.ai/api/affinda`
Auth: `Authorization: Bearer sk_live_…` — create a workspace API key at https://mcp.ai/settings/api-keys
Discover endpoints: `GET https://api.mcp.ai/api/affinda/_endpoints`

### Endpoints
- `POST https://api.mcp.ai/api/affinda/add/tag/to/documents` — Tool to add a tag to multiple documents in a single operation. Use when you need to organize or categorize multiple documents by assigning them a shared tag. Tags enable efficient filtering and groupi
  - body: { tag: integer, identifiers: string[] }
- `POST https://api.mcp.ai/api/affinda/batch/update/annotations` — Batch update multiple document annotations in a single API call. Use this action to efficiently update parsed values or other fields across many annotations at once, rather than making individual upda
  - body: { annotations: object[] }
- `POST https://api.mcp.ai/api/affinda/create/api/user` — Tool to create a new API user within an organization. Use when you need to generate a new API user with authentication credentials for programmatic access to Affinda services.
  - body: { name?: string, email?: string, avatar?: string, username?: string, organization: string }
- `POST https://api.mcp.ai/api/affinda/create/batch/annotations` — Batch create multiple document annotations in a single API call. Use this action to efficiently create multiple annotations at once for documents that have been processed by Affinda. This is useful fo
  - body: { annotations: object[] }
- `POST https://api.mcp.ai/api/affinda/create/collection` — Tool to create a new collection. Use after you have a valid workspace ID and want to group documents by a specific extractor within that workspace.
  - body: { name: string, extractor: string, workspace: string }
- `POST https://api.mcp.ai/api/affinda/create/data/field/for/collection` — Tool to create a data field for a collection along with a new data point. Use when you need to add a custom field to a collection for document processing and validation.
  - body: { field: object, dataPoint: object, identifier: string, categoryLabel?: string }
- `POST https://api.mcp.ai/api/affinda/create/data/point` — Tool to create a custom data point for document extraction. Use when you need to define a new field that should be extracted from documents in a specific extractor. Note: This endpoint is deprecated b
  - body: { name: string, slug: string, noRect?: boolean, parent?: string, multiple?: boolean, extractor: string, description?: string, manualEntry?: boolean, organization: string, mappingDataSource?: string, annotationContentType: string }
- `POST https://api.mcp.ai/api/affinda/create/data/point/choice` — Tool to create a custom data point choice. Use when you need to add a new choice option for a specific data point in a collection or organization. Note: This endpoint is deprecated but still functiona
  - body: { label: string, value: string, synonyms?: string[], dataPoint: string, collection?: string, description?: string, organization?: string }
- `POST https://api.mcp.ai/api/affinda/create/data/source` — Tool to create a custom mapping data source. Use when you need to set up a new data source for mapping AI-extracted values to your database records.
  - body: { name?: string, schema?: object, values?: object[], workspace?: string, identifier: string, keyProperty?: string, organization?: string, displayProperty?: string }
- `POST https://api.mcp.ai/api/affinda/create/data/source/value` — Tool to add a new value to a mapping data source. Use when you need to add entries to a data source for mapping or validation purposes. The created value can then be referenced in document extraction 
  - body: { label?: string, value: string, identifier: string, description?: string }
- `POST https://api.mcp.ai/api/affinda/create/document` — Upload a document to Affinda for parsing and data extraction. Use this action when you need to: - Parse resumes/CVs to extract candidate information - Process invoices to extract line items, amounts, 
  - body: { url?: string, file?: object, wait?: boolean, compact?: boolean, fileName?: string, language?: string, workspace?: string, collection?: string, expiryTime?: string, identifier?: string, rejectDuplicates?: boolean }
- `POST https://api.mcp.ai/api/affinda/create/document/type` — Tool to create a new document type in the specified organization. Use when you need to define a new category of documents for processing. Document types allow you to organize and categorize documents 
  - body: { name: string, description?: string, organization: string }
- `POST https://api.mcp.ai/api/affinda/create/extractor` — Tool to create a new extractor. Use when you need to define a custom document parser with specific fields and extraction rules, typically derived from a base extractor.
  - body: { name: string, category?: string, namePlural?: string, fieldGroups?: object[], validatable?: boolean, organization: string, baseExtractor?: string }
- `POST https://api.mcp.ai/api/affinda/create/from/data/documents` — Create a document from structured resume or job description data for Search & Match. Use this when you have structured data to create a document programmatically without file uploads. Returns an ident
  - body: { data: object, wait?: boolean, language?: string, file_name?: string, workspace?: string, collection?: string, identifier?: string, snake_case?: boolean, expiry_time?: string, document_type?: string }
- `POST https://api.mcp.ai/api/affinda/create/index` — Tool to create a new index for search and match functionality. Use when you need to set up a new index for organizing and searching documents like resumes or job descriptions.
  - body: { name: string, docType?: string }
- `POST https://api.mcp.ai/api/affinda/create/invitation` — Tool to create a new organization invitation. Use when you need to invite a user to join an organization with a specific role.
  - body: { role: string, email: string, organization: string }
- `POST https://api.mcp.ai/api/affinda/create/job/description/search` — Search through parsed job descriptions using custom criteria or resume matching. Use this action when you need to find job postings that match specific requirements such as skills, experience, locatio
  - body: { limit?: integer, offset?: integer, resume?: string, skills?: object[], degrees?: string[], indices: string[], socCodes?: integer[], jobTitles?: string[], languages?: object[], locations?: object[], customData?: object[], degreeTypes?: string[], skillsWeight?: number, socCodesWeight?: number, degreesRequired?: boolean, educationWeight?: number, jobTitlesWeight?: number, languagesWeight?: number, locationsWeight?: number, managementLevel?: string, searchExpression?: string, socCodesRequired?: boolean, jobTitlesRequired?: boolean, locationsRequired?: boolean, degreeTypesRequired?: boolean, totalYearsExperience?: number, managementLevelWeight?: number, yearsExperienceWeight?: number, searchExpressionWeight?: number, managementLevelRequired?: boolean, yearsExperienceRequired?: boolean, searchExpressionRequired?: boolean }
- `POST https://api.mcp.ai/api/affinda/create/job/description/search/embed/url` — Tool to create and return a signed URL for the embeddable job description search tool. Use this when you need to generate a URL that can be embedded on a web page to provide job description search fun
  - body: { configOverride?: object }
- `POST https://api.mcp.ai/api/affinda/create/mapping` — Tool to create a custom mapping for a data source. Use when you need to configure specific lookup settings for a MappingDataSource. Note: This endpoint is deprecated.
  - body: { orderBy?: string, dataSource: string, scoreCutoff?: number, organization?: string }
- `POST https://api.mcp.ai/api/affinda/create/organization` — Tool to create a new organization. Use when you have a unique organization name and want to group resources under it.
  - body: { name: string }
- `POST https://api.mcp.ai/api/affinda/create/resthook/subscription` — Tool to create a new RESTHook subscription. Use after confirming your webhook endpoint is ready to receive document event notifications.
  - body: { event: string, targetUrl: string, organization: string }
- `POST https://api.mcp.ai/api/affinda/create/resume/search` — Tool to search through parsed resumes using three methods: match to a job description, match to a resume, or custom criteria. Use when you need to find candidates matching specific requirements.
  - body: { limit?: integer, offset?: integer, resume?: string, skills?: object[], degrees?: string[], indices: string[], socCodes?: integer[], jobTitles?: string[], languages?: object[], locations?: object[], customData?: object[], institutions?: string[], skillsWeight?: number, jobDescription?: string, socCodesWeight?: number, degreesRequired?: boolean, educationWeight?: number, jobTitlesWeight?: number, languagesWeight?: number, locationsWeight?: number, managementLevel?: string, isCurrentStudent?: boolean, isRecentGraduate?: boolean, searchExpression?: string, socCodesRequired?: boolean, jobTitlesRequired?: boolean, locationsRequired?: boolean, highestDegreeTypes?: string[], yearsExperienceMax?: integer, yearsExperienceMin?: integer, institutionsRequired?: boolean, jobTitlesCurrentOnly?: boolean, managementLevelWeight?: number, yearsExperienceWeight?: number, searchExpressionWeight?: number, managementLevelRequired?: boolean, yearsExperienceRequired?: boolean, isCurrentStudentRequired?: boolean, isRecentGraduateRequired?: boolean, searchExpressionRequired?: boolean, highestDegreeTypesRequired?: boolean }
- `POST https://api.mcp.ai/api/affinda/create/resume/search/embed/url` — Tool to create and return a signed URL for the embeddable resume search tool. Use this when you need to generate a URL that can be embedded on a web page to provide resume search functionality. Option
  - body: { configOverride?: object }
- `POST https://api.mcp.ai/api/affinda/create/tag` — Creates a new tag in the specified workspace. Tags can be used to categorize and label documents for organization and filtering. Each tag name must be unique within its workspace. Returns the created 
  - body: { name: string, workspace: string }
- `POST https://api.mcp.ai/api/affinda/create/validation/result` — Create a validation result for document annotations in Affinda. Use this tool to record validation outcomes after parsing a document. Validation results track whether specific annotations (extracted d
  - body: { passed?: boolean, message: string, document: string, ruleSlug: string, annotations: integer[] }
- `POST https://api.mcp.ai/api/affinda/create/validation/results/batch` — Batch create multiple validation results for document annotations in a single API call. Use this action to efficiently record validation outcomes for multiple documents or rules at once, rather than m
  - body: { validation_results: object[] }
- `POST https://api.mcp.ai/api/affinda/create/workspace` — Tool to create a new workspace. Use when you need to programmatically create a workspace container within an organization.
  - body: { name: string, visibility?: string, organization: string, rejectInvalidDocuments?: boolean }
- `POST https://api.mcp.ai/api/affinda/create/workspace/membership` — Tool to add a user to a workspace by creating a membership. Use when you need to grant a user access to a specific workspace.
  - body: { user: integer, workspace: string }
- `POST https://api.mcp.ai/api/affinda/delete/annotations/batch` — Batch delete multiple document annotations in a single API call. Use this action to efficiently remove multiple annotations at once rather than making individual delete requests for each annotation. P
  - body: { annotation_ids: integer[] }
- `POST https://api.mcp.ai/api/affinda/delete/collection` — Permanently delete a collection from Affinda by its identifier. This is a destructive operation that cannot be undone. Use Get Collections first to verify the collection ID before deletion. Note: Docu
  - body: { collection_id: string }
- `POST https://api.mcp.ai/api/affinda/delete/data/point` — Tool to permanently delete a data point by its identifier. Use when you need to remove a data point from the database after confirming the identifier. Note: This endpoint is deprecated but still funct
  - body: { identifier: string }
- `POST https://api.mcp.ai/api/affinda/delete/data/source` — Permanently delete a mapping data source from the database by its identifier. This is a destructive operation that cannot be undone. Use when you need to remove a data source that is no longer needed 
  - body: { identifier: string }
- `POST https://api.mcp.ai/api/affinda/delete/data/source/value` — Tool to delete a specific value from a mapping data source. Use when you need to remove an incorrect or outdated value from a data source mapping.
  - body: { value: string, identifier: string }
- `POST https://api.mcp.ai/api/affinda/delete/document` — Tool to delete a specific document by its ID. Use when you need to remove a document that is incorrect or no longer needed, after confirming the document ID.
  - body: { identifier: string }
- `POST https://api.mcp.ai/api/affinda/delete/document/type` — Tool to permanently delete a document type by its identifier. Use when you need to remove a document type that is no longer needed. This is a destructive operation that cannot be undone.
  - body: { identifier: string }
- `POST https://api.mcp.ai/api/affinda/delete/extractor` — Permanently delete an extractor from Affinda by its identifier. This is a destructive operation that cannot be undone. Use Get Extractors first to verify the extractor ID before deletion. Note: This a
  - body: { identifier: string }
- `POST https://api.mcp.ai/api/affinda/delete/index` — Tool to permanently delete an index from Affinda by its name. Use when you need to remove an index that is no longer needed. This is a destructive operation that cannot be undone.
  - body: { name: string }
- `POST https://api.mcp.ai/api/affinda/delete/invitation` — Tool to delete an invitation by its identifier. Use when you need to remove or revoke an invitation after confirming the invitation identifier.
  - body: { identifier: string }
- `POST https://api.mcp.ai/api/affinda/delete/mapping` — Tool to delete a specific mapping by its identifier. Use when you need to remove an unused or incorrect mapping from the database. Note: This endpoint is deprecated.
  - body: { identifier: string }
- `POST https://api.mcp.ai/api/affinda/delete/organization` — Permanently deletes an organization from Affinda. This action is destructive and cannot be undone. All workspaces, collections, and documents associated with the organization will also be deleted. Use
  - body: { identifier: string }
- `POST https://api.mcp.ai/api/affinda/delete/resthook/subscription` — Tool to delete a specific resthook subscription by ID. Use after confirming the subscription identifier when the webhook is no longer needed.
  - body: { identifier: integer }
- `POST https://api.mcp.ai/api/affinda/delete/tag` — Permanently delete a tag from Affinda by its ID. This is a destructive operation that cannot be undone. Use Get Tags first to verify the tag ID before deletion.
  - body: { id: integer }
- `POST https://api.mcp.ai/api/affinda/delete/validation/results` — Delete multiple validation results in a single API call. Use this action to efficiently remove multiple validation results at once rather than making individual delete requests for each validation res
  - body: { ids: integer[] }
- `POST https://api.mcp.ai/api/affinda/delete/workspace` — Tool to delete a specific workspace by its ID. Use when you need to remove an unused workspace after confirming the workspace ID.
  - body: { workspace_id: string }
- `POST https://api.mcp.ai/api/affinda/delete/workspace/membership` — Tool to remove a user from a workspace by membership ID. Use after confirming the workspace membership ID to revoke access.
  - body: { identifier: string }
- `POST https://api.mcp.ai/api/affinda/get/all/api/users` — Tool to retrieve a list of all API users. Use when you need to list API users, optionally filtered by organization.
  - body: { limit?: integer, offset?: integer, organization?: string }
- `POST https://api.mcp.ai/api/affinda/get/all/document/splitters` — Tool to get a list of all document splitters. Use when you need to retrieve document splitters, optionally filtered by organization.
  - body: { limit?: integer, offset?: integer, organization?: string, includePublic?: boolean }
- `POST https://api.mcp.ai/api/affinda/get/all/invitations` — Tool to retrieve all invitations you created or sent to you. Use when you need to list organization invitations with optional filtering by status, role, or organization.
  - body: { role?: string, limit?: integer, offset?: integer, status?: string, organization?: string }
- `POST https://api.mcp.ai/api/affinda/get/all/organization/memberships` — Retrieve all organization memberships across the account. Returns paginated results showing which users belong to which organizations. Use to audit organization access or find specific user membership
  - body: { role?: string, limit?: integer, offset?: integer, organization?: string }
- `POST https://api.mcp.ai/api/affinda/get/all/tags` — Tool to list all tags. Use after confirming authentication to fetch tags across workspaces.
  - body: { name?: string, limit?: integer, offset?: integer, workspace?: string }
- `POST https://api.mcp.ai/api/affinda/get/all/validation/results` — Tool to list validation results for documents. Use after processing documents to inspect validation outcomes.
  - body: { limit?: integer, offset?: integer, document: string }
- `POST https://api.mcp.ai/api/affinda/get/all/workspace/memberships` — Retrieve all workspace memberships across the account. Returns paginated results showing which users belong to which workspaces. Use to audit workspace access or find specific user memberships.
  - body: { user?: string, limit?: integer, offset?: integer, workspace?: string }
- `POST https://api.mcp.ai/api/affinda/get/annotations` — Retrieves all annotations for a specific document. Annotations are extracted data fields (text, dates, numbers, tables, etc.) from parsed documents. Use this after a document has been processed to acc
  - body: { document: string }
- `POST https://api.mcp.ai/api/affinda/get/collection` — Tool to retrieve details of a specific collection by its ID. Use when you need full metadata about a collection after confirming its identifier.
  - body: { collection_id: string }
- `POST https://api.mcp.ai/api/affinda/get/collection/fields` — Tool to retrieve data field configuration for a collection associated with a data point. Use when you need to understand the structure and validation rules of a specific field in a collection. Note: T
  - body: { identifier: string, datapoint_identifier: string }
- `POST https://api.mcp.ai/api/affinda/get/collection/usage` — Retrieves monthly credits consumption statistics for a specific collection. Returns a list of usage records showing how many credits were consumed each month. Use this to track collection activity, mo
  - body: { end?: string, start?: string, identifier: string }
- `POST https://api.mcp.ai/api/affinda/get/collections` — Tool to retrieve a list of all collections. Use when you need to list collections in your Affinda workspace after authentication.
  - body: { limit?: integer, offset?: integer, workspace: string }
- `POST https://api.mcp.ai/api/affinda/get/data/point` — Tool to retrieve details of a specific data point by its identifier. Use when you need to inspect a data point's configuration, type, or structure. Data points represent individual fields that can be 
  - body: { identifier: string }
- `POST https://api.mcp.ai/api/affinda/get/data/point/choice` — Tool to return a specific data point choice by its ID. Use when you need details about a particular data point choice option. Note: This endpoint is deprecated but still functional.
  - body: { id: integer }
- `POST https://api.mcp.ai/api/affinda/get/data/source` — Tool to retrieve details of a specific mapping data source by its identifier. Use when you need to fetch mapping data source metadata and schema configuration.
  - body: { identifier: string }
- `POST https://api.mcp.ai/api/affinda/get/data/source/value` — Tool to retrieve a specific value from a mapping data source. Use when you need to get details about a particular value in a data source.
  - body: { value: string, identifier: string }
- `POST https://api.mcp.ai/api/affinda/get/data/source/values` — Tool to retrieve all values from a mapping data source. Use when you need to list or search values in a specific data source after authentication.
  - body: { limit?: integer, offset?: integer, search?: string, document?: string, annotation?: integer, identifier: string }
- `POST https://api.mcp.ai/api/affinda/get/document` — Retrieve full details and parsed data for a specific document by its identifier. Use this tool to get comprehensive information about a document including: - Processing status (ready/failed) - Documen
  - body: { identifier: string }
- `POST https://api.mcp.ai/api/affinda/get/document/redacted` — Tool to retrieve the redacted version of a document as a PDF file. Use when you need to get a document with sensitive information removed. The original document is not modified by this operation.
  - body: { identifier: string }
- `POST https://api.mcp.ai/api/affinda/get/document/splitter` — Tool to retrieve details of a specific document splitter by its identifier. Use when you need to fetch metadata about a document splitter configuration.
  - body: { identifier: string }
- `POST https://api.mcp.ai/api/affinda/get/document/type` — Tool to retrieve details of a specific document type by its ID. Use when you need to confirm the configuration or metadata of a document type before processing documents.
  - body: { identifier: string }
- `POST https://api.mcp.ai/api/affinda/get/document/type/json/schema` — Tool to generate a JSON schema from a document type by its identifier. Use when you need the structured schema definition for a document type to understand its field structure and validation rules.
  - body: { title?: string, identifier: string }
- `POST https://api.mcp.ai/api/affinda/get/document/type/pydantic/models` — Tool to generate Pydantic model code from a document type's schema. Use when you need type-safe Python models for parsing documents of a specific type.
  - body: { identifier: string, model_name?: string }
- `POST https://api.mcp.ai/api/affinda/get/document/types` — Retrieve all document types accessible to the authenticated user. Returns a list containing each document type's identifier, name, description, ingest email, and organization. Use this to discover ava
- `POST https://api.mcp.ai/api/affinda/get/documents` — Tool to retrieve a list of all documents. Use when you need to list documents in your Affinda workspace after authentication.
  - body: { count?: boolean, limit?: integer, ready?: boolean, state?: string, failed?: boolean, offset?: integer, search?: string, compact?: boolean, ordering?: string, workspace?: string, collection?: string, include_data?: boolean }
- `POST https://api.mcp.ai/api/affinda/get/extractor` — Tool to retrieve detailed information about a specific extractor by its identifier. Use when you need complete metadata about an extractor's configuration, fields, and capabilities.
  - body: { identifier: string }
- `POST https://api.mcp.ai/api/affinda/get/extractors` — Retrieve all extractors available for an organization. Extractors are document parsing configurations that define what data to extract from documents. This includes both Affinda's built-in extractors 
  - body: { organization: string }
- `POST https://api.mcp.ai/api/affinda/get/index/documents` — Tool to retrieve all indexed documents for a specific index. Use when you need to list documents in a search index after creating or accessing an index.
  - body: { name: string, limit?: integer, offset?: integer }
- `POST https://api.mcp.ai/api/affinda/get/invitation` — Tool to retrieve details of a specific organization invitation by its identifier. Use when you need to check invitation status or get invitation metadata.
  - body: { identifier: string }
- `POST https://api.mcp.ai/api/affinda/get/job/description/search/config` — Tool to get the configuration for the logged in user's embeddable job description search tool. Returns display settings, field weights, and maximum results limits.
- `POST https://api.mcp.ai/api/affinda/get/mapping` — Tool to retrieve a specific mapping by its identifier. Use when you need to fetch mapping configuration details for a lookup against a MappingDataSource.
  - body: { identifier: string }
- `POST https://api.mcp.ai/api/affinda/get/organization` — Tool to retrieve details of a specific organization by its ID. Use when you need to fetch an organization's metadata after confirming its identifier.
  - body: { identifier: string }
- `POST https://api.mcp.ai/api/affinda/get/organization/membership` — Tool to retrieve details of a specific organization membership by its ID. Use when you need to confirm a user's role and details within an organization.
  - body: { identifier: string }
- `POST https://api.mcp.ai/api/affinda/get/organizations` — Retrieves all organizations accessible to the authenticated user. Returns a list of organizations with details including identifier, name, user role, trial status, and configuration settings. Use the 
- `POST https://api.mcp.ai/api/affinda/get/resthook/subscription` — Tool to retrieve details of a specific resthook subscription by its ID. Use after confirming its creation to verify its settings.
  - body: { identifier: integer }
- `POST https://api.mcp.ai/api/affinda/get/resthook/subscriptions` — Tool to retrieve a list of all RESTHook subscriptions. Use after authenticating to list all webhook subscriptions associated with your account.
  - body: { limit?: integer, offset?: integer }
- `POST https://api.mcp.ai/api/affinda/get/tag` — Tool to retrieve details of a specific tag by its ID. Use when you need to fetch information about a particular tag.
  - body: { tag_id: integer }
- `POST https://api.mcp.ai/api/affinda/get/usage/by/workspace` — Retrieves monthly document processing usage statistics for a specific workspace. Returns a list of usage records showing how many documents were processed each month. Use this to track workspace activ
  - body: { end?: string, start?: string, workspace_id: string }
- `POST https://api.mcp.ai/api/affinda/get/workspace` — Tool to retrieve details of a specific workspace by its ID. Use when you need full workspace metadata after confirming its identifier.
  - body: { identifier: string }
- `POST https://api.mcp.ai/api/affinda/get/workspace/membership` — Tool to retrieve details of a specific workspace membership by its ID. Use when you need to confirm a user's role and details within a workspace after obtaining the membership identifier.
  - body: { identifier: string }
- `POST https://api.mcp.ai/api/affinda/get/workspaces` — Tool to retrieve a list of all workspaces. Use when you need to list workspaces filtered by organization and optional name.
  - body: { name?: string, organization: string }
- `POST https://api.mcp.ai/api/affinda/list/data/point/choices` — Tool to retrieve available choices for a specific enum data point. Use when you need to discover valid options for dropdown/enum fields in a collection's data schema. Note: This endpoint is deprecated
  - body: { limit?: integer, offset?: integer, search?: string, collection: string, data_point: string }
- `POST https://api.mcp.ai/api/affinda/list/data/points` — Tool to retrieve all data points. Returns both custom data points and Affinda's off-the-shelf data points. Use when you need to list available data points for extractors.
  - body: { slug?: string, limit?: integer, offset?: integer, extractor?: string, identifier?: string[], description?: string, organization?: string, include_public?: boolean, annotation_content_type?: string }
- `POST https://api.mcp.ai/api/affinda/list/data/sources` — Tool to retrieve the list of all custom mapping data sources. Use when you need to list or search for mapping data sources in your Affinda workspace.
  - body: { name?: string, limit?: integer, offset?: integer, workspace?: string, identifier?: string, organization?: string }
- `POST https://api.mcp.ai/api/affinda/list/indexes` — Tool to retrieve a list of all search indexes. Use when you need to view available indexes for searching and matching documents in Affinda.
  - body: { name?: string, limit?: integer, offset?: integer, document_type?: string }
- `POST https://api.mcp.ai/api/affinda/list/mappings` — Tool to retrieve the list of all custom data mappings. Use when you need to list mappings for a specific data source.
  - body: { limit?: integer, offset?: integer, mappingDataSource: string }
- `POST https://api.mcp.ai/api/affinda/list/occupation/groups` — Tool to retrieve the list of searchable occupation groups. Use when you need to get available occupation categories for job matching or classification.
- `POST https://api.mcp.ai/api/affinda/list/resume/search/config` — Tool to get the configuration for the logged in user's embeddable resume search tool. Use this to retrieve display field settings, search weights, maximum results, and theme customization options for 
- `POST https://api.mcp.ai/api/affinda/list/resume/search/job/title/suggestions` — Tool to get job title suggestions based on provided job title(s). Use when you need to find related job titles for resume search.
  - body: { job_titles: string[] }
- `POST https://api.mcp.ai/api/affinda/list/resume/search/skill/suggestions` — Tool to get skill suggestions based on provided skills. Use when you need to find related skills to expand or refine resume search queries.
  - body: { skills: string[] }
- `POST https://api.mcp.ai/api/affinda/remove/tag/from/documents` — Remove a tag from multiple documents in a single batch operation. Use this action to efficiently untag many documents at once rather than making individual remove requests. The operation is idempotent
  - body: { tag: integer, identifiers: string[] }
- `POST https://api.mcp.ai/api/affinda/replace/data/point/choices` — Tool to completely replace all choices for a data point. Use when you need to bulk update enum options - existing choices are matched by value, new values are created, updated values are modified, and
  - body: { choices: object[], dataPoint: string, collection?: string, organization?: string }
- `POST https://api.mcp.ai/api/affinda/replace/data/source/values` — Tool to completely replace all values in a mapping data source. Use when you need to bulk update or refresh an entire data source's value list. Note: For large data sources (>1000 values), new values 
  - body: { values: object[], identifier: string }
- `POST https://api.mcp.ai/api/affinda/split/document/pages` — Split a document into multiple documents by dividing its pages. Use when you need to separate a multi-page document into distinct documents based on page groupings. Prerequisites: - Obtain the documen
  - body: { splits: object[], identifier: string }
- `POST https://api.mcp.ai/api/affinda/update/annotation` — Tool to update data of a single annotation in Affinda. Use when you need to correct extracted values, verify annotations, or modify annotation metadata after document processing. Prerequisites: - Obta
  - body: { id: integer, raw?: string, field?: string, parent?: integer, parsed?: string|integer|number|boolean|object|string|integer|number|boolean|object[], document?: string, dataPoint?: string, pageIndex?: integer, rectangles?: object[], isClientVerified?: boolean, validationResults?: object[] }
- `POST https://api.mcp.ai/api/affinda/update/collection` — Tool to update specific fields of a collection. Use when you need to rename or reassign a collection after creation.
  - body: { name?: string, identifier: string }
- `POST https://api.mcp.ai/api/affinda/update/data/field/for/collection` — Tool to update a data field configuration for a collection's data point. Use when you need to modify field properties such as label, type, mandatory status, or validation settings after the field has 
  - body: { label?: string, mapping?: string, fieldType?: string, mandatory?: boolean, dataSource?: string, identifier: string, showDropdown?: boolean, displayRawText?: string, displayEnumValue?: boolean, datapoint_identifier: string, autoValidationThreshold?: number, enableAutoValidationThreshold?: boolean }
- `POST https://api.mcp.ai/api/affinda/update/data/point` — Tool to update data of a data point by its identifier. Use when you need to modify a data point's name, description, slug, parent, or mapping data source. Note: This endpoint is deprecated but still f
  - body: { name?: string, slug?: string, parent?: string, identifier: string, description?: string, mappingDataSource?: string }
- `POST https://api.mcp.ai/api/affinda/update/data/point/choice` — Tool to update data of a data point choice by its ID. Use when you need to modify label, value, description, synonyms, or associated collection/organization for an existing data point choice. Note: Th
  - body: { id: integer, label?: string, value?: string, synonyms?: string[], dataPoint?: string, collection?: string, description?: string, organization?: string }
- `POST https://api.mcp.ai/api/affinda/update/data/source/value` — Tool to update an existing value in a mapping data source. Use when you need to modify the label or description of an existing data source value. The value identifier itself cannot be changed.
  - body: { label?: string, value: string, identifier: string, description?: string }
- `POST https://api.mcp.ai/api/affinda/update/document` — Tool to update specific fields of a document. Use when you need to rename, reassign, or adjust expiry and storage settings after document creation.
  - body: { fileName?: string, language?: string, workspace?: string, collection?: string, expiryTime?: string, identifier: string, regionBias?: object, customIdentifier?: string, deleteAfterParse?: boolean, enableValidationTool?: boolean }
- `POST https://api.mcp.ai/api/affinda/update/document/data` — Update parsed data for a resume or job description document in Affinda. This endpoint is ONLY applicable for documents that have been processed with 'resume' or 'job-description' extractors. For other
  - body: { data: object, identifier: string }
- `POST https://api.mcp.ai/api/affinda/update/document/type` — Tool to update a document type by its identifier. Use when you need to modify the name or description of an existing document type.
  - body: { name?: string, identifier: string, description?: string }
- `POST https://api.mcp.ai/api/affinda/update/extractor` — Tool to update specific fields of an extractor. Use when you need to modify an extractor's name, category, validation settings, or field groups after creation.
  - body: { name?: string, category?: string, identifier: string, namePlural?: string, fieldGroups?: object[], validatable?: boolean, baseExtractor?: string }
- `POST https://api.mcp.ai/api/affinda/update/index` — Tool to update the name of an existing search index. Use when you need to rename an index after creation.
  - body: { name: string, new_name?: string }
- `POST https://api.mcp.ai/api/affinda/update/invitation` — Tool to update an organization invitation's role. Use when you need to change the role assigned to an invitation before it is accepted.
  - body: { role?: string, identifier: string }
- `POST https://api.mcp.ai/api/affinda/update/job/description/search/config` — Tool to update the configuration for the logged in user's embeddable job description search tool. Use to configure display fields, field weights, maximum results, and UI customization options.
  - body: { userId?: integer, actions?: object[], indices?: string[], username?: string, maxResults?: integer, hideToolbar?: boolean, distanceUnit?: string, weightSkills?: number, displaySkills?: boolean, hideSidePanel?: boolean, weightJobTitle?: number, weightKeywords?: number, weightLocation?: number, displayJobTitle?: boolean, displayKeywords?: boolean, displayLocation?: boolean, searchToolTheme?: object, weightEducation?: number, weightLanguages?: number, allowPdfDownload?: boolean, displayEducation?: boolean, displayLanguages?: boolean, showIndexDropdown?: boolean, customFieldsConfig?: object[], weightManagementLevel?: number, weightOccupationGroup?: number, weightYearsExperience?: number, displayManagementLevel?: boolean, displayOccupationGroup?: boolean, displayYearsExperience?: boolean }
- `POST https://api.mcp.ai/api/affinda/update/mapping` — Tool to update a specific mapping's settings. Use when you need to adjust score cutoff or ordering for a lookup against a MappingDataSource.
  - body: { orderBy?: string, identifier: string, scoreCutoff?: number }
- `POST https://api.mcp.ai/api/affinda/update/organization` — Tool to update specific fields of an organization. Use when you need to modify an organization's name, avatar, or webhook and validation settings after creation.
  - body: { name?: string, avatar?: string, identifier: string, resthook_signature_key?: string, validation_tool_config?: object }
- `POST https://api.mcp.ai/api/affinda/update/organization/membership` — Tool to update an organization membership's role. Use when you need to change a user's role within an organization.
  - body: { role?: string, identifier: string }
- `POST https://api.mcp.ai/api/affinda/update/resthook/subscription` — Tool to update an existing RESTHook subscription. Use after confirming the subscription identifier to modify its URL, event, or activation status.
  - body: { event?: string, active?: boolean, targetUrl?: string, identifier: integer }
- `POST https://api.mcp.ai/api/affinda/update/resume/search/config` — Tool to update the configuration for the logged in user's embeddable resume search tool. Use this to modify which fields are displayed, their search weights, maximum results limit, distance units, cus
  - body: { userId?: integer, actions?: object[], indices?: string[], username?: string, maxResults?: integer, hideToolbar?: boolean, distanceUnit?: string, weightSkills?: number, displaySkills?: boolean, hideSidePanel?: boolean, weightJobTitle?: number, weightKeywords?: number, weightLocation?: number, displayJobTitle?: boolean, displayKeywords?: boolean, displayLocation?: boolean, searchToolTheme?: object, weightEducation?: number, weightLanguages?: number, allowPdfDownload?: boolean, displayEducation?: boolean, displayLanguages?: boolean, showIndexDropdown?: boolean, customFieldsConfig?: object[], weightManagementLevel?: number, weightOccupationGroup?: number, weightYearsExperience?: number, displayManagementLevel?: boolean, displayOccupationGroup?: boolean, displayYearsExperience?: boolean }
- `POST https://api.mcp.ai/api/affinda/update/tag` — Tool to update data of a tag. Use when you need to modify a tag's name or reassign it to a different workspace. Only provide the fields you want to change; other fields will remain unchanged.
  - body: { id: integer, name?: string, workspace?: string }
- `POST https://api.mcp.ai/api/affinda/update/workspace` — Tool to update specific fields of a workspace. Use when you need to modify a workspace's name, visibility, document rejection policy, or other settings. Only provide the fields you want to change; oth
  - body: { name?: string, visibility?: string, workspace_id: string, documentTypes?: string[], documentSplitter?: string, rejectDuplicates?: boolean, rejectInvalidDocuments?: boolean, whitelistIngestAddresses?: string[] }

## Example prompts
- "What can I do in Affinda?"
- "Show me a summary of my Affinda account"

## More
- Page: https://mcp.ai/affinda
- Agent spec (llms.txt): https://mcp.ai/affinda/llms.txt
- Postman collection: https://mcp.ai/affinda/postman.json