Roar AI

[Roar AI]

The Roar AI MCP server: every AI model and app hosting, run from your AI assistant

Website · MCP docs · Models · Pricing · Sign in

[Listed in Claude's connector directory] [Listed in ChatGPT's plugin directory] [Add to Cursor] [Add to VS Code] [Remote MCP · Streamable HTTP · OAuth]

Roar AI is an AI gateway and an app hosting platform for teams. This repository is the home of its remote MCP server, the one address that lets Claude, ChatGPT, Codex, Cursor, VS Code and any other MCP client work in your Roar AI account for you:

https://cloud.roar-ai.com/mcp

Connect once and sign in with your Roar AI account. There is nothing to install, no API key to paste, and no server to run.

What you can ask

"Deploy my GitHub repo and give me the live link."

"My last deploy failed. Find out why and fix it."

"Add a Postgres database to my app and wire it up."

"Point app.example.com at my app."

"Create an API key for my app with a $50 monthly limit."

"What did we spend on AI this week, and on which models?"

"Ask a different model to review this function, and compare the two answers."

Connect it

New to Roar AI? You can create an account during the connect step itself. Your assistant opens a Roar AI sign-in page, you enter your email and a 6-digit code, and you're back in the conversation.

https://cloud.roar-ai.com/mcp

claude plugin marketplace add Roar-AI-Labs/roar-ai-mcpclaude plugin install roar-ai@roar-ai

claude mcp add --transport http roar https://cloud.roar-ai.com/mcp

codex mcp add roar --url https://cloud.roar-ai.com/mcp && codex mcp login roar

[mcp_servers.roar]url = "https://cloud.roar-ai.com/mcp"

{  "mcpServers": {    "roar": { "url": "https://cloud.roar-ai.com/mcp" }  }}

{  "servers": {    "roar": { "type": "http", "url": "https://cloud.roar-ai.com/mcp" }  }}

{  "mcp": {    "roar": { "type": "remote", "url": "https://cloud.roar-ai.com/mcp", "enabled": true }  }}

{  "mcpServers": {    "roar": { "url": "https://cloud.roar-ai.com/mcp" }  }}

What it can do

The server exposes around 90 tools. Your assistant picks the right one from what you ask.

Security and permissions

• You sign in with OAuth. Your assistant never sees a password or a long-lived key.
• It can only do what you can. Every action goes through the same permission checks as the Roar AI console. A teammate with read-only access gets a read-only assistant.
• Sensitive reads are opt-in. Reading the rows inside your app's database, or prompts stored in your request logs, needs a permission you grant separately.
• One company at a time. If you belong to more than one, you choose which one your assistant works in, and you can switch by asking it.
• AI spend has a cap. The model calls your assistant makes go through their own key with a monthly limit, which you can pause or change in the console.

See Security at Roar AI for how we handle data, residency and compliance.

About Roar AI

Roar AI gives a team two things behind one account:

• An OpenAI-compatible AI gateway. One API key reaches 200+ frontier and open-source models, with fixed published prices, spending limits per key and per project, and one bill. Read the API docs.
• App hosting built for people who vibe-code. Pick a repo and get a live URL, with a database, a domain and logs, without touching a server. Apps run in the region you choose, including in-country hosting for teams that need their data to stay local.

Start at roar-ai.com, or read the quickstart.

What's in this repository

The server itself is hosted by Roar AI, so there is no server code here, only the files that tell each assistant where to find it.

Support

• Something not working? Open an issue or contact us.
• Read the MCP guide and the troubleshooting page.

License

The configuration files in this repository are MIT licensed. Using the Roar AI service is covered by the Roar AI terms and privacy policy.