MCP Tool Catalog
The complete MCP tool catalog: 138 tools across 10 toolsets, plus 11 apiant-docs tools. Core tools carry a DEV/PROD toggle.
Tools are organized by workflow. All 138 platform tools are available from session start — toolsets group them by purpose for navigation. Skills call ToolSearch to load schemas for the specific tools they need.
Skills drive the workflow. MCP tools do the actual work against APIANT's dev, prod, and docs environments. Tools are grouped into toolsets by purpose. Prod and dev share the same 138-tool surface; prod is read-only by default and writes gate on explicit confirmation. Toggle any Core card below to see the prod-side description.
Load, list, create, update, rename, and delete assemblies. The low-level assembly API.
Structured overview of an automation: triggers, steps, mappings. Fast context for edits.
Flat list of every automation in a scope. Filter by name, folder, or status.
Navigate the folder tree. Find automations grouped by customer, product, or environment.
Create, rename, duplicate, move, enable, disable. Every CRUD operation for automations.
The full catalog of available app integrations. Filter by category, vendor, or capability.
30 tools. Search the catalog, compose triggers and actions, edit mappings, commit versions, save patterns. The full automation authoring surface.
17 tools. Run test executions, inspect every step's input and output, mutate data, replay webhooks, walk branch-coverage test points. Debugging with full ground truth.
10 tools. List and organize committed automations, version them, compare versions, roll back. The git-like layer over automation drafts and releases.
22 tools. Switch between customer accounts, query usage and health across a tenant, read the keyvault, run ad-hoc SQL, tune retryable errors, manage lookups, snapshot + disable + restore parent-child account groups during incidents. The operator's toolbox.
5 tools. Tenant-wide alert rules, suppressed-alert lists, retry policy, 401 domain carve-outs. Requires Switch Account context.
11 tools. Per-automation alert mapping rules, step-level alert triggers, mapping trace, suppression, system-level mappings.
3 tools. Search, save, and delete reusable pattern recipes: field mappings, transforms, gotchas, templates.
6 tools. Publish folders or individual assemblies from dev to prod. Roll changes out to customer accounts in a single coordinated step.
28 tools. Create connectors, inject settings, compile JSP, test API endpoints, configure dynamic field discovery, finalize assemblies. The low-level integration plumbing.
1 tool. File structured MCP-layer bug reports back to APIANT's internal triage. The model calls report_mcp_issue when it observes an MCP tool misbehaving; tickets land in APIANT's Jira with identity context attached. Available from session start so the bug-detection moment is never gated.
Programmatic access. Issue a docs API key for CI/CD or automated publishing.
Retrieval-augmented Q&A. Claude asks the docs corpus before writing code or answering.
Publish a new doc. Title, body, parent, tags, and status, in one call.
Browse the full table of contents. Filter by section, tag, or status.
Authenticate the docs session. Tokens cached for the session.
Fetch the full contents of any doc. Markdown, images, and metadata included.
Take a live screenshot of the editor or platform UI and embed it into a doc.
Semantic + keyword search across the entire docs corpus. Ranked results with context.
Edit title, body, tags, or status. Revisions tracked automatically.
Attach an illustration or diagram to any page. Auto-alt-text generated.
List revisions, diff between versions, roll back if needed.