Starton MCP integration for AI agents.
Connect AI agents to Starton through 5 structured actions, including get pin, create json pin, delete pin, and pin existing file. Review authentication, inpu…
- ACTION CONTRACTS
- 5
- 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 Starton integration exposes
The Starton Agent App exposes 5 provider-backed actions for storage and developer tools work. Its current contract lets an authorized agent read one ipfs pin from starton by pin identifier, upload json content to starton ipfs and create a new pin, and delete a starton pin by pin identifier. 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 Starton account, granted provider permissions, workspace policy, region, plan, and upstream API behavior.
VERIFIED ACTION SAMPLE
Real Starton capabilities.
Showing 5 of 5 actions. Risk labels are conservative signals based on operation names, not substitutes for provider documentation or runtime policy.
get_pinREADRead one IPFS pin from Starton by pin identifier.
INPUTS: id / includeDirectoryContent
create_json_pinWRITEUpload JSON content to Starton IPFS and create a new pin.
INPUTS: name / content / metadata
delete_pinHIGH IMPACTDelete a Starton pin by pin identifier.
INPUTS: id
pin_existing_fileREVIEWCreate a Starton pin for an existing IPFS CID.
INPUTS: cid / name / metadata
list_pinsREADList IPFS pins from the current Starton project.
INPUTS: cid / includeDirectoryContent / limit / name / page
INPUT CONTRACTS
Know what the action needs before it runs.
get_pin
idREQUIRED- The unique Starton pin identifier.
includeDirectoryContentOPTIONAL- Whether Starton should include nested directory content in the response.
create_json_pin
nameREQUIRED- The name recorded for the uploaded JSON file.
contentREQUIRED- The JSON content that Starton should upload.
metadataOPTIONAL- Optional metadata stored alongside the uploaded JSON file.
delete_pin
idREQUIRED- The unique Starton pin identifier.
pin_existing_file
cidREQUIRED- The existing IPFS CID that Starton should pin.
nameOPTIONAL- An optional display name recorded for the new pin.
metadataOPTIONAL- Optional metadata stored alongside the new pin.
PROVIDER-SPECIFIC WORKFLOWS
Jobs this Agent App can support
Inspect Get Pin
Read one IPFS pin from Starton by pin identifier. Use this as a bounded discovery step, retain the returned identifier, and avoid expanding the read beyond the task's stated scope.
get_pinControl Create Json Pin
Upload JSON content to Starton IPFS and create a new pin. Resolve the target first, present material changes for confirmation, and make retries idempotent where the provider supports it.
create_json_pinVerify with List Pins
List IPFS pins from the current Starton project. Compare the returned provider state with the intended outcome and preserve stable IDs or canonical links in the run record.
list_pinsSAFETY BOUNDARY
Operate Starton with explicit limits
- Authorize Starton with API key and grant only the provider access required by the selected actions.
- 2 actions are change-capable by name. Confirm the target identity and material parameters before allowing a write.
- Treat `delete_pin` 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 Starton rather than assuming unrestricted access.
- After a call, inspect the structured result and execution record before reporting that the Starton task completed successfully.
CONNECTION MODEL
API key
Starton API key sent with the x-api-key header. Create it in Starton project developer settings: https://app.starton.com/projects/default/developer.
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
- 1
- HIGH IMPACT
- 1
- REVIEW SIGNALS
- 1
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 Starton.