ima MCP integration for AI agents.
Connect AI agents to ima through 17 structured actions, including check repeated names, add note to knowledge base, and append note. Review authentication, i…
- ACTION CONTRACTS
- 17
- AUTHENTICATION
- Custom credentials
- SOURCE STATUS
- Provider-backed
CATALOG SOURCE REVIEWED AUGUST 23, 2026 / ACTION NAMES AND SCHEMAS DERIVED FROM WORKING MACHINES PROVIDER SOURCE
CAPABILITY PROFILE
What the ima integration exposes
The ima Agent App exposes 17 provider-backed actions for ai and productivity work. Its current contract lets an authorized agent check whether file names already exist in an ima knowledge-base folder, add an existing ima note into one ima knowledge base, and append markdown content to an existing ima note. These operations are called through Working Machines as typed capabilities rather than through browser navigation or copied UI steps.
A connection uses Custom credentials. 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 ima account, granted provider permissions, workspace policy, region, plan, and upstream API behavior.
VERIFIED ACTION SAMPLE
Real ima capabilities.
Showing 12 of 17 actions. Risk labels are conservative signals based on operation names, not substitutes for provider documentation or runtime policy.
check_repeated_namesREADCheck whether file names already exist in an IMA knowledge-base folder.
INPUTS: knowledgeBaseId / folderId / files
add_note_to_knowledge_baseWRITEAdd an existing IMA note into one IMA knowledge base.
INPUTS: knowledgeBaseId / folderId / noteId / title
append_noteREVIEWAppend Markdown content to an existing IMA note.
INPUTS: noteId / content
create_noteWRITECreate a new IMA note from Markdown content.
INPUTS: content / folderId / folderName
get_knowledge_basesREADFetch metadata for one or more IMA knowledge bases.
INPUTS: knowledgeBaseIds
get_knowledge_item_originalREADFetch access information for a knowledge-base item and download URL-backed original content through local transit storage when available.
INPUTS: mediaId / fileName
get_media_infoREADGet IMA knowledge-base media access information for one media item.
INPUTS: mediaId
get_note_contentREADFetch the plain-text or JSON content for one IMA note.
INPUTS: noteId / targetContentFormat
import_urlsWRITEImport webpages or WeChat article URLs into one IMA knowledge base.
INPUTS: knowledgeBaseId / folderId / urls
list_addable_knowledge_basesREADList the IMA knowledge bases that accept new content.
INPUTS: cursor / limit
list_knowledge_itemsREADList files and folders inside one IMA knowledge-base folder.
INPUTS: knowledgeBaseId / folderId / cursor / limit
list_notebooksREADList IMA note folders for the connected account.
INPUTS: cursor / limit
INPUT CONTRACTS
Know what the action needs before it runs.
check_repeated_names
knowledgeBaseIdREQUIRED- The IMA knowledge base ID.
folderIdOPTIONAL- The target folder ID inside the knowledge base.
filesREQUIRED- The files to check for duplicate names.
add_note_to_knowledge_base
knowledgeBaseIdREQUIRED- The IMA knowledge base ID.
folderIdOPTIONAL- The target folder ID inside the knowledge base.
noteIdREQUIRED- The IMA note ID to add.
titleREQUIRED- The title to use for the knowledge-base item.
append_note
noteIdOPTIONAL- The target IMA note ID.
contentOPTIONAL- The Markdown content to append to the note.
create_note
contentREQUIRED- The Markdown content to import as a new note.
folderIdOPTIONAL- The notebook folder ID that should receive the new note.
folderNameOPTIONAL- The notebook folder name that should receive the new note.
PROVIDER-SPECIFIC WORKFLOWS
Jobs this Agent App can support
Inspect Check Repeated Names
Check whether file names already exist in an IMA knowledge-base folder. Use this as a bounded discovery step, retain the returned identifier, and avoid expanding the read beyond the task's stated scope.
check_repeated_namesControl Add Note To Knowledge Base
Add an existing IMA note into one IMA knowledge base. Resolve the target first, present material changes for confirmation, and make retries idempotent where the provider supports it.
add_note_to_knowledge_baseVerify with Get Knowledge Bases
Fetch metadata for one or more IMA knowledge bases. Compare the returned provider state with the intended outcome and preserve stable IDs or canonical links in the run record.
get_knowledge_basesSAFETY BOUNDARY
Operate ima with explicit limits
- Authorize ima with Custom credentials and grant only the provider access required by the selected actions.
- 4 actions are change-capable by name. Confirm the target identity and material parameters before allowing a write.
- 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 ima rather than assuming unrestricted access.
- After a call, inspect the structured result and execution record before reporting that the ima task completed successfully.
CONNECTION MODEL
Custom credentials
ima uses Custom credentials. Connection requirements and availability are determined by the provider and the Working Machines deployment.
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
- 12
- WRITE SIGNALS
- 4
- HIGH IMPACT
- 0
- REVIEW SIGNALS
- 1
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 ima.