Orgsdk

ai.orgsdkPublished by orgsdk.aiOfficial publisherv1.0.0Updated Oct 24, 2026

Hosted runtime for persistent agent teams, durable workflows, memory, schedules, and goals.

VerifiedStreamable HTTPWeb executableAI & ML

Overview

AI-generated overview

A hosted runtime that gives an assistant persistent agent teams, durable workflows, memory, schedules, and goals.

What you can do
According to its registry description, this is a hosted runtime for persistent agent teams, durable workflows, memory, schedules, and goals. It is offered as a remote streamable HTTP endpoint rather than a local package. No individual tools are listed in the supplied material, so the exact operations available are not documented here.
When to use it
Consider it when an assistant needs long-running, stateful work: coordinating multiple agents, keeping memory across sessions, running scheduled jobs, or tracking goals over time. It is less relevant for one-off, stateless requests.
Requirements
A remote MCP client that supports streamable HTTP, connecting to the provider's hosted endpoint. No packages, environment variables, or headers are declared, and no authentication is declared in the manifest.
Before you install
The manifest declares no authentication, so it is unclear how access is controlled or who can reach the endpoint. The description mentions persistent memory and durable workflows, which implies data is stored on the provider's servers; the material does not state what is retained, for how long, or how it is protected. No tools are listed, so the scope of actions the assistant could take is unverified.

Installation

In SourceWeft

  1. Open Orgsdk in the dashboard and add it to a workspace.
  2. 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/ai.orgsdk%2Fmcp/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.

{
  "mcpServers": {
    "orgsdk": {
      "type": "http",
      "url": "https://relay.orgsdk.ai/mcp"
    }
  }
}

Tools

0
SourceWeft has not read this server's tools yet.

Version history

1
  1. v1.0.0LatestSep 16, 2026

Score

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

    Keep the endpoint answering the MCP handshake; SourceWeft probes it every 30 days.

  • Auth declaredRequired10 pts

    Declare the credential headers in the registry entry, or keep the endpoint answering the probe so its auth can be classified.

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