Deck.co MCP integration for AI agents.
Connect AI agents to Deck.co through 6 structured actions, including get agent, create source, and test api key. Review authentication, inputs, workflows, an…
- ACTION CONTRACTS
- 6
- 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 Deck.co integration exposes
The Deck.co Agent App exposes 6 provider-backed actions for ai and developer tools work. Its current contract lets an authorized agent retrieve a deck.co agent by id, including its task summaries, create a deck.co website source from a url and optional display name, and verify that a deck.co secret key can authenticate with the v2 api. 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 Deck.co account, granted provider permissions, workspace policy, region, plan, and upstream API behavior.
VERIFIED ACTION SAMPLE
Real Deck.co capabilities.
Showing 6 of 6 actions. Risk labels are conservative signals based on operation names, not substitutes for provider documentation or runtime policy.
get_agentREADRetrieve a Deck.co agent by ID, including its task summaries.
INPUTS: agent_id
create_sourceWRITECreate a Deck.co website source from a URL and optional display name.
INPUTS: website_url / name / idempotencyKey
test_api_keyREVIEWVerify that a Deck.co secret key can authenticate with the v2 API.
get_sourceREADRetrieve a Deck.co source by ID.
INPUTS: source_id
list_agentsREADList Deck.co agents with cursor pagination.
INPUTS: limit / cursor
list_sourcesREADList Deck.co sources with cursor pagination.
INPUTS: limit / cursor
INPUT CONTRACTS
Know what the action needs before it runs.
get_agent
agent_idOPTIONAL- Unique identifier for the agent, prefixed with agt_.
create_source
website_urlREQUIRED- The website or service URL to register as a Deck.co source.
nameOPTIONAL- Display name for the source.
idempotencyKeyOPTIONAL- An optional Idempotency-Key header value for safe retries.
get_source
source_idOPTIONAL- Unique identifier for the source, prefixed with src_.
list_agents
limitOPTIONAL- Maximum number of items to return. Deck.co allows 1 to 100.
cursorOPTIONAL- Opaque cursor string returned by a previous Deck.co page.
PROVIDER-SPECIFIC WORKFLOWS
Jobs this Agent App can support
Inspect Get Agent
Retrieve a Deck.co agent by ID, including its task summaries. Use this as a bounded discovery step, retain the returned identifier, and avoid expanding the read beyond the task's stated scope.
get_agentControl Create Source
Create a Deck.co website source from a URL and optional display name. Resolve the target first, present material changes for confirmation, and make retries idempotent where the provider supports it.
create_sourceVerify with Get Source
Retrieve a Deck.co source by ID. Compare the returned provider state with the intended outcome and preserve stable IDs or canonical links in the run record.
get_sourceSAFETY BOUNDARY
Operate Deck.co with explicit limits
- Authorize Deck.co with API key and grant only the provider access required by the selected actions.
- 1 action is change-capable by name. Confirm the target identity and material parameters before allowing a write.
- 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 Deck.co rather than assuming unrestricted access.
- After a call, inspect the structured result and execution record before reporting that the Deck.co task completed successfully.
CONNECTION MODEL
API key
Deck.co v2 secret key sent as a Bearer token. Create or view API keys from the Deck.co dashboard API keys page: https://app.deck.co/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
- 4
- WRITE SIGNALS
- 1
- HIGH IMPACT
- 0
- 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 Deck.co.