ARP Keep the systems your business relies on. Give your agents a useful way to work with them through custom MCP integrations.
Explore the connections ↓
These platforms have documented integration paths we can build on. Each connection is scoped to your process; this directory is not a list of one-click, ready-made connectors.
12 platforms
Find relevant products and connect catalog workflows.
Dev Dashboard app with scoped access tokens. Client credentials apply to stores in the same organization; other merchants need the appropriate app installation and authorization flow. Product search is used in our private beta.
Official documentation ↗Documentation checked · 26 Sep 2026Bring products and orders into connected workflows.
Store-generated consumer key and secret, with read/write permissions set by the owner. Store hosting and endpoint access must be checked.
Official documentation ↗Documentation checked · 26 Sep 2026
Find contacts, companies, and deals where the work happens.
Private-app access token with selected scopes for an account-owned integration. Public distribution uses OAuth; endpoint availability depends on the account and plan.
Official documentation ↗Documentation checked · 26 Sep 2026Connect deal updates, contacts, and sales activities.
API token for a private account integration, or OAuth for distributed apps. Access follows the user’s permissions.
Official documentation ↗Documentation checked · 26 Sep 2026
Make business knowledge and structured records useful to agents.
Internal connection token. Workspace owners choose capabilities and explicitly grant access to the relevant pages. Public connections use OAuth.
Official documentation ↗Documentation checked · 26 Sep 2026
Work with the records and relationships your team already maintains.
Scoped personal access token with selected bases and permissions. Account roles, plan limits, and organization policies still apply.
Official documentation ↗Documentation checked · 26 Sep 2026
Connect tasks, projects, and the next useful step.
Personal access token for private use; OAuth for an app used by multiple people. Access follows the authorized account.
Official documentation ↗Documentation checked · 26 Sep 2026Bring boards and work updates into your business process.
Personal token with the user’s permissions for a private connection. Public apps use OAuth. Plan and complexity limits apply.
Official documentation ↗Documentation checked · 26 Sep 2026Turn defined next steps into useful task workflows.
Personal token from integration settings for private use; OAuth is available for distributed applications.
Official documentation ↗Documentation checked · 26 Sep 2026Connect issues, project progress, and team handoffs.
Public REST API. For a Morning service used by customers, use a compliant OAuth/Forge app. Atlassian restricts third-party apps that collect customer API tokens; personal-token scripts are not the managed-service route.
Official documentation ↗Documentation checked · 26 Sep 2026
Look up payment and subscription information within an approved workflow.
Secret or restricted API key for an account-owned integration. Test keys support sandbox development. Connecting other businesses uses the appropriate Stripe Connect authorization.
Official documentation ↗Documentation checked · 26 Sep 2026Connect messaging workflows and delivery information.
API keys with appropriate account permissions. Channel setup, phone numbers, WhatsApp eligibility, and messaging rules remain separate requirements. The WhatsApp pilot currently runs through Twilio.
Official documentation ↗Documentation checked · 26 Sep 2026No matches yet. Try another name or tell us what you use.
We start with what people need to accomplish, select the relevant capabilities, and build MCP tools with clear inputs, permissions, and results. Your agents get a defined way to use your systems. Your team keeps control of the work.
Our WhatsApp bot already uses a Shopify connection for advanced product searches and runs through Twilio. See how the conversation and operator inbox work together.
Explore the WhatsApp bot ↗Tell us which tools you use and what should happen between them. We can assess a custom integration, including your own systems with documented interfaces.
Discuss your integration ↗A public API confirms a technical starting point, not every action or a completed Morning integration. Account permissions, scopes, plans, rate limits, terms, and channel eligibility determine what can be built. Private tokens can support account-owned implementations on many platforms; public or managed distribution may require OAuth, app registration, or review. Credentials are configured securely during implementation, never submitted through this directory.