Add apideck-mcp + 4 workflow playbooks#3
Merged
Conversation
Phase 4 distribution work: skills layer paired with the Apideck MCP
server (github.com/apideck-libraries/mcp).
The MCP server is the *agent-tool* layer — 330 unified-API tools + 4
intent-grouped workflows exposed via dynamic discovery. These skills are
the *agent-instruction* layer: the agent reads them before tool selection
so by the time it's choosing tools it already knows the routing rules,
the confirmation conventions, and the connector quirks.
New skills:
apideck-mcp — front-door: hosted vs stdio,
dynamic mode, scopes, Vault OAuth
elicitations, when to prefer over
a language SDK
apideck-mcp-pay-bill — playbook for the AP workflow.
Confirmation prompts, partial
payments, QB capitalisation,
AR-vs-AP routing
apideck-mcp-receive-payment — AR mirror of pay-bill
apideck-mcp-onboard-employee — cross-API (ATS + HRIS) playbook,
soft-fail semantics on optional
stage move, two-service-id headers
apideck-mcp-month-end-close — read-only fan-out playbook,
partial-result envelope, when
`unsupported` is acceptable
Cross-references:
- apideck-unified-api/SKILL.md — added "use apideck-mcp for
agent-driven integrations" pointer
- README.md — added MCP install line; added 5 rows to the
apideck-* skills table; bumped count 13 → 18
Each playbook covers: when to pick the workflow over manual chains,
mutation/idempotency rules, argument map, success/failure result
envelope (incl. `failingStep` semantics), worked example, common
failure modes, links back to the workflow source.
Connector-quirk content (e.g. QuickBooks requires capitalised
`payment_method`, Moneybird models customer payments as
`financial_mutations`) was learned from running each workflow live
against the sandbox. Putting it in skill markdown means agents avoid
those gotchas on the first call.
Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
Merged
9 tasks
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Phase 4 distribution work for
apideck-libraries/mcp. Adds the skills layer that pairs with the MCP server.Two layers, one product
apideck-libraries/mcpMCP descriptions tell the agent what a tool does. Skills tell the agent when to pick which one — and how to handle the connector-specific gotchas we learned the hard way (QuickBooks capitalization, Moneybird's
financial_mutationscoverage gap, AR/AP endpoint routing, partial-result envelopes).What's added
```
skills/
├── apideck-mcp/ # NEW front-door
├── apideck-mcp-pay-bill/ # NEW playbook
├── apideck-mcp-receive-payment/ # NEW playbook
├── apideck-mcp-onboard-employee/ # NEW playbook (cross-API: ATS + HRIS)
└── apideck-mcp-month-end-close/ # NEW playbook (read fan-out)
```
Plus pointer from `apideck-unified-api/SKILL.md` → `apideck-mcp` for agent-driven integrations, and an `apideck-mcp` install line in the README.
Each playbook covers
Test plan
🤖 Generated with Claude Code