Frontitude MCP connector for AI agents

Tools your UX writing agent reaches for on Frontitude, scoped per user.

CALL ANY TOOL

34 tools for UX copy: search and list texts and copy components, write values and statuses, manage tags, variables, plurals, and categories, and comment for copy owners.

frontitudemcp_frontitude_add_comment

Frontitude add comment

Post a comment for the people who own this copy: answer a question they have asked, raise one of your own, flag a risk, or explain a change you are proposing. It writes no copy and changes no status, and it is the one write a viewer may make. Reply in a thread with discussionId, or start one on a text or a copy component. Posting the same message twice in a row is taken as one comment: an identical message from you within five minutes comes back with isChanged false and the comment already there. On a text or component target that covers every thread on it in that language pane, so a second thread carrying the same wording is not started there. Mentions are not delivered from here, so nobody is emailed. This runs in a single workspace, so an id read from another workspace is refused; ping reports the workspace you are in.

Parameters

Name

Type

Required

Description

message

string

Required

The comment to post. Plain text, written for the people who own this copy.

componentId

string

Optional

One copy component, the reusable piece of copy in the library. Starts a new thread on the component itself rather than on any of its instances. Pass exactly one of discussionId, textId, componentId.

discussionId

string

Optional

An existing comment thread, from get_text or get_component with include discussions. The reply joins that thread. Pass exactly one of discussionId, textId, componentId.

localeId

string

Optional

The language pane the new thread belongs to. Omit it to comment on the source language. A reply already has the pane its thread was started in. Pass it only alongside textId or componentId; the other alternatives refuse it.

textId

string

Optional

One text, meaning one use of copy in one project. Starts a new thread on it, in the project it belongs to. Pass exactly one of discussionId, textId, componentId.

frontitudemcp_frontitude_attach_texts

Frontitude attach texts

Make texts instances of a copy component, so they take its value and follow it from then on. Any variable the text fills in is captured from its value against the component template. Texts already belonging to another component are reported with the component blocking them, and the rest of the batch still attaches. A text already an instance of this component is left alone and comes back with isChanged false. Search results are unaffected: this writes the instances, never the component. A text holding a developer key of its own has that key cleared rather than moved to the component: from then on it reports the component's key, and detaching does not bring the old one back. One exception: an id nothing in this workspace answers to refuses the whole call, names the ids it could not find, and writes nothing. This runs in a single workspace, so an id read from another workspace is refused; ping reports the workspace you are in.

Parameters

Name

Type

Required

Description

componentId

string

Required

The copy component the texts become instances of.

localeId

string

Required

The language pane this call acts on. `main` is the source language; any other id is a translation. Use `list_scopes` with `scopeType: 'locale'` for the workspace's locales. Here it gives the pane pluralId applies to; the attach itself copies the component's copy into the text in every locale.

textIds

array

Required

The texts to attach, at most 50 per call. A text already attached to this component is left alone.

isCreateMissingPlaceholders

boolean

Optional

Register any placeholder value captured from the text against its workspace variable. This write is permanent even if the attach is rolled back. Default: `false`.

isDetachIfAlreadyAttached

boolean

Optional

A text that belongs to another component stops showing its own copy in every locale, takes this component's instead, and reports this component's key from then on, with none of the old coming back. This flag accepts that and moves it. Without it such a text is reported in failed and the rest still attach. Default: `false`.

pluralId

string

Optional

The plural form to act on. Omit it to take the form the component already shows in this locale; the empty string is the non-pluralized form. It has to be a form the component already has in this locale, since this call selects a form rather than writing one. Read the forms from get_component with the same localeId. One of: ``, `zero`, `one`, `two`, `few`, `many`, `other`.

frontitudemcp_frontitude_count_scope

Frontitude count scope

frontitudemcp_frontitude_create_components

Frontitude create components

frontitudemcp_frontitude_delete_category

Frontitude delete category

frontitudemcp_frontitude_delete_components

Frontitude delete components

frontitudemcp_frontitude_delete_tag

Frontitude delete tag

frontitudemcp_frontitude_delete_variable

Frontitude delete variable

