RiteKit MCP integration for AI agents.
Connect AI agents to RiteKit through 7 structured actions, including get hashtag stats, auto hashtag, and clean banned instagram hashtags. Review authenticat…
- ACTION CONTRACTS
- 7
- 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 RiteKit integration exposes
The RiteKit Agent App exposes 7 provider-backed actions for social and marketing work. Its current contract lets an authorized agent get current engagement statistics for one or more hashtags, add relevant hashtags to social post text with ritekit, and remove hashtags that ritekit identifies as currently blocked by instagram. 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 RiteKit account, granted provider permissions, workspace policy, region, plan, and upstream API behavior.
VERIFIED ACTION SAMPLE
Real RiteKit capabilities.
Showing 7 of 7 actions. Risk labels are conservative signals based on operation names, not substitutes for provider documentation or runtime policy.
get_hashtag_statsREADGet current engagement statistics for one or more hashtags.
INPUTS: tags
auto_hashtagREVIEWAdd relevant hashtags to social post text with RiteKit.
INPUTS: post / maxHashtags / hashtagPosition
clean_banned_instagram_hashtagsREVIEWRemove hashtags that RiteKit identifies as currently blocked by Instagram.
INPUTS: post
list_trending_hashtagsREADList hashtags that are currently trending according to RiteKit.
INPUTS: green / latin
suggest_hashtags_for_imageREVIEWGenerate engagement-ranked hashtag suggestions from a public image URL.
INPUTS: imageUrl
suggest_hashtags_for_textREVIEWGenerate engagement-ranked hashtag suggestions from text.
INPUTS: text
suggest_hashtags_for_urlREVIEWGenerate engagement-ranked hashtag suggestions from a public webpage URL.
INPUTS: pageUrl
INPUT CONTRACTS
Know what the action needs before it runs.
get_hashtag_stats
tagsREQUIRED- The hashtag names to analyze.
auto_hashtag
postREQUIRED- The social post text to enhance with relevant hashtags.
maxHashtagsOPTIONAL- The maximum number of hashtags RiteKit should add.
hashtagPositionOPTIONAL- Where RiteKit should place generated hashtags.
clean_banned_instagram_hashtags
postREQUIRED- The Instagram post text whose hashtags should be checked.
list_trending_hashtags
greenOPTIONAL- Whether to limit results to hashtags with RiteKit's green rating.
latinOPTIONAL- Whether to limit results to hashtags written with Latin characters.
PROVIDER-SPECIFIC WORKFLOWS
Jobs this Agent App can support
Inspect Get Hashtag Stats
Get current engagement statistics for one or more hashtags. Use this as a bounded discovery step, retain the returned identifier, and avoid expanding the read beyond the task's stated scope.
get_hashtag_statsVerify with List Trending Hashtags
List hashtags that are currently trending according to RiteKit. Compare the returned provider state with the intended outcome and preserve stable IDs or canonical links in the run record.
list_trending_hashtagsSAFETY BOUNDARY
Operate RiteKit with explicit limits
- Authorize RiteKit with API key and grant only the provider access required by the selected actions.
- The current action names appear read-oriented, but returned RiteKit 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 RiteKit rather than assuming unrestricted access.
- After a call, inspect the structured result and execution record before reporting that the RiteKit task completed successfully.
CONNECTION MODEL
API key
RiteKit Client ID sent as the client_id query parameter. Create or view it in the official RiteKit API Console: https://ritekit.com/developer/dashboard/
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
- 2
- WRITE SIGNALS
- 0
- HIGH IMPACT
- 0
- REVIEW SIGNALS
- 5
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 RiteKit.