Tisane MCP integration for AI agents.
Connect AI agents to Tisane through 7 structured actions, including list supported languages, analyze text, and calculate similarity. Review authentication…
- ACTION CONTRACTS
- 7
- AUTHENTICATION
- API key
- SOURCE STATUS
- Provider-backed
CATALOG SOURCE REVIEWED AUGUST 23, 2026 / ACTION NAMES AND SCHEMAS DERIVED FROM WORKING MACHINES PROVIDER SOURCE
CAPABILITY PROFILE
What the Tisane integration exposes
The Tisane Agent App exposes 7 provider-backed actions for ai and security work. Its current contract lets an authorized agent list the languages currently supported by tisane, analyze text with tisane for problematic content, sentiment, entities, topics, and other linguistic features, and calculate the semantic similarity between two text fragments, either in one language or across languages. These operations are called through Working Machines as typed capabilities rather than through browser navigation or copied UI steps.
A connection uses API key. Before execution, the agent can inspect the selected action, its required fields, declared scopes, and expected output contract. Provider credentials remain inside the Working Machines runtime; the calling agent receives the capability and its structured result, not the underlying secret.
For reliable operation, start with the narrowest action that satisfies the task, resolve stable provider identifiers before changing state, and validate the returned object or status after execution. Availability still depends on the connected Tisane account, granted provider permissions, workspace policy, region, plan, and upstream API behavior.
VERIFIED ACTION SAMPLE
Real Tisane capabilities.
Showing 7 of 7 actions. Risk labels are conservative signals based on operation names, not substitutes for provider documentation or runtime policy.
list_supported_languagesREADList the languages currently supported by Tisane.
analyze_textREVIEWAnalyze text with Tisane for problematic content, sentiment, entities, topics, and other linguistic features.
INPUTS: language / content / settings
calculate_similarityREVIEWCalculate the semantic similarity between two text fragments, either in one language or across languages.
INPUTS: language1 / content1 / language2 / content2 / settings
compare_entitiesREVIEWCompare two compound person entities with Tisane and return whether they are the same or different.
INPUTS: language1 / entity1 / language2 / entity2 / type
detect_languageREVIEWDetect the language segments used in a text fragment with optional language hints and delimiter settings.
INPUTS: content / languages / delimiter
extract_textREVIEWRemove markup such as HTML, CSS, JavaScript, or JSON from UTF-8 text and return plain decoded text.
INPUTS: content
transform_textREVIEWTranslate text between languages with Tisane, or paraphrase text when source and target languages match.
INPUTS: from / to / content / settings
INPUT CONTRACTS
Know what the action needs before it runs.
analyze_text
languageREQUIRED- The IETF language tag used by Tisane, such as en or zh-CN.
contentREQUIRED- The UTF-8 text content to send to Tisane.
settingsOPTIONAL- Optional Tisane settings forwarded to the endpoint. Use official Tisane configuration keys.
calculate_similarity
language1REQUIRED- The IETF language tag used by Tisane, such as en or zh-CN.
content1REQUIRED- The first UTF-8 text fragment to compare.
language2REQUIRED- The IETF language tag used by Tisane, such as en or zh-CN.
content2REQUIRED- The second UTF-8 text fragment to compare.
settingsOPTIONAL- Optional Tisane settings forwarded to the endpoint. Use official Tisane configuration keys.
compare_entities
language1OPTIONAL- The IETF language tag used by Tisane, such as en or zh-CN.
entity1OPTIONAL- The first person entity text to compare.
language2OPTIONAL- The IETF language tag used by Tisane, such as en or zh-CN.
entity2OPTIONAL- The second person entity text to compare.
typeOPTIONAL- The entity type to compare. Tisane currently supports person.
detect_language
contentREQUIRED- The UTF-8 text content to send to Tisane.
languagesOPTIONAL- Optional vertical-bar-delimited language hints, such as en|ru|he.
delimiterOPTIONAL- Optional delimiter expression used by Tisane to segment the text.
PROVIDER-SPECIFIC WORKFLOWS
Jobs this Agent App can support
Inspect List Supported Languages
List the languages currently supported by Tisane. Use this as a bounded discovery step, retain the returned identifier, and avoid expanding the read beyond the task's stated scope.
list_supported_languagesVerify with Analyze Text
Analyze text with Tisane for problematic content, sentiment, entities, topics, and other linguistic features. Compare the returned provider state with the intended outcome and preserve stable IDs or canonical links in the run record.
analyze_textSAFETY BOUNDARY
Operate Tisane with explicit limits
- Authorize Tisane with API key and grant only the provider access required by the selected actions.
- The current action names appear read-oriented, but returned Tisane data may still be sensitive and should be minimized before it enters model context.
- Do not infer permission from catalog visibility. Workspace policy, connection identity, and upstream authorization still govern execution.
- No provider scope string is declared on the sampled actions. Verify the connected account's actual permissions in Tisane rather than assuming unrestricted access.
- After a call, inspect the structured result and execution record before reporting that the Tisane task completed successfully.
CONNECTION MODEL
API key
Tisane API subscription key sent in the Ocp-Apim-Subscription-Key header. View your key in the Tisane Developer Portal.
Working Machines stores provider credentials behind the execution boundary. An agent can use an authorized connection identity, but catalog discovery alone does not reveal OAuth tokens, API keys, or provider secrets.
- READ SIGNALS
- 1
- WRITE SIGNALS
- 0
- HIGH IMPACT
- 0
- REVIEW SIGNALS
- 6
EVIDENCE AND AVAILABILITY
Provider reference
Action names, input fields, authentication types, and counts on this page are generated from the Working Machines provider catalog. Provider behavior, quotas, object semantics, account eligibility, and regional availability remain governed by Tisane.