Remove one example value from a workspace variable with remove_value, or delete the variable itself with delete_variable. remove_value keeps the variable and every other value it offers, and is refused while a component or an instance still shows the value. delete_variable rewrites every component value and every unattached text value that uses the variable, replacing the variable with the example value that entry shows, so the copy becomes literal text and cannot be turned back. A component takes its own example value, and every instance of it then shows that one, because the copy is the component's and can hold only one literal: an instance that had chosen an example of its own loses it. It drops everything it rewrote from new or final to draft, leaving anything at review where it stands, marks their translations as needing review and takes at most 200 affected components and texts. expectedAffectedCount confirms what that delete will rewrite; the action alone decides which of the two runs. Search and list results reflect the delete as soon as this call returns. This runs in a single workspace, so an id read from another workspace is refused; ping reports the workspace you are in.

Parameters

Name

Type

Required

Description

action

string

Required

What to do: remove_value takes one example value off the variable and leaves the variable in the workspace; delete_variable deletes the variable and rewrites every value using it into literal text, which cannot be turned back. One of: `remove_value`, `delete_variable`.

variableName

string

Required

The variable name, without braces. Matched exactly and case-sensitively.

expectedAffectedCount

integer

Optional

The number of components plus unattached texts whose values will be rewritten. Pass it when action is delete_variable; every other action refuses it. Count it first: list_components with variableName gives the components, and list_texts with type regular gives the unattached texts one project at a time, whose values show which of them use it. Both reads show the source language and the plural form each component currently shows, so a use that appears only in a translation or only in another plural form is counted by the write and not by these reads. The call is refused when the true number is different. The refusal writes nothing and reports that number, so a count that came out low costs one refused call and you send the number it named.

value

string

Optional

One example value to remove from the variable. The variable itself stays. Pass it when action is remove_value; every other action refuses it.

frontitudemcp_frontitude_get_component

Frontitude get component

frontitudemcp_frontitude_get_project_structure

Frontitude get project structure

frontitudemcp_frontitude_get_text

Frontitude get text

frontitudemcp_frontitude_list_component_instances

Frontitude list component instances

frontitudemcp_frontitude_list_components

Frontitude list components

List the reusable copy components in the copy library, in one category or across the whole library. Filter by name, status, tag, unique key, whether they have design instances, translated or missing in a locale, variable use, or last-changed date. Each row carries its pluralId, so a batch can be partitioned into pluralized and plain components from one call; a row is one selected plural form, so dedupe by id before writing. Use it to browse or audit the library by attribute; to find components by meaning use search instead. Pass exactly one of categoryId or wholeLibrary. Every row's value and status is the source language; use get_component with a localeId to read a translation. When hasMore is true, more rows follow: call again with offset set to nextOffset to read them.

Parameters

Name

Type

Required

Description

categoryId

string

Optional

List components filed directly in this category, not those in its subcategories. Takes a category id from list_scopes with scopeType category, not a name or a path. Pass exactly one of categoryId, wholeLibrary.

hasInstances

string

Optional

Only components that have (or lack) attached design instances. One of: `with-instances`, `without-instances`.

hasKey

string

Optional

Only components that have (or lack) a unique key. One of: `with-key`, `without-key`.

keyContains

string

Optional

Only components whose unique key contains this text.

limit

integer

Optional

Rows to return, max 100, default 50. Default: `50`.

missingTranslationLocaleId

string

Optional

Only components with no translation at all in this locale, not even one plural form. Use it to find what is left to translate; it is the exact complement of translatedInLocaleId.

nameMatch

string

Optional

Case-insensitive substring match on the component name, not on its value and not on its category path.

offset

integer

Optional

Rows to skip. Pass the nextOffset a page returned to read the next one, or any position you already know to reach that row in one call. Narrow the request with a filter where one applies. Default: `0`.

since

string

Optional

Only components changed at or after this ISO datetime (last change).

status

string

Optional

Only components in this status. One of: `new`, `draft`, `review`, `final`.

tagIds

array

Optional

Only components carrying all of these tag ids.

translatedInLocaleId

string

Optional

Only components translated in this locale. A pluralized component counts as translated once any of its forms is.

variableName

string

Optional

Only components whose value uses this variable.

wholeLibrary

boolean

Optional

List across the whole library instead of one category. Count the library first (count_scope) and prefer a narrowing filter. Pass exactly one of categoryId, wholeLibrary.

frontitudemcp_frontitude_list_scopes

Frontitude list scopes

