Viggle MCP integration for AI agents.
Connect AI agents to Viggle through 11 structured actions, including get character, create character, and delete character. Review authentication, inputs, wo…
- ACTION CONTRACTS
- 11
- 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 Viggle integration exposes
The Viggle Agent App exposes 11 provider-backed actions for ai and design & media work. Its current contract lets an authorized agent get a viggle character by id, including preprocessing status, create a reusable viggle character from a publicly accessible image url and return the preprocessing handle, and soft-delete a viggle character 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 Viggle account, granted provider permissions, workspace policy, region, plan, and upstream API behavior.
VERIFIED ACTION SAMPLE
Real Viggle capabilities.
Showing 11 of 11 actions. Risk labels are conservative signals based on operation names, not substitutes for provider documentation or runtime policy.
get_characterREADGet a Viggle character by ID, including preprocessing status.
INPUTS: character_id
create_characterWRITECreate a reusable Viggle character from a publicly accessible image URL and return the preprocessing handle.
INPUTS: name / image_url / model
delete_characterHIGH IMPACTSoft-delete a Viggle character by ID.
INPUTS: character_id
create_render_jobWRITECreate a Viggle render job from URL inputs or preprocessed character and scene IDs.
INPUTS: ref_image_url / driving_video_url / character_id / scene_id / model
delete_sceneHIGH IMPACTSoft-delete a Viggle scene by ID.
INPUTS: scene_id
get_credit_balanceREADGet the current Viggle credit balance for the authenticated account.
get_render_job_statusREADGet a Viggle render job status and return the video URL when rendering is complete.
INPUTS: job_id
get_sceneREADGet a Viggle scene by ID, including preprocessing status.
INPUTS: scene_id
import_templateWRITEImport a Viggle template as a reusable scene.
INPUTS: template_uuid / name
list_charactersREADList Viggle characters for the authenticated account.
INPUTS: limit / offset
list_scenesREADList Viggle scenes for the authenticated account.
INPUTS: limit / offset
INPUT CONTRACTS
Know what the action needs before it runs.
get_character
character_idOPTIONAL- The character identifier returned by Viggle.
create_character
nameREQUIRED- The display name for the character.
image_urlREQUIRED- The publicly accessible character image URL.
modelOPTIONAL- The Viggle model to use for preprocessing or rendering.
delete_character
character_idOPTIONAL- The character identifier to delete.
create_render_job
ref_image_urlOPTIONAL- The public character image URL for on-demand rendering.
driving_video_urlOPTIONAL- The public driving video URL for on-demand rendering.
character_idOPTIONAL- The ready character ID for preprocessed rendering.
scene_idOPTIONAL- The ready scene ID for preprocessed rendering.
modelOPTIONAL- The Viggle model to use for preprocessing or rendering.
PROVIDER-SPECIFIC WORKFLOWS
Jobs this Agent App can support
Inspect Get Character
Get a Viggle character by ID, including preprocessing status. Use this as a bounded discovery step, retain the returned identifier, and avoid expanding the read beyond the task's stated scope.
get_characterControl Create Character
Create a reusable Viggle character from a publicly accessible image URL and return the preprocessing handle. Resolve the target first, present material changes for confirmation, and make retries idempotent where the provider supports it.
create_characterVerify with Get Credit Balance
Get the current Viggle credit balance for the authenticated account. Compare the returned provider state with the intended outcome and preserve stable IDs or canonical links in the run record.
get_credit_balanceSAFETY BOUNDARY
Operate Viggle with explicit limits
- Authorize Viggle with API key and grant only the provider access required by the selected actions.
- 5 actions are change-capable by name. Confirm the target identity and material parameters before allowing a write.
- Treat `delete_character` and `delete_scene` 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 Viggle rather than assuming unrestricted access.
- After a call, inspect the structured result and execution record before reporting that the Viggle task completed successfully.
CONNECTION MODEL
API key
Viggle API key sent as a Bearer token. Create or manage keys in the Viggle Dashboard API Keys page: https://portal.viggle.ai/api-keys.
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
- 6
- WRITE SIGNALS
- 3
- 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 Viggle.