External Connections And MCP Integrations
Connect Staffless agents to APIs and MCP servers, configure credentials, and verify tools are available at runtime.
Connection Types
Staffless supports both API-style connections and MCP-style tool connections. API connections manage credentials and endpoint use; MCP connections expose tool interfaces to the runtime.
Choose the minimal set of connections needed for each workspace to reduce complexity and failure points.
Validate After Connecting
After enabling a connection, run one targeted test call. Confirm the tool is discoverable and that auth works in the active workspace context.
If a tool is visible but failing, check token scope, project permissions, and key freshness before changing skill logic.
Operate Integrations Like Production Systems
Integrations are infrastructure. Track owner, purpose, and last verified date for each critical connection.
- Avoid duplicate integrations per workspace.
- Disable unused connectors to reduce noise.
- Re-test after key rotation or provider-side permission changes.
FAQ
Do cron jobs have access to connections and MCP tools?
Yes, if the integration is enabled and valid in that workspace. Manual and scheduled runs share the same workspace integration context.
Why does a tool work in chat but fail in scheduled runs?
Usually due to missing delivery routing, missing skill pinning, or stale credentials. Validate channel settings and key state for the scheduled task.