Book a demo

Tell us about your use case. We will walk through composing a workflow, deploying to AWS Bedrock AgentCore, and invoking it from your product.

Tools

Agent tool catalog in Floprints — built-in AgentCore tools, remote MCP servers, gateway tools, and provider-specific aliases.

Tool sources

Agents draw tools from a catalog with four sources:

Built-in AgentCore tools

Shipped with Bedrock AgentCore:

ToolCapability
BrowserFetch and render live web pages
CodeInterpreterRun Python in a sandbox
EmailGatewaySend email via a configured gateway

Remote MCP servers

User-configured by Config URL. Credentials and headers are envelope-encrypted and injected at deploy time.

Configure per-user in Settings → Tools.

AgentCore Gateway tools

Routed through the provider-configured gateway ARN in Bedrock settings.

Tool aliases

Friendly names (e.g. browser, code_interpreter) mapped per-provider to the real harness tool type. Aliases are managed as data so the catalog can evolve without code changes.

Console management

Settings → Tools lists configured tools. Admins add MCP servers, set credentials, and verify connectivity.

When the composer proposes a plan, tool references resolve against the catalog available to the workflow’s provider.

Deploy-time resolution

At deploy, Floprints:

  1. Resolves each agent’s tool list to concrete harness tool configurations
  2. Snapshots the resolved tools into the workflow version
  3. Injects secrets through the SecretStore interface (never logged or returned)