Find Frontitude locations, tags, and variables by name and get the ids the other tools need. Lists folders, projects, categories, pages, frames, tags, variables, or locales, optionally narrowed to a name substring, each result carrying its id, name, parent, and how many children it holds. Start here when you have a name (a project called 'Checkout', a category called 'Errors', a tag called 'legal') but need its id. childCount is the scopes one level down, so subcategories for a category, except on a frame, where it is the frame's visible texts and count_scope and list_texts can report more for the same frame. A category also carries its fullPath and its componentCount, which is the components filed directly in it and never those in its subcategories, and a variable carries its list of values. A locale list that is not narrowed or paged past starts with the source language, whose id is main and whose own name Frontitude does not store, so it is reported as Source language. When you hold particular projects rather than the whole workspace, the folder and project lists name only those projects, and category is refused unless you can edit one of them. When hasMore is true, more rows follow: call again with offset set to nextOffset to read them.

Parameters

Name

Type

Required

Description

scopeType

string

Required

What to list. folder/project/category/tag/variable/locale live under the workspace; page requires a project parentId; frame requires a page parentId. One of: `folder`, `project`, `category`, `page`, `frame`, `tag`, `variable`, `locale`.

limit

integer

Optional

Rows to return, max 100, default 50. Default: `50`.

nameMatch

string

Optional

Case-insensitive substring match on the scope name. Omit to list all children.

offset

integer

Optional

parentId

string

Optional

Narrow to one parent: a folder id for projects, a parent category id for categories, a project id for pages (required), a page id for frames (required). folder, tag, variable, and locale sit under no parent and refuse it.

frontitudemcp_frontitude_list_texts

Frontitude list texts

List the texts placed in a project, page, frame, or across the whole workspace. Filter by status, type, tag, unique key, value, translation coverage, visibility, or last-changed date. Use it to enumerate the copy sitting in designs, as opposed to the reusable copy components (for those use list_components or search). Pass exactly one of projectId, pageId, frameId, or wholeWorkspace. Use valueContains to find copy in the designs by its wording and keyContains to find it by its developer key. Every row's value and status is the source language; use get_text with a localeId to read a translation. When hasMore is true, more rows follow: call again with offset set to nextOffset to read them.

Parameters

Name

Type

Required

Description

frameId

string

Optional

List texts in this frame.

hasKey

string

Optional

Only texts that have (or lack) a unique key. One of: `with-key`, `without-key`.

keyContains

string

Optional

Only texts whose unique key contains this text.

limit

integer

Optional

Rows to return, max 100, default 50. Default: `50`.

offset

integer

Optional

pageId

string

Optional

List texts in this page.

projectId

string

Optional

List texts in this project. Provide exactly one of projectId, pageId, frameId, or wholeWorkspace.

since

string

Optional

Only texts changed at or after this ISO datetime (last change).

status

string

Optional

Only texts in this status. One of: `new`, `draft`, `review`, `final`.

tagIds

array

Optional

Only texts carrying all of these tag ids.

translatedInLocaleId

string

Optional

Only texts that have a translation in this locale. The rows still carry the source-language value and status.

type

string

Optional

instance: attached to a component; regular: unattached. One of: `instance`, `regular`.

valueContains

string

Optional

Only texts whose value contains this text, matched on the source language. It searches the copy placed in designs, so reach for search_components when you are after the library entry behind it.

visibility

string

Optional

visible: exclude hidden texts; all: include them (default). One of: `visible`, `all`.

wholeWorkspace

boolean

Optional

Read every project you can access in this workspace instead of one location. Use it when you do not know which project a piece of copy sits in. It reaches a lot of copy, so narrow it with a filter, and read total on the first page before you page through the rest.

frontitudemcp_frontitude_manage_tag

Frontitude manage tag

frontitudemcp_frontitude_manage_variable

Frontitude manage variable

Create a workspace variable, rename one, or manage the example values it offers. rename and rename_value are the expensive ones: the name and the value are both stored inside every value that uses the variable, so both rewrite stored copy. rename writes a new revision of every component and text using the variable, in every locale, drops each of them from new or final to draft, leaving anything at review where it stands, and marks their translations as needing review. rename_value only swaps the shown value on the components and texts carrying that one value, writing no revision and changing no status. Both take at most 200 affected components and texts and both need expectedAffectedCount, counted over every use of the variable for rename and over the uses showing that one value for rename_value. A call that leaves the variable as it already is, including add_value with a value it already offers, writes nothing, comes back with isChanged false and does not check expectedAffectedCount. Search and list results reflect either as soon as this call returns; create and add_value change no stored copy. This runs in a single workspace, so an id read from another workspace is refused; ping reports the workspace you are in.

Parameters

Name

Type

Required

Description

action

string

Required

What to do: create adds a variable with no values yet; rename renames the variable and rewrites every stored value that uses it; add_value offers another example value on the variable; rename_value changes one of the example values, everywhere it is shown. One of: `create`, `rename`, `add_value`, `rename_value`.

