Claude Code
Connect Claude Code to Aroai over Streamable HTTP and run a first local business workflow.
Integrations
Your AI stack. A shared business toolkit.
Connect a compatible AI assistant, developer tool or automation client to Aroai over Streamable HTTP.
Connection basics
Aroai uses a single Streamable HTTP endpoint for discovery and tool calls. Compatible clients can authenticate with OAuth or an API key. Client feature support and account controls vary by product and version.
Aroai MCP endpoint
https://mcp.aroai.com/v1Choose your client
Claude web and Desktop
Add Aroai as a remote MCP connector in Claude web or Desktop, then review your plan and organization controls.
ChatGPT
Add Aroai as a custom MCP connector from Plugins and review current account and workspace access.
Cursor
Configure Aroai as an HTTP MCP server in Cursor and keep API keys in protected client credentials.
Copilot Studio
Configure Aroai as a remote Streamable HTTP MCP server in Microsoft Copilot Studio.
Gemini CLI
Add Aroai to Gemini CLI as a remote HTTP MCP server using an authentication method supported by your client version.
Gemini API
Connect the Gemini API's remote MCP integration to Aroai over Streamable HTTP.
Gemini Enterprise
Configure Aroai through your Gemini Enterprise administrator and review imported actions before enabling them.
n8n
Use a current n8n MCP Client Tool with Streamable HTTP to add Aroai tools to an AI workflow.
Before a first workflow
- 01
Confirm the exact client
Use the matching guide for Claude Code, Claude web/Desktop, ChatGPT, an API or a cloud product. These are not interchangeable surfaces.
- 02
Connect the endpoint
Configure https://mcp.aroai.com/v1 with Streamable HTTP where offered.
- 03
Authenticate
Use the sign-in flow or protected API-key credentials accepted by the client.
- 04
Discover and review
Check the tools and features the client actually exposes, then run a small task and inspect its source fields.
Bring a source-provider key where supported
Keep the Aroai client credential separate from paid data-provider credentials. An eligible tool may use a workspace source key and charge fewer Aroai credits when it avoids an upstream platform expense. Check each published tool for support and its actual credit rate.
Provider keys and credits
See live support, billing behavior and planned providers.
Feature support depends on the host
Tools, resources, prompts, skills and interactive interfaces have different support requirements. Check client version and workspace permissions before designing around an optional feature.
Local intelligence. Ready to build.
Start with a task you can inspect.
Connect a compatible client, choose a workflow and review the source fields that come back.