Memos MCP integration for AI agents.
Connect AI agents to Memos through 14 structured actions, including get attachment, create memo, and delete attachment. Review authentication, inputs, workfl…
- ACTION CONTRACTS
- 14
- 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 Memos integration exposes
The Memos Agent App exposes 14 provider-backed actions for productivity work. Its current contract lets an authorized agent retrieve one attachment's metadata by resource name, create a markdown memo on the connected memos instance, and delete one attachment by resource name. 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 Memos account, granted provider permissions, workspace policy, region, plan, and upstream API behavior.
VERIFIED ACTION SAMPLE
Real Memos capabilities.
Showing 12 of 14 actions. Risk labels are conservative signals based on operation names, not substitutes for provider documentation or runtime policy.
get_attachmentREADRetrieve one attachment's metadata by resource name.
INPUTS: name
create_memoWRITECreate a Markdown memo on the connected Memos instance.
INPUTS: content / visibility / memoId / createTime / pinned
delete_attachmentHIGH IMPACTDelete one attachment by resource name.
INPUTS: name
delete_memoHIGH IMPACTDelete one memo, optionally forcing deletion when associated data exists.
INPUTS: name / force
get_current_userREADRetrieve the Memos user associated with the connected personal access token.
get_memoREADRetrieve one memo by its Memos resource name.
INPUTS: name
get_userREADRetrieve one Memos user by resource name.
INPUTS: name / readMask
list_attachmentsREADList attachment metadata with pagination, filtering, and ordering.
INPUTS: pageSize / pageToken / filter / orderBy
list_memo_attachmentsREADList attachments associated with one memo.
INPUTS: name / pageSize / pageToken
list_memosREADList memos with pagination, state selection, ordering, and CEL filtering.
INPUTS: pageSize / pageToken / state / orderBy / filter
list_usersREADList users visible to the connected Memos account.
INPUTS: pageSize / pageToken / filter / showDeleted
set_memo_attachmentsWRITEReplace the complete attachment set associated with one memo.
INPUTS: name / attachmentNames
INPUT CONTRACTS
Know what the action needs before it runs.
get_attachment
nameREQUIRED- The Memos attachment resource name in the format attachments/{attachment}.
create_memo
contentREQUIRED- The memo content in Markdown format.
visibilityOPTIONAL- The memo visibility.
memoIdOPTIONAL- An optional caller-selected memo ID.
createTimeOPTIONAL- An optional creation time for imported content.
pinnedOPTIONAL- Whether the new memo should be pinned.
delete_attachment
nameREQUIRED- The Memos attachment resource name in the format attachments/{attachment}.
delete_memo
nameREQUIRED- The Memos memo resource name in the format memos/{memo}.
forceOPTIONAL- Whether to force deletion when the memo has associated data.
PROVIDER-SPECIFIC WORKFLOWS
Jobs this Agent App can support
Inspect Get Attachment
Retrieve one attachment's metadata by resource name. Use this as a bounded discovery step, retain the returned identifier, and avoid expanding the read beyond the task's stated scope.
get_attachmentControl Create Memo
Create a Markdown memo on the connected Memos instance. Resolve the target first, present material changes for confirmation, and make retries idempotent where the provider supports it.
create_memoVerify with Get Current User
Retrieve the Memos user associated with the connected personal access token. Compare the returned provider state with the intended outcome and preserve stable IDs or canonical links in the run record.
get_current_userSAFETY BOUNDARY
Operate Memos with explicit limits
- Authorize Memos with API key and grant only the provider access required by the selected actions.
- 6 actions are change-capable by name. Confirm the target identity and material parameters before allowing a write.
- Treat `delete_attachment` and `delete_memo` as high-impact operations and require an explicit approval boundary.
- No provider scope string is declared on the sampled actions. Verify the connected account's actual permissions in Memos rather than assuming unrestricted access.
- After a call, inspect the structured result and execution record before reporting that the Memos task completed successfully.
CONNECTION MODEL
API key
Memos personal access token sent as a Bearer credential. Create one in account settings.
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
- 8
- WRITE SIGNALS
- 4
- HIGH IMPACT
- 2
- REVIEW SIGNALS
- 0
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 Memos.