Rocky

world.getrockyPublished by getrocky.worldOfficial publisherv0.1.0Updated Oct 24, 2026

Your personal world model for any agent.

VerifiedStreamable HTTPWeb executableKnowledge & Memory

Overview

AI-generated overview

Rocky is a remote MCP endpoint that presents itself as a personal world model for any agent, connected over streamable HTTP with OAuth sign-in.

What you can do
Connects an assistant to a hosted personal world model service over a remote streamable HTTP endpoint. The manifest lists no tools, so the specific actions available are not documented here. Access is gated behind OAuth authentication, so the assistant works within a signed-in account context.
When to use it
Consider it when you want an agent to draw on a hosted personal world model rather than local data. Because no tools or documentation are published, evaluate it only after confirming what it actually exposes.
Requirements
A remote MCP client that supports streamable HTTP, network access to the provider's endpoint, and an OAuth sign-in with the provider. No environment variables, headers or packages are declared.
Before you install
Signing in grants the service an OAuth connection to your account, and the server's purpose implies personal context data being sent to a third party. No tool list is published, so what it reads or changes cannot be verified in advance.

Installation

In SourceWeft

  1. Open Rocky 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/world.getrocky%2Frocky/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": {
    "rocky": {
      "type": "http",
      "url": "https://mcp.getrocky.world/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. v0.1.0LatestOct 16, 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.