BidSketch MCP integration for AI agents.
Connect AI agents to BidSketch through 6 structured actions, including get client, get proposal, and get proposal content. Review authentication, inputs, wor…
- 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 BidSketch integration exposes
The BidSketch Agent App exposes 6 provider-backed actions for productivity and marketing work. Its current contract lets an authorized agent get one bidsketch client by client id, get one bidsketch proposal by proposal id, and get one bidsketch proposal with its grouped sections and fees. 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 BidSketch account, granted provider permissions, workspace policy, region, plan, and upstream API behavior.
VERIFIED ACTION SAMPLE
Real BidSketch capabilities.
Showing 6 of 6 actions. Risk labels are conservative signals based on operation names, not substitutes for provider documentation or runtime policy.
get_clientREADGet one BidSketch client by client ID.
INPUTS: clientId
get_proposalREADGet one BidSketch proposal by proposal ID.
INPUTS: proposalId
get_proposal_contentREADGet one BidSketch proposal with its grouped sections and fees.
INPUTS: proposalId
list_client_proposalsREADList proposals that belong to one BidSketch client.
INPUTS: clientId / page / perPage
list_clientsREADList clients available in the authenticated BidSketch account.
INPUTS: page / perPage
list_proposalsREADList proposals available in the authenticated BidSketch account.
INPUTS: page / perPage
INPUT CONTRACTS
Know what the action needs before it runs.
get_client
clientIdOPTIONAL- The BidSketch client ID.
get_proposal
proposalIdOPTIONAL- The BidSketch proposal ID.
get_proposal_content
proposalIdOPTIONAL- The BidSketch proposal ID.
list_client_proposals
clientIdREQUIRED- The BidSketch client ID.
pageOPTIONAL- The 1-based page number to request from BidSketch.
perPageOPTIONAL- The maximum number of records to request per page.
PROVIDER-SPECIFIC WORKFLOWS
Jobs this Agent App can support
Inspect Get Client
Get one BidSketch client by client ID. Use this as a bounded discovery step, retain the returned identifier, and avoid expanding the read beyond the task's stated scope.
get_clientVerify with Get Proposal
Get one BidSketch proposal by proposal ID. Compare the returned provider state with the intended outcome and preserve stable IDs or canonical links in the run record.
get_proposalSAFETY BOUNDARY
Operate BidSketch with explicit limits
- Authorize BidSketch with API key and grant only the provider access required by the selected actions.
- The current action names appear read-oriented, but returned BidSketch 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 BidSketch rather than assuming unrestricted access.
- After a call, inspect the structured result and execution record before reporting that the BidSketch task completed successfully.
CONNECTION MODEL
API key
BidSketch API token used with the Authorization header. Admin users can create and view it at your workspace /account/api_tokens page, as described in the official API help article: https://help.bidsketch.com/article/76-using-the-bidsketch-api
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
- 0
- HIGH IMPACT
- 0
- 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 BidSketch.