User Guide: Enable OSC with AI agents - EyevinnOSC/community GitHub Wiki

Connect AI Agents with OSC

The integration of Model Context Protocol (MCP) into Eyevinn Open Source Cloud (OSC) now enables anyone – regardless of technical expertise – to deploy and manage sophisticated web services simply by describing their needs in plain language.

In this guide we describe how you enable this in your favorite AI agent.

For Claude Desktop Users

Configure and extend your Claude for Desktop so that it can get access to all the tools provided by Open Source Cloud. Don't worry it will ask for your permissions before executing any actions.

Step 1: Download Claude for Desktop

Start by downloading Claude for Desktop, choosing either macOS or Windows.

Follow the installation instructions.

If you already have Claude for Desktop, make sure it's on the latest version by clicking on the Claude menu on your computer and selecting "Check for Updates…"

Step 2: Connect Claude with OSC

Open up the Claude menu on your computer and select "Settings...".

Select the menu alternative on the left labelled "Connectors".

In the bottom of the list you find a button "Add custom connector"

Click on it and give the connector a name, for example "OSC" and enter the URL https://mcp.osaas.io/mcp.

Then press Add.

Go to the connector and press the button "Connect". You are now prompted to authenticate with Open Source Cloud and allow access for Claude to access your OSC account on your behalf. Press the button "Allow" to allow this.

Step 3: Try it out!

You can now talk to Claude to help you perform various tasks and it will complete the tasks using all the open source tools that Eyevinn Open Source Cloud are making available.

Here are some things you might try to ask Claude:

Can you help me setup a stream for live streaming?
Can you create English subtitles in VTT format for my video file?
Can you take my video file and turn it into a black and white movie?
Can you create a team mailbox for me? (Professional/Business plans only)
Can you check the status of my team email?
What is the status of my eyevinn-test-adserver instance?
Restart my eyevinn-subtitle-generator instance called mysubs
Update the configuration of my eyevinn-test-adserver instance called myadserver (e.g. change a setting without deleting and recreating it)
Estimate the cost of running eyevinn-test-adserver before I deploy it
Create a service token for eyevinn-test-adserver so I can call its API
Create a delegate token for my service instance so I can share temporary access with a colleague
What service categories are available on OSC?
List all services in the database category
What's my current token usage and which services are consuming the most?
How long will my tokens last at my current usage rate?
Upgrade my plan to Professional

When you ask about your plan or token usage, the AI agent provides a per-service breakdown showing which services consume the most tokens, your consumption trend, and an estimate of how long your balance will last. If you ask to upgrade your plan, the agent can generate a direct Stripe Checkout link — useful when working in a terminal-based agent like Claude Code.

When you ask the agent to estimate the cost of a service before deploying it, the agent checks your current token balance, daily refill rate, and burn rate to project how many days your balance will last after adding the new service. It will suggest upgrading your plan if you are running low.

As needed, Claude will call the relevant tools and seek your approval before taking an action.

For Claude Code Users

The easiest way to get the connection command with your personal access token pre-filled is to visit Settings → MCP in the OSC web console and copy the command from there.

Alternatively, run the following command in your terminal. Replace <your-personal-access-token> with the token from Settings/API:

% claude mcp add --transport http --header "Authorization: Bearer <your-personal-access-token>" osc https://mcp.osaas.io/mcp
Added HTTP MCP server osc with URL: https://mcp.osaas.io/mcp to local config

Note: Do not share this command with others — it contains your personal access token.

Then start Claude Code:

% claude

Claude Code is now connected to OSC and ready to use.

Build a Full-Stack App with Claude Code and OSC

Want to see a complete example? The Build & Deploy a Full-Stack App with Claude Code tutorial walks through a 5-step workflow — from project setup to a live production deployment — using Claude Code with the OSC MCP integration.

Manage Services from a Service Page

When you have active instances of a service, an "Manage with AI Agent" chip appears on the service's dashboard page. Clicking it opens the AI Agent panel with a pre-filled prompt to list your instances of that service — a quick way to jump into AI-assisted management.

Troubleshooting

If the command above does not work, you can configure the connection manually by editing your Claude configuration file ~/.claude.json. Replace <personal-access-token> with the token from Settings/API:

"mcpServers": {
  "osc": {
    "type": "http",
    "url": "https://mcp.osaas.io/mcp",
    "headers": {
      "Authorization": "Bearer <personal-access-token>"
  }
},

For VS Code Users

Click on View and Command Palette menu item.

Start typing "MCP" and choose Add server.

Choose HTTP.

Enter the following URL: https://mcp.osaas.io/mcp

Give it a name, for example "Open Source Cloud".

Choose whether it should be globally available or only the current workspace. Then choose Allow when asked for allowing authentication.

Authenticate in Open Source Cloud and give VS Code access to your account. Once authenticated you should have the tools available for your agent.

For Cursor Users

Cursor supports MCP through a configuration file.

Step 1: Create or Edit the MCP Configuration File

Create or edit the file at ~/.cursor/mcp.json with the following content:

{
  "mcpServers": {
    "osc": {
      "type": "http",
      "url": "https://mcp.osaas.io/mcp"
    }
  }
}

Step 2: Restart Cursor

Close and reopen Cursor for the configuration to take effect.

Step 3: Authenticate

When you first interact with your AI agent in Cursor, it will prompt you to authenticate with OSC. Click the authentication link and grant access.

Troubleshooting

If authentication via browser doesn't work, you can use your personal access token:

Navigate to Settings/API in the OSC web console
Copy your personal access token
Update ~/.cursor/mcp.json:

{
  "mcpServers": {
    "osc": {
      "type": "http",
      "url": "https://mcp.osaas.io/mcp",
      "headers": {
        "Authorization": "Bearer <your-personal-access-token>"
      }
    }
  }
}

Replace <your-personal-access-token> with your actual token.

For Windsurf Users

Windsurf supports MCP through a JSON configuration file.

Step 1: Create or Edit the MCP Configuration File

Create or edit the file at ~/.codeium/windsurf/mcp_config.json with the following content:

{
  "mcpServers": {
    "osc": {
      "serverUrl": "https://mcp.osaas.io/mcp",
      "headers": {
        "Authorization": "Bearer <your-personal-access-token>"
      }
    }
  }
}

Replace <your-personal-access-token> with the token from Settings/API in the OSC web console.

Step 2: Restart Windsurf

Close and reopen Windsurf for the configuration to take effect.

For Codex CLI Users

OpenAI Codex CLI supports MCP through a TOML configuration file.

Step 1: Set Your Personal Access Token

Export your OSC personal access token as an environment variable (add this to your shell profile for persistence):

export OSC_ACCESS_TOKEN=<your-personal-access-token>

Replace <your-personal-access-token> with the token from Settings/API in the OSC web console.

Step 2: Edit the Codex Configuration File

Create or edit ~/.codex/config.toml and add the following:

# ~/.codex/config.toml
[mcp_servers.osc]
url = "https://mcp.osaas.io/mcp"
bearer_token_env_var = "OSC_ACCESS_TOKEN"

Step 3: Use Codex with OSC

Codex will now have access to OSC tools when you run it. The token is read from the OSC_ACCESS_TOKEN environment variable at runtime — avoid embedding the token directly in the config file.