MCP and coding agents

Ferry exposes its control plane through Model Context Protocol so a compatible coding agent can create links, inspect analytics, and help configure domains.

Connection details

Setting	Value
Server URL	https://api.ferrylink.io/v1/mcp
Transport	Streamable HTTP request and response
Authentication	Workspace sk_ secret key

Use the server URL and an authorization header in the MCP client you trust:

Authorization: Bearer sk_live_your_secret_key

Caution

An MCP connection uses a workspace secret key. Keep it in the MCP client’s secret or environment configuration. Never place it in an app, an SDK setup file, a prompt, or source control.

Available tools

Tool	Job
create_link	Create a link for a project and domain
list_links	List workspace links, optionally filtered by project
setup_domain	Claim a shared hostname or attach a custom hostname
get_analytics_overview	Read project funnel, install mix, traffic quality, and coverage
get_analytics_timeseries	Read an hourly or daily metric trend
get_analytics_links	Compare links with measures and conversion rates
get_analytics_link	Inspect one link’s funnel and breakdowns
get_analytics_breakdown	Group project analytics by a supported dimension

The deprecated get_link_stats tool remains available for compatibility. New integrations should use the Analytics V2 tools above.

Give the agent a bounded task

Good requests identify the project, target domain, payload, and intended outcome:

Create a Ferry link for the Summer Launch project on go.acme.com.
Route the app to the product screen with product_id sku_123.
Use campaign source newsletter, medium email, and name summer-launch.
Return the final HTTPS link.

For analytics, include the project and time range:

Compare Ferry links in the Summer Launch project over the last 30 days.
Sort by attributed revenue and call out links with high opens but low signup rate.
Tell me if the data is stale.

Agent integration prompt

You can also ask a coding agent to implement the SDK in an application repository:

Add the Ferry SDK to this app using the platform guide at ferrylink.io/docs.

Use the Ferry public key from app configuration. Register one link handler
at startup, route from link.data, configure the platform association for
go.acme.com, and report signup and purchase events.

Never add an sk_ key to the app. Preserve the existing navigation and
analytics architecture. Add tests for the routing function.

Review the agent’s changes before release, especially platform entitlements, Android manifests, public-key environment selection, and the route fallback for unknown payloads.