Eyevinn Open Source Cloud

io.github.EyevinnOSCPublished by GitHub account EyevinnOSCv8.15.3Updated Oct 24, 2026

Deploy open-source services and your own apps on Open Source Cloud (OSC, osaas.io).

The publisher's own server: Source

VerifiedStreamable HTTPWeb executableCloud & Infrastructure

Overview

AI-generated overview

A remote MCP server for Eyevinn Open Source Cloud that lets an assistant deploy open-source services and your own applications on the OSC platform.

What you can do
Deploy open-source services on Open Source Cloud (OSC). Deploy your own applications to the platform. The manifest lists no individual tools, so the exact operations available are not documented here; the stated purpose is deployment of services and apps on osaas.io.
When to use it
Use it when you want an assistant to help stand up open-source services or your own apps on Eyevinn Open Source Cloud without leaving the conversation.
Requirements
A remote streamable HTTP endpoint at mcp.osaas.io; no local package or runtime is needed. OAuth authentication is required, so you need an OSC account and must complete the OAuth sign-in flow. Network access to the endpoint is required.
Before you install
Deployment actions create and change resources on your OSC account, which may incur usage or costs depending on the platform's terms. Access is granted through OAuth, so review the scopes requested during sign-in. The manifest lists no tools, so confirm what the server can actually do before relying on it.

Installation

In SourceWeft

  1. Open Eyevinn Open Source Cloud in the dashboard and add it to a workspace.
  2. Connect the required credentials. They are stored privately and never shown on public pages.
  3. Enable the server for the chats that should use its tools.

Web executable via Streamable HTTP. Remote servers run from the web runtime once configured in a workspace.

Use with an agent

Paste this prompt into Claude Code, Codex, Cursor or another agent — or into SourceWeft chat. The agent reads this server's install guide, shows you its publisher, endpoint and sign-in, and adds it to your client once you agree. Keys never go into a command.

Read https://sourceweft.com/mcp/io.github.EyevinnOSC%2Fosaas/install.md and connect the MCP server it describes to my client. Before changing any config, show me its publisher, endpoint and sign-in method and wait for my OK. Never put an API key in a command or in a file I would commit; ask me where it should come from.

Read the install guide the agent follows

Other MCP clients

Add this to your client's mcpServers config. The client completes OAuth sign-in on first connect.

{
  "mcpServers": {
    "eyevinn-open-source-cloud": {
      "type": "http",
      "url": "https://mcp.osaas.io/mcp"
    }
  }
}

Tools

0
This server asks you to sign in, so SourceWeft could not read its tools without an account and has not indexed them. What a connected account sees can depend on that account and its permissions.

Version history

1
  1. v8.15.3LatestOct 13, 2026

Score

67% of the applicable checks met

How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.

  • Reached in the last 30 daysRequired25 pts
  • Auth declaredRequired10 pts
  • Tools listed15 pts

    Answer tools/list without a credential, or ship a package that starts in a sandbox without one.

  • DescriptionRequired15 pts
  • Logo10 pts
  • Documentation15 pts

    Declare a GitHub repository with a README, or serve resource_documentation in the OAuth protected-resource metadata.

  • LicenseNot applicable

    A hosted service is used under its provider's terms, so no license is expected here. This check is left out of the percentage.

Other Source integrations