variableName

string

Required

The variable name, without braces. Matched exactly and case-sensitively, so firstName and firstname are two variables.

expectedAffectedCount

integer

Optional

The number of components and texts whose values will be rewritten. Pass it when action is rename or rename_value; every other action refuses it. Count it first: list_components with variableName gives the components, and list_texts with type regular gives the unattached texts one project at a time, whose values show which of them use it. Both reads show the source language and the plural form each component currently shows, so a use that appears only in a translation or only in another plural form is counted by the write and not by these reads. For rename_value, get_component with include variables says which components show that one value, and every instance of such a component is counted as well. The call is refused when the true number is different. The refusal writes nothing and reports that number, so a count that came out low costs one refused call and you send the number it named.

newName

string

Optional

The new name, without braces. It must not already exist in the workspace. Pass it when action is rename; every other action refuses it.

newValue

string

Optional

The replacement example value. Pass it when action is rename_value; every other action refuses it.

value

string

Optional

One of the example values the variable offers, shown in place of it in the app. Pass it when action is add_value or rename_value; every other action refuses it.

frontitudemcp_frontitude_move_project

Frontitude move project

frontitudemcp_frontitude_ping

Frontitude ping

frontitudemcp_frontitude_remove_plurals

Frontitude remove plurals

Delete one plural form of a component, or turn plurals off for it entirely, in one locale. Both are permanent. delete_form takes deletedValue, the copy the named form holds, and turn_off takes deletedValues, the copy of every form it removes but the one on show; either is refused when the component holds something else, so copy is only destroyed by a caller that has read it. delete_form also refuses the form the component shows and any form an instance shows, because deleting it would change what those designs read. turn_off writes a new value revision, which resets the component to draft if it stood at new or final, and marks its translations as needing review. It also narrows every instance to the variables the form it keeps uses: a placeholder an instance chose for any other variable is gone in this locale. Search and list results reflect this change as soon as this call returns. This runs in a single workspace, so an id read from another workspace is refused; ping reports the workspace you are in.

Parameters

Name

Type

Required

Description

action

string

Required

What to do: delete_form removes one plural form and its values, keeping the component pluralized; turn_off removes every plural form, leaving the component with the single value it shows now. One of: `delete_form`, `turn_off`.

localeId

string

Required

The language pane this call acts on. `main` is the source language; any other id is a translation. Use `list_scopes` with `scopeType: 'locale'` for the workspace's locales.

componentId

string

Optional

The copy component to change. Every instance of it in every project follows. Pass exactly one of componentId, textId.

deletedValue

string

Optional

The copy the form named in pluralId holds in this locale, copied over exactly. It is the wording this call destroys, so read it first from get_component with include plurals and the same localeId. The empty string says the form holds no copy. Pass it when action is delete_form; every other action refuses it.

deletedValues

array

Optional

The copy of every form turn_off removes but the one the component shows now, whose copy stays as the single value it keeps: one entry per form, in any order, and an empty list when the shown form is the only one. Read them first from get_component with include plurals and the same localeId, which marks the shown form isSelected. The empty string stands for a form holding no copy. Pass it when action is turn_off; every other action refuses it.

pluralId

string

Optional

One of the plural forms the component has in this locale. Read them from get_component with the same localeId; the non-plural form is not one of them. Pass it when action is delete_form; every other action refuses it. One of: `zero`, `one`, `two`, `few`, `many`, `other`.

textId

string

Optional

One text. Its component is what changes, so every other instance of that component follows too. get_text with include component gives that componentId. Pass exactly one of componentId, textId.

frontitudemcp_frontitude_search_components

Frontitude search components

Find copy components by meaning rather than exact wording. Give a natural-language query (for example 'error shown when a payment fails') and get the closest-matching components ranked by relevance, optionally filtered by category, status, or translation coverage. Use it when you know roughly what a piece of copy says but not where it lives. Only close matches come back, so an empty page is not proof the library holds nothing like the query: retry with different wording, or with the filters dropped, before treating the copy as missing. It returns a single ranked page and cannot be paged: if hasMore says the matches were cut, ask a narrower query or use list_components, which pages. Each row's fullPath ends in the component's own name, so drop the last segment to get the category path it is filed under. It covers the copy library only, not the texts placed in individual projects, so it is not a search of every piece of copy in the product. Every row's value and status is the source language, and so is the wording the query is matched against. get_component with a localeId reads what one translation says. translatedInLocaleId, translationStatus and missingTranslationLocaleId narrow on whether a translation exists and the status it holds, never on what it says.

