Connect · BAMF Developer Platform

Connect MCP & Skills

How Connect agents split work across BAMF MCP tools, direct API calls, governed browser skills, and fallback reconciliation.

Connect should feel like one agent surface, but work still needs explicit routing across API, MCP, browser skills, and reconciliation.

Browser skills should carry tighter approval rules and audit traces for setup or UI-bound mutations.

On this page

• Fetch the capability map
• Route fuzzy operator requests
• Execute browser ops only when needed

Agent discovery

• llms.txt
• llms-full.txt
• OpenAPI schema
• LinkedIn AI Agent Playbook

Related documentation

• BAMF Developer Docs - Build creator workflows with the BAMF REST API, Product MCP, playbooks, local agent kits, and agent-discoverable docs.
• Connect Overview - BAMF Developer Docs - Public overview of the Connect CRM, outreach ops, MCP, browser skills, and client-portal surface.
• Client Portal Integration - BAMF Developer Docs - How the bamf.com client portal should expose Connect docs, API keys, MCP setup, and shared queue language as one developer surface.
• Connect API - BAMF Developer Docs - Campaign, lead, conversation, tagging, and qualification endpoints for the Connect CRM surface.
• Connect API Contract - BAMF Developer Docs - How Connect keeps a clean api.bamf.ai contract, stable resource naming, and clear product-facing endpoints.
• Campaign Stats & Queues - BAMF Developer Docs - Branded BAMF metrics, queue health, and campaign scoreboard endpoints for connection rate, reply rate, warm-lead flow, and operator visibility.