Saina Studio MCP

run.sainaPublished by saina.runOfficial publisherv1.0.0Updated Oct 30, 2026

Run Saina decision endpoints and retrieve decisions via MCP.

VerifiedStreamable HTTPWeb executableProductivity & Workflow

Overview

AI-generated overview

Remote MCP endpoint that lets an assistant run Saina decision endpoints and retrieve decisions from Saina.

What you can do
  • Run Saina decision endpoints through the assistant
  • Retrieve existing decisions from Saina
  • No individual tools are documented in the listing, so the exact operations are not described.
When to use it
Useful when you already work with Saina decisions and want an assistant to trigger decision endpoints or pull decision results without leaving the chat.
Requirements
Remote streamable HTTP endpoint at api.saina.run; no local package. Requires OAuth authentication plus an Authorization header carrying a Saina API key as a Bearer token, created in Saina Studio under Keys.
Before you install
The server needs a Saina API key sent as a Bearer token in the Authorization header; treat it as a secret and grant only the access you intend. Running decision endpoints may trigger actions or consume Saina resources, and the scope of what the tools can read or change is not documented here.

Installation

In SourceWeft

  1. Open Saina Studio MCP 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/run.saina%2Fstudio-mcp/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": {
    "saina-studio": {
      "type": "http",
      "url": "https://api.saina.run/v1/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. v1.0.0LatestOct 30, 2026

Score

56% 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

    Publish an icon in the registry entry.

  • 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.