Parameters

Name

Type

Required

Description

query

string

Required

Natural-language text to match semantically against component copy in the library. It is matched against the wording alone, so a project, screen or component name in the query pulls it away from the copy rather than narrowing it: describe what the copy says, and use categoryId to narrow where it lives.

categoryId

string

Optional

Restrict to components under this category (and its subcategories). Takes a category id from list_scopes with scopeType category, not a name or a path.

limit

integer

Optional

Rows to return, max 50, default 20. Default: `20`.

missingTranslationLocaleId

string

Optional

Only components with no translation at all in this locale, not even one plural form. It is the exact complement of translatedInLocaleId. It must be one locale of the workspace, and any other value is refused.

status

string

Optional

Only components in this status. One of: `new`, `draft`, `review`, `final`.

translatedInLocaleId

string

Optional

Only components that have a translation in this locale (optionally narrowed by translationStatus). A pluralized component counts as translated once any of its forms is. It must be one locale of the workspace, and any other value is refused.

translationStatus

string

Optional

Require the translation to be in this status. Pass it only alongside translatedInLocaleId, which names the locale it narrows; on its own it is refused. One of: `new`, `draft`, `review`, `final`.

frontitudemcp_frontitude_set_selected_plural

Frontitude set selected plural

frontitudemcp_frontitude_set_status

Frontitude set status

Move copy components or texts to a new status in one locale. Moving source-language copy to final can start auto-translation and spend the workspace translation quota, and unattached texts moved to final can create components in whichever workspace those texts belong to. A write whose translations would carry the workspace past its translation allowance translates nothing, turns auto-translation off for the whole workspace, and emails the workspace admin. Nothing here turns it back on. Unattached texts in the same call that hold the same copy get one component between them, built from the last of them, so in every other locale the others take its translation in place of their own. A component created here holds no developer key, and the text it was created from loses the key it was reporting: read that key with get_text first if you mean to keep it, and set it on the component with set_unique_key. A placeholder value the workspace variable does not list yet is added to it, workspace-wide. A workspace can have that creation switched off, in which case createdComponents comes back empty however many texts moved, and create_components is the way to make one. Auto-translation, if it triggers, runs after this call returns, so the counts here are a projection rather than a record. Anything already at the status is left alone and comes back with isChanged false, so a repeat spends no quota and logs nothing. Search and list results reflect this change as soon as this call returns. This runs in a single workspace, so an id read from another workspace is refused; ping reports the workspace you are in.

Parameters

Name

Type

Required

Description

localeId

string

Required

The language pane this call acts on. `main` is the source language; any other id is a translation. Use `list_scopes` with `scopeType: 'locale'` for the workspace's locales.

status

string

Required

The status to move everything listed to, in the locale given on the call. One of: `new`, `draft`, `review`, `final`.

componentIds

array

Optional

The copy components to move, at most 50 per call. A component is the reusable piece of copy in the library. Pass exactly one of componentIds, textIds.

textIds

array

Optional

The texts to move, at most 50 per call. A text is one use of copy in one project. A text attached to a component moves that shared component too. Pass exactly one of componentIds, textIds.

frontitudemcp_frontitude_set_text_hidden

Frontitude set text hidden

frontitudemcp_frontitude_set_unique_key

Frontitude set unique key

frontitudemcp_frontitude_update_component_metadata

Frontitude update component metadata

frontitudemcp_frontitude_update_component_values

Frontitude update component values

Write the values of copy components in one locale, either the source language or a translation. A source-language write resets every translation of those components that stood at review or final to new, and drops the component itself from new or final to draft unless the call passes a status. A translation left at draft, and a component at review, are where they were. effects.translationStatusResets counts the translations it reset. A component used by more than one text takes acknowledgedInstances, because writing it writes every one of them. A first write into a translation locale is stored and selected, so it shows in the app straight away. Writing the value a component already holds writes nothing for it: no revision, no translation reset and no webhook, and the item comes back with isChanged false. Each item also reports which effects fired, so a call that moved the status but not the value is legible. Send expectedValue on an item to have the whole call refused when that component no longer holds the value you read, rather than writing over somebody else. Search and list results reflect this change as soon as this call returns. This runs in a single workspace, so an id read from another workspace is refused; ping reports the workspace you are in.

Parameters

Name

Type

Required

Description

localeId

