JSONBin.io MCP integration for AI agents.
Connect AI agents to JSONBin.io through 4 structured actions, including read bin, create bin, and delete bin. Review authentication, inputs, workflows, and s…
- ACTION CONTRACTS
- 4
- 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 JSONBin.io integration exposes
The JSONBin.io Agent App exposes 4 provider-backed actions for storage and developer tools work. Its current contract lets an authorized agent read the latest or a specific version of a jsonbin bin, create a jsonbin bin from a json object and return the stored record plus bin metadata, and delete a jsonbin bin and return the deletion metadata returned by jsonbin. 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 JSONBin.io account, granted provider permissions, workspace policy, region, plan, and upstream API behavior.
VERIFIED ACTION SAMPLE
Real JSONBin.io capabilities.
Showing 4 of 4 actions. Risk labels are conservative signals based on operation names, not substitutes for provider documentation or runtime policy.
read_binREADRead the latest or a specific version of a JSONBin bin.
INPUTS: binId / version
create_binWRITECreate a JSONBin bin from a JSON object and return the stored record plus bin metadata.
INPUTS: record / name / collectionId / private
delete_binHIGH IMPACTDelete a JSONBin bin and return the deletion metadata returned by JSONBin.
INPUTS: binId
update_binWRITEReplace the JSON object stored in a JSONBin bin and return the updated record plus bin metadata.
INPUTS: binId / record / versioning
INPUT CONTRACTS
Know what the action needs before it runs.
read_bin
binIdREQUIRED- The JSONBin bin identifier.
versionOPTIONAL- Optional JSONBin version identifier to read.
create_bin
recordREQUIRED- The JSON object stored in the bin. JSONBin bins store object records.
nameOPTIONAL- Optional bin name sent with the X-Bin-Name header.
collectionIdOPTIONAL- Optional collection id sent with the X-Collection-Id header.
privateOPTIONAL- Whether the bin should be private.
delete_bin
binIdOPTIONAL- The JSONBin bin identifier.
update_bin
binIdREQUIRED- The JSONBin bin identifier.
recordREQUIRED- The JSON object stored in the bin. JSONBin bins store object records.
versioningOPTIONAL- Whether JSONBin should create a new version for this update.
PROVIDER-SPECIFIC WORKFLOWS
Jobs this Agent App can support
Inspect Read Bin
Read the latest or a specific version of a JSONBin bin. Use this as a bounded discovery step, retain the returned identifier, and avoid expanding the read beyond the task's stated scope.
read_binControl Create Bin
Create a JSONBin bin from a JSON object and return the stored record plus bin metadata. Resolve the target first, present material changes for confirmation, and make retries idempotent where the provider supports it.
create_binVerify with Create Bin
Create a JSONBin bin from a JSON object and return the stored record plus bin metadata. Compare the returned provider state with the intended outcome and preserve stable IDs or canonical links in the run record.
create_binSAFETY BOUNDARY
Operate JSONBin.io with explicit limits
- Authorize JSONBin.io 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_bin` 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 JSONBin.io rather than assuming unrestricted access.
- After a call, inspect the structured result and execution record before reporting that the JSONBin.io task completed successfully.
CONNECTION MODEL
API key
JSONBin.io master key sent with the X-Master-Key header. Open your JSONBin API Keys page to view or create keys: https://jsonbin.io/app/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
- 1
- 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 JSONBin.io.