Ordinal MCP integration for AI agents.
Connect AI agents to Ordinal through 9 structured actions, including get idea, get post, and get workspace. Review authentication, inputs, workflows, and saf…
- ACTION CONTRACTS
- 9
- 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 Ordinal integration exposes
The Ordinal Agent App exposes 9 provider-backed actions for social and marketing work. Its current contract lets an authorized agent get a specific ordinal idea by id, get a specific ordinal post by id, and get details about the current ordinal workspace. 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 Ordinal account, granted provider permissions, workspace policy, region, plan, and upstream API behavior.
VERIFIED ACTION SAMPLE
Real Ordinal capabilities.
Showing 9 of 9 actions. Risk labels are conservative signals based on operation names, not substitutes for provider documentation or runtime policy.
get_ideaREADGet a specific Ordinal idea by ID.
INPUTS: id
get_postREADGet a specific Ordinal post by ID.
INPUTS: id
get_workspaceREADGet details about the current Ordinal workspace.
list_engagement_profilesREADList Ordinal engagement-only profiles connected to the workspace.
list_ideasREADList Ordinal ideas with pagination and optional filters.
INPUTS: limit / cursor / ids / channel / linkedInProfileId
list_labelsREADList labels in the current Ordinal workspace.
list_postsREADList Ordinal posts with pagination and optional filters.
INPUTS: limit / cursor / ids / status / channel
list_scheduling_profilesREADList Ordinal scheduling profiles connected to the workspace.
list_usersREADList users in the current Ordinal workspace.
INPUT CONTRACTS
Know what the action needs before it runs.
get_idea
idREQUIRED- The Ordinal idea ID.
get_post
idREQUIRED- The Ordinal post ID.
list_ideas
limitOPTIONAL- The maximum number of items to return, from 1 to 100.
cursorOPTIONAL- The pagination cursor from the previous Ordinal page.
idsOPTIONAL- One or more Ordinal UUIDs.
channelOPTIONAL- The social channel to filter ideas by.
linkedInProfileIdOPTIONAL- Filter ideas by LinkedIn profile ID.
list_posts
limitOPTIONAL- The maximum number of items to return, from 1 to 100.
cursorOPTIONAL- The pagination cursor from the previous Ordinal page.
idsOPTIONAL- One or more Ordinal UUIDs.
statusOPTIONAL- The Ordinal post status.
channelOPTIONAL- The social channel to filter posts by.
PROVIDER-SPECIFIC WORKFLOWS
Jobs this Agent App can support
Inspect Get Idea
Get a specific Ordinal idea by ID. Use this as a bounded discovery step, retain the returned identifier, and avoid expanding the read beyond the task's stated scope.
get_ideaVerify with Get Post
Get a specific Ordinal post by ID. Compare the returned provider state with the intended outcome and preserve stable IDs or canonical links in the run record.
get_postSAFETY BOUNDARY
Operate Ordinal with explicit limits
- Authorize Ordinal with API key and grant only the provider access required by the selected actions.
- The current action names appear read-oriented, but returned Ordinal 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 Ordinal rather than assuming unrestricted access.
- After a call, inspect the structured result and execution record before reporting that the Ordinal task completed successfully.
CONNECTION MODEL
API key
Ordinal workspace API key used with the Authorization Bearer header. Create one from the API Keys page in workspace settings: https://app.tryordinal.com/settings/integrations/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
- 9
- WRITE SIGNALS
- 0
- HIGH IMPACT
- 0
- 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 Ordinal.