string

Required

The locale to write. `main` is the source language, not a translation: writing there replaces the original copy and resets every translation. Use `list_scopes` with `scopeType: 'locale'` for the workspace's locales.

updates

array

Required

The components to write, at most 25 per call and at most 10 when the locale is the source language.

acknowledgedInstances

integer

Optional

How many texts this call writes, added up over the components named. Required when any of them is used by more than one text, since writing a component writes every text using it, and refused when it is not the true number. get_component reports the number per component as textsCount, and list_components reports it on each row.

isSetSelectedPlural

boolean

Optional

Make the plural form given here the one the component displays in this locale. Default: `false`.

pluralId

string

Optional

The plural form to write. Omit it to keep the form the component already uses in this locale; the empty string is the non-pluralized form. Passing a form on a component that is not pluralized turns plurals on for it and for every instance of it. One of: ``, `zero`, `one`, `two`, `few`, `many`, `other`.

status

string

Optional

The status to leave the components at. Without it a component at new or final drops to draft, because its copy changed. Setting final on the source language starts auto-translation and spends the workspace translation quota after this call returns. A write whose translations would carry the workspace past its translation allowance translates nothing, turns auto-translation off for the whole workspace, and emails the workspace admin. Nothing here turns it back on. It applies to every update in the call, so it sits beside updates and not inside one. One of: `new`, `draft`, `review`, `final`.

frontitudemcp_frontitude_update_tags

Frontitude update tags

Add or remove workspace tags on copy components or on texts. A tag is given by label or by id, and both resolve in the workspace of the rows you pass, so a tag from another workspace cannot be written. isCreateMissingTags acts on labels only; an id matching no tag is reported in failed. A label or id that does not resolve costs only that tag, and the tags that did resolve are still written on every row listed. Minting a tag takes a place in the workspace holding the rows, so on the textIds branch a workspace you only hold a project in refuses the flag and the whole call with it, whether or not the label needed creating; pass a tag that workspace already has instead. manage_tag only ever creates in the one this connection works in. Pass at least one of addLabels, removeLabels, addTagIds or removeTagIds. Adding and removing land together or not at all, and the result says which ran. A row that already carries every tag being added and none being removed is left alone and comes back with isChanged false. This runs in a single workspace, so an id read from another workspace is refused; ping reports the workspace you are in.

Parameters

Name

Type

Required

Description

addLabels

array

Optional

Tag labels to add, at most 50 per call. Matched case-insensitively against the workspace tags, so a label takes no lookup first: pass the name the caller gave and one the workspace does not have is reported in failed.

addTagIds

array

Optional

Tag ids to add, at most 50 per call, as list_scopes with scopeType tag returns them. An id the workspace does not have is reported in failed; isCreateMissingTags cannot create one.

componentIds

array

Optional

The copy components to tag, at most 50 per call. A component is the reusable piece of copy in the library. Pass exactly one of componentIds, textIds.

isCreateMissingTags

boolean

Optional

Create any label in addLabels the workspace does not have yet, rather than reporting it in failed. Does not apply to addTagIds. On the textIds branch a workspace you only hold a project in refuses this flag and the whole call with it, whether or not the label needed creating. Default: `false`.

removeLabels

array

Optional

Tag labels to remove, at most 50 per call. A label the workspace does not have is reported in failed.

removeTagIds

array

Optional

Tag ids to remove, at most 50 per call. An id the workspace does not have is reported in failed.

textIds

array

Optional

The texts to tag, at most 50 per call. A text is one use of copy in one project. Pass exactly one of componentIds, textIds.

frontitudemcp_frontitude_update_text_values

Frontitude update text values

Write the copy of texts in one locale. A text attached to a copy component writes through to that component, so every translation of it resets and effects.translationStatusResets counts those resets. Where that component is used by more than one text the write is refused, because it would change copy in texts this call never named: write the component with update_component_values. An unattached text changes on its own. Writing a value can also attach a text to a component that already holds the same copy, which is reported in autoAttachedComponentIds. Writing the copy a text already holds writes nothing for it: no revision, no translation reset and no webhook, and the item comes back with isChanged false. Each item also reports which effects fired, so a call that moved the status but not the copy is legible. Send expectedValue on an item to have the whole call refused when that text no longer holds the copy you read, rather than writing over somebody else. Search and list results reflect this change as soon as this call returns. This runs in a single workspace, so an id read from another workspace is refused; ping reports the workspace you are in.

Parameters

Name

Type

Required

Description

