SciGround MCP (Public Beta)

ai.lickliderPublished by licklider.aiv0.1.0Updated Nov 12, 2026

Google sign-in; study_create, study_current, study_diagnostics. Remote HTTP and stdio adapter.

The publisher's own server: Ground

VerifiedStreamable HTTPWeb executable

Overview

AI-generated overview

SciGround MCP (public beta) is a remote or local MCP server that gives an assistant tools to create and inspect studies, with Google sign-in required.

What you can do
  • Create a new study through the study_create tool.
  • Check the current study with study_current.
  • Run or read diagnostics for a study with study_diagnostics.
  • Connect either to a hosted remote endpoint or through a local stdio adapter package.
When to use it
Worth considering if you want an assistant to set up and inspect studies inside the SciGround service and you are comfortable signing in with a Google account. The public beta label and the thin documentation make it a fit mainly for early evaluation.
Requirements
A SciGround account signed in through Google OAuth; authentication is required. Either the remote streamable HTTP endpoint or the local npm package run over stdio, which needs Node.js. No environment variables or headers are declared.
Before you install
Sign-in is through Google OAuth, so the server receives access tied to your Google identity; review the consent scope before authorizing. The study tools appear to create and change data in your account. It is a public beta with no published README, so behavior and data handling are not documented here.

Installation

In SourceWeft

  1. Open SciGround MCP (Public Beta) 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/ai.licklider%2Fsciground/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": {
    "sciground-public-beta": {
      "type": "http",
      "url": "https://sciground-api-mcp-845495614928.us-west2.run.app/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.0LatestNov 12, 2026

Score

60% 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.

  • License10 pts

    Declare a license in the repository or the registry entry.

Other Ground integrations