Typefully MCP integration for AI agents.
Connect AI agents to Typefully through 8 structured actions, including get current user, create draft, and delete draft. Review authentication, inputs, workf…
- ACTION CONTRACTS
- 8
- 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 Typefully integration exposes
The Typefully Agent App exposes 8 provider-backed actions for social and marketing work. Its current contract lets an authorized agent retrieve the typefully user associated with the current api key, create a typefully draft for a social set, and delete a typefully draft by id. 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 Typefully account, granted provider permissions, workspace policy, region, plan, and upstream API behavior.
VERIFIED ACTION SAMPLE
Real Typefully capabilities.
Showing 8 of 8 actions. Risk labels are conservative signals based on operation names, not substitutes for provider documentation or runtime policy.
get_current_userREADRetrieve the Typefully user associated with the current API key.
create_draftWRITECreate a Typefully draft for a social set.
INPUTS: social_set_id / body
delete_draftHIGH IMPACTDelete a Typefully draft by ID.
INPUTS: social_set_id / draft_id
get_draftREADRetrieve a Typefully draft by ID.
INPUTS: social_set_id / draft_id / exclude_comment_markers
get_social_setREADRetrieve details for a Typefully social set.
INPUTS: social_set_id
list_draftsREADList Typefully drafts for a social set with optional filters.
INPUTS: social_set_id / limit / offset / status / platform
list_social_setsREADList Typefully social sets available to the current API key.
INPUTS: limit / offset
update_draftWRITEUpdate a Typefully draft by ID.
INPUTS: social_set_id / draft_id / body / exclude_comment_markers
INPUT CONTRACTS
Know what the action needs before it runs.
create_draft
social_set_idOPTIONAL- The Typefully social set ID.
bodyOPTIONAL- Request body for creating a Typefully draft.
delete_draft
social_set_idOPTIONAL- The Typefully social set ID.
draft_idOPTIONAL- The Typefully draft ID.
get_draft
social_set_idREQUIRED- The Typefully social set ID.
draft_idREQUIRED- The Typefully draft ID.
exclude_comment_markersOPTIONAL- Whether returned draft text should omit Typefully comment-thread markers.
get_social_set
social_set_idOPTIONAL- The Typefully social set ID.
PROVIDER-SPECIFIC WORKFLOWS
Jobs this Agent App can support
Inspect Get Current User
Retrieve the Typefully user associated with the current API key. Use this as a bounded discovery step, retain the returned identifier, and avoid expanding the read beyond the task's stated scope.
get_current_userControl Create Draft
Create a Typefully draft for a social set. Resolve the target first, present material changes for confirmation, and make retries idempotent where the provider supports it.
create_draftVerify with Get Draft
Retrieve a Typefully draft by ID. Compare the returned provider state with the intended outcome and preserve stable IDs or canonical links in the run record.
get_draftSAFETY BOUNDARY
Operate Typefully with explicit limits
- Authorize Typefully with API key and grant only the provider access required by the selected actions.
- 3 actions are change-capable by name. Confirm the target identity and material parameters before allowing a write.
- Treat `delete_draft` 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 Typefully rather than assuming unrestricted access.
- After a call, inspect the structured result and execution record before reporting that the Typefully task completed successfully.
CONNECTION MODEL
API key
Typefully API key used with the Authorization Bearer header. Generate it from your Typefully settings: https://typefully.com/docs/api
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
- 5
- WRITE SIGNALS
- 2
- HIGH IMPACT
- 1
- 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 Typefully.