localeId

string

Required

updates

array

Required

The texts to write, at most 25 per call and at most 10 when the locale is the source language.

isSetSelectedPlural

boolean

Optional

Make the plural form given here the one the text displays in this locale. Default: `false`.

pluralId

string

Optional

status

string

Optional

The status to leave the texts at. Without it a text at new or final drops to draft, because its copy changed. Setting final on the source language starts auto-translation and spends the workspace translation quota after this call returns. A write whose translations would carry the workspace past its translation allowance translates nothing, turns auto-translation off for the whole workspace, and emails the workspace admin. Nothing here turns it back on. Where the workspace creates a copy component from a text reaching final, an unattached text is refused here and set_status is the tool for it. When the value written attaches a text to a copy component, the status lands on that component and moves every other instance of it. It applies to every update in the call, so it sits beside updates and not inside one. One of: `new`, `draft`, `review`, `final`.

frontitudemcp_frontitude_upsert_category

Frontitude upsert category

For more tools, view docs.

Build your Agent

Same auth pattern across LangChain, OpenAI, Anthropic, and Google ADK.

import { ScalekitClient } from "@scalekit-sdk/node";
import { createReactAgent } from "@langchain/langgraph/prebuilt";

const sk = new ScalekitClient(env.SCALEKIT_ENV_URL, env.SCALEKIT_CLIENT_ID, env.SCALEKIT_CLIENT_SECRET);

// Frontitude MCP tools scoped to this user
const { tools } = await sk.tools.listScopedTools("user_123", {
  filter: { connectionNames: ["frontitudemcp"], toolNames: [
    "frontitudemcp_frontitude_search_components",
    "frontitudemcp_frontitude_list_texts",
    "frontitudemcp_frontitude_get_component"] },
  pageSize: 100,
});

const agent = createReactAgent({ llm, tools });
await agent.invoke({ messages: [{ role: "user", content: "Find copy components for the error shown when a payment fails" }] });

import OpenAI from "openai";
import { ScalekitClient } from "@scalekit-sdk/node";

const sk = new ScalekitClient(env.SCALEKIT_ENV_URL, env.SCALEKIT_CLIENT_ID, env.SCALEKIT_CLIENT_SECRET);
const openai = new OpenAI();

const { tools } = await sk.tools.listScopedTools("user_123", {
  filter: { connectionNames: ["frontitudemcp"] }, pageSize: 100,
});

const res = await openai.chat.completions.create({
  model: "gpt-5",
  messages: [{ role: "user", content: "Find copy components for the error shown when a payment fails" }],
  tools,
});

// Execute the tool call with the user's vaulted Frontitude token
await sk.tools.executeTool(res.choices[0].message.tool_calls[0], "user_123");

import Anthropic from "@anthropic-ai/sdk";
import { ScalekitClient } from "@scalekit-sdk/node";

const sk = new ScalekitClient(env.SCALEKIT_ENV_URL, env.SCALEKIT_CLIENT_ID, env.SCALEKIT_CLIENT_SECRET);
const anthropic = new Anthropic();

const { tools } = await sk.tools.listScopedTools("user_123", {
  filter: { connectionNames: ["frontitudemcp"] }, pageSize: 100,
});

const msg = await anthropic.messages.create({
  model: "claude-sonnet-5",
  max_tokens: 1024,
  messages: [{ role: "user", content: "Find copy components for the error shown when a payment fails" }],
  tools,
});

// Tool call runs with the user's vaulted Frontitude token
await sk.tools.executeTool(msg.content, "user_123");

import { Agent } from "@google/adk/agents";
import { ScalekitClient } from "@scalekit-sdk/node";

const sk = new ScalekitClient(env.SCALEKIT_ENV_URL, env.SCALEKIT_CLIENT_ID, env.SCALEKIT_CLIENT_SECRET);

const { tools } = await sk.tools.listScopedTools("user_123", {
  filter: { connectionNames: ["frontitudemcp"] }, pageSize: 100,
});

const agent = new Agent({
  name: "copy_agent",
  model: "gemini-2.5-pro",
  instruction: "Frontitude MCP tools scoped to this user",
  tools,
});

await agent.run("Find copy components for the error shown when a payment fails");

Try these prompts

Copy any prompt into your agent. Each maps directly to a Frontitude MCP tool. Click to copy, paste into your agent, done.

Find copy

Copy the prompt

Copied

Find copy components for the error shown when a payment fails.

Copy the prompt

Copied

List draft texts in the Checkout project.

Copy the prompt

Copied

Where is the Save changes component used?

Edit copy

Copy the prompt

Copied

Update the Payment declined component to a shorter message.

Copy the prompt

Copied

Move these components to final status in English.

Copy the prompt

Copied

Add the onboarding tag to these texts.

Organize the library

Copy the prompt

Copied

Create a library category for billing copy.

Copy the prompt

Copied

Give these components developer keys in our key format.

Copy the prompt

Copied

Comment on this text asking the owner to confirm the tone.

SEE HOW AUTH WORKS

Each user signs in to Frontitude once; Scalekit stores and refreshes their tokens. Every call is scope checked, and every action is logged.

Authorize

Your user connects

Frontitude MCP

once. We tie it to their identity and the meetings they approved — no shared bot account, no org-wide access

Who:

user ‘A’

when:

Once per user

access:

Limited to user

Store

Their

Frontitude MCP

token lives in a vault scoped to them. User A's meetings are never reachable by an agent acting for user B, even on the same connection

vault:

encrypted

scope:

per-user

tokens:

auto-refreshed

Resolve

When your agent calls a

Frontitude MCP

tool, we fetch the right token server-side. It never touches your agent, never appears in the LLM context, never shows up in your logs

speed:

~40ms

check:

before every call

seen by:

nobody

Audit

Every

Frontitude MCP

tool call is logged — who triggered it, which meeting was fetched, what came back. 90 days of history, tied to the user who authorized it

history:

90 days

export:

SIEM-ready

logged:

every call

Test other agents

See the same per-user auth pattern across other design and content connectors.

Engineering Teams

Auto release notes agent

Reads merged GitHub PRs, groups them into structured release notes, publishes the page to Notion, and announces the release in Slack. Every call runs on the engineer's own delegated OAuth.

Engineering Teams

Engineering standup agent

Pulls commits from GitHub and GitLab, tracks issue movement in Jira, and posts a per-engineer standup brief to Slack. Each engineer's activity is read on their own delegated OAuth.

Engineering Teams

Slack triage

Polls Slack for new messages, classifies bugs and support requests with a LangGraph router, files GitHub issues or Zendesk tickets, and confirms in the thread.

Engineering Teams

DevOps assistant agent

Polls GitHub for failing checks and stale PRs, opens Linear issues for the ones that need work, and posts a daily digest to Slack. It acts as the engineer, not a shared service account.

Why Scalekit

Secure your agent's access. Connectors ship in minutes

01.

Shared tokens break per-user analytics

A shared Frontitude token looks fine in a demo. In production every copy edit looks like one service account, and you cannot tell which user triggered it. Scalekit resolves the credential of the actual user who triggered the agent, never a shared bot.

// shared token
audit → bot_service_account

// scalekit
audit → user_abc ✓

02.

Authentication is not authorization

03.

Multi-tenancy is architectural

04.

Frontitude today. Ten connectors tomorrow.

“Our agents act across Salesforce, Gong, Google Drive, and more, on behalf of every customer. Scalekit behind the scenes meant we can keep adding tools without ever rebuilding how credentials or tool calling work.”

Venu Madhav Kattagoni

Head of Engineering / Von

FAQs

Frequently Asked Questions

Does the agent access Frontitude as the user or as a shared key?

As the user. Each user signs in to Frontitude once, and Scalekit stores and refreshes their tokens. Audit logs attribute every action to that user, not a shared service account.

Where is the Frontitude OAuth token stored?

In Scalekit's managed AES-256 token vault, namespaced per tenant. Refresh is automatic. Revocation is a single dashboard action. Credentials never appear in prompts, logs, or LLM context.

Can I limit what the agent does in Frontitude?

Yes. Filter by tool name in listScopedTools to expose only what you want. Scalekit also enforces scope checks before every API call.

What happens when a user revokes Frontitude access?

The connection is invalidated on the next tool call. Subsequent requests for that user fail closed with a clear error. Other users in the tenant remain unaffected. The event is logged for audit.

Can the agent change live copy?

Only through the tools you expose. 24 of the 34 tools write or are destructive, from frontitudemcp_frontitude_update_text_values to frontitudemcp_frontitude_delete_components. Moving source-language copy to final with frontitudemcp_frontitude_set_status can start auto-translation and spend the workspace translation quota, so start with the read tools plus frontitudemcp_frontitude_add_comment.

On this page

Tool and actions Framework Compatibility Starter Prompt Auth Lifecycle Try Other Agents Why Scalekit