Developers
Connect agency workflows with MCP and webhooks
Connect supported AI assistants, receive workflow events and link agency operations to other systems. Choose the interface that matches the job and your access.
Reviewed by Agency Pilot ·
Use MCP for supported assistant workflows
The remote MCP service lets an authorized assistant work with supported Agency Pilot tools. Each request is relayed with the caller’s access token, so the API applies account, agency, role and client-portal permissions. Start by reading a known record, then inspect the tool’s current inputs before attempting a change. Tool availability and plan entitlements should be confirmed in the account.
Use webhooks for event-driven integrations
Agency Pilot includes webhook workflows for eligible plans. Define the event, destination and record identity before enabling an integration. Test with an appropriate example, inspect delivery results and design the receiver to handle repeats. A webhook delivery is an integration event; it should not silently be treated as payment confirmation or approval unless the event actually represents that state.
Plan the integration boundary
Write down which system owns each field, how duplicate records are identified and what happens when an external service is unavailable. Keep tokens in the integration’s credential store, not in user-facing notes. Ask support about a required interface that is not documented. The internal app API is not presented here as a stable, unrestricted public REST contract.
Frequently asked questions
Where is the MCP endpoint?
The public service is https://mcp.agencypilot.io, with /mcp also supported. Follow the connection guide and your assistant’s current remote-MCP setup.
Are MCP and webhooks interchangeable?
No. MCP exposes supported tools to an authorized assistant. Webhooks deliver configured events to a receiver. Select the interface according to whether the workflow needs a requested action or an event notification.
Can an integration read another agency’s data?
Access is checked using the caller’s permissions and tenancy rules. A connected tool does not grant access to unrelated agencies or unrestricted client records.