Getnote MCP integration for AI agents.
Connect AI agents to Getnote through 23 structured actions, including get blogger content, add note tags, delete note, and follow live. Review authentication…
- ACTION CONTRACTS
- 23
- 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 Getnote integration exposes
The Getnote Agent App exposes 23 provider-backed actions for ai and productivity work. Its current contract lets an authorized agent get one getnote blogger content detail, including original text when returned, add one or more tags to a getnote note, and move a getnote note to trash. 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 Getnote account, granted provider permissions, workspace policy, region, plan, and upstream API behavior.
VERIFIED ACTION SAMPLE
Real Getnote capabilities.
Showing 12 of 23 actions. Risk labels are conservative signals based on operation names, not substitutes for provider documentation or runtime policy.
get_blogger_contentREADGet one Getnote blogger content detail, including original text when returned.
INPUTS: topicId / postId
add_note_tagsWRITEAdd one or more tags to a Getnote note.
INPUTS: noteId / tags
delete_noteHIGH IMPACTMove a Getnote note to trash.
INPUTS: noteId
follow_liveREVIEWSubscribe a Dedao live channel link into one Getnote knowledge base. Upstream currently supports Dedao App live links.
INPUTS: topicId / link / platform
add_notes_to_knowledge_baseWRITEAdd up to 20 notes to one Getnote knowledge base. Subscribed knowledge bases are read-only unless the user is an admin.
INPUTS: topicId / noteIds
create_knowledge_baseWRITECreate a Getnote knowledge base. Upstream limits creation to 50 per day.
INPUTS: name / description
get_live_detailREADGet one Getnote live detail, including AI summary and transcript when returned.
INPUTS: topicId / liveId
get_noteREADGet one Getnote note detail, including fields that are not present in lists.
INPUTS: noteId / imageQuality
get_save_taskREADCheck the progress of an asynchronous Getnote link or image save task.
INPUTS: taskId
list_blogger_contentsREADList content items for a subscribed blogger in a Getnote knowledge base.
INPUTS: topicId / followId / page
list_knowledge_base_bloggersREADList bloggers subscribed in one Getnote knowledge base.
INPUTS: topicId / page
list_knowledge_base_livesREADList completed live sessions in one Getnote knowledge base.
INPUTS: topicId / page
INPUT CONTRACTS
Know what the action needs before it runs.
get_blogger_content
topicIdOPTIONAL- Getnote knowledge base topic ID.
postIdOPTIONAL- Blogger post ID alias returned by list_blogger_contents.
add_note_tags
noteIdOPTIONAL- Getnote note ID. Treat this as a string because upstream IDs are int64.
tagsOPTIONAL- Tag names to add.
delete_note
noteIdOPTIONAL- Getnote note ID. Treat this as a string because upstream IDs are int64.
follow_live
topicIdREQUIRED- Getnote knowledge base topic ID.
linkREQUIRED- Dedao live link to subscribe.
platformOPTIONAL- Optional upstream platform value.
PROVIDER-SPECIFIC WORKFLOWS
Jobs this Agent App can support
Inspect Get Blogger Content
Get one Getnote blogger content detail, including original text when returned. Use this as a bounded discovery step, retain the returned identifier, and avoid expanding the read beyond the task's stated scope.
get_blogger_contentControl Add Note Tags
Add one or more tags to a Getnote note. Resolve the target first, present material changes for confirmation, and make retries idempotent where the provider supports it.
add_note_tagsVerify with Get Live Detail
Get one Getnote live detail, including AI summary and transcript when returned. Compare the returned provider state with the intended outcome and preserve stable IDs or canonical links in the run record.
get_live_detailSAFETY BOUNDARY
Operate Getnote with explicit limits
- Authorize Getnote with API key and grant only the provider access required by the selected actions.
- 7 actions are change-capable by name. Confirm the target identity and material parameters before allowing a write.
- Treat `delete_note`, `remove_note_tag`, and `remove_notes_from_knowledge_base` 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 Getnote rather than assuming unrestricted access.
- After a call, inspect the structured result and execution record before reporting that the Getnote task completed successfully.
CONNECTION MODEL
API key
Getnote API key sent with the Authorization header. Create an app in the official open platform: https://www.biji.com/openapi.
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
- 13
- WRITE SIGNALS
- 4
- HIGH IMPACT
- 3
- REVIEW SIGNALS
- 3
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 Getnote.