Scispot

io.scispotPublished by scispot.ioOfficial publisherv1.0.0Updated Nov 2, 2026

Turn any LLM into your lab assistant: search samples, track experiments, analyze data with AI.

VerifiedStreamable HTTPWeb executableFiles & StorageKnowledge & MemoryData & Analytics

Overview

AI-generated overview

Remote MCP server that connects an assistant to a Scispot lab workspace to query Labsheets, manage ELN experiments, protocols and documentation, and look up…

What you can do
  • List, inspect schemas for, search and fetch Labsheet rows and folders
  • List, read, create and write experiments, protocols and documentation entries, and link Labsheet rows to them
  • Browse storage locations and fetch manifests by ID or barcode
  • List Labspaces and list sample UUIDs associated with a Labflow
  • Download a row's image thumbnail
When to use it
Useful for lab and research teams already on Scispot who want to query sample and inventory data, draft or update ELN records, and trace samples to protocols through natural language instead of the web UI.
Requirements
A remote server at mcp.scispot.io; no local install. Requires a Scispot account with API access and OAuth 2.0 with PKCE, where the Scispot API key is supplied as the client secret (or as a Bearer token when registering in Claude Code).
Before you install
Eleven tools write to the workspace: updating Labsheet rows overwrites existing values, and writing to experiments, protocols and documentation modifies records. Treat the Scispot API key as a secret and avoid pasting it into shared configs. Workspace data is sent to the remote server to execute requests.

Installation

In SourceWeft

  1. Open Scispot 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.scispot%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. The client completes OAuth sign-in on first connect.

{
  "mcpServers": {
    "scispot": {
      "type": "http",
      "url": "https://mcp.scispot.io/"
    }
  }
}

README

Scispot MCP Server

Connect Claude to your Scispot lab workspace — query Labsheets, manage ELN experiments, protocols, documentation, storage locations, manifests, and more, all through natural language.

Description

The Scispot MCP Server is a remote Model Context Protocol (MCP) server that integrates Scispot's Lab Operating System with AI assistants like Claude. It provides 27 tools spanning Labsheet data management, Electronic Lab Notebook (ELN) operations, inventory/storage lookups, and Labflow sample tracking. The server runs as an AWS Lambda function and authenticates via OAuth 2.0 with PKCE.

Features

  • Labsheet Management — List, search, and filter Labsheet rows; inspect schemas; add and update data; organize by folders.
  • ELN Experiments — List, read, create, and write content to experiments; link Labsheet rows for traceability.
  • ELN Protocols — List, read, create, and write structured content (text, sections, files, images) to protocols; link Labsheet rows.
  • ELN Documentation — List, read, create, and write to documentation entries; link Labsheet rows.
  • Storage & Inventory — Browse storage locations (freezers, rooms, cabinets) and fetch manifests (plates, boxes, racks) by ID or barcode.
  • Labflows — List sample UUIDs associated with a Labflow for downstream analysis.
  • Labspaces — Discover all available Labspaces as the entry point for ELN navigation.

Setup

Claude web app (Anthropic MCP Directory)

Use these steps when using Claude in the browser (claude.ai), not Claude Code.

  1. Visit the Anthropic MCP Directory
  2. Find and connect to Scispot
  3. Complete OAuth authentication using your Scispot API key
  4. Start interacting with your workspace through Claude

Claude Code (terminal)

From a terminal, register the remote MCP server with Claude Code using your Scispot API key:

bash
claude mcp add scispot https://mcp.scispot.io/ --transport http --header "Authorization: Bearer YOUR_SCISPOT_API_KEY"

Replace YOUR_SCISPOT_API_KEY with your actual API key. Restart Claude Code or reload MCP configuration if prompted so the new server is picked up.

Authentication

This server requires OAuth 2.0 authentication with PKCE (S256). During the connection flow:

  • You will be prompted to provide your Scispot API key as the client secret
  • The API key is used solely as a Bearer token for Scispot API requests
  • No credentials are persisted to permanent storage on the server
  • Authorization codes expire within 5 minutes

You need a valid Scispot account with API access. Contact your Scispot administrator if you need an API key.

Examples

Example 1: Explore and query Labsheet data

User prompt: "Show me all the Labsheets in my workspace, then find the schema for the 'Cell Lines' Labsheet and search for rows where the Status column equals 'Active'."

What happens:

  • Server calls list_labsheets to return all available Labsheets
  • Server calls get_labsheet_schema for "Cell Lines" to discover column names and types
  • Server calls search_labsheet_rows with a mandatory filter on the Status column
  • Returns matching rows with all column data

Example 2: Create an experiment and write a protocol summary

User prompt: "Create a new experiment called 'Western Blot Optimization Round 3' in the 'Protein Lab' Labspace, then write a summary of the protocol steps I'll be using."

What happens:

  • Server calls list_labspaces to confirm "Protein Lab" exists and get its location
  • Server calls create_experiment_stub with the name and location
  • Server calls write_to_experiment to append the protocol summary as HTML content
  • Returns confirmation with the new experiment details

Example 3: Link Labsheet samples to a protocol with structured content

User prompt: "Find all samples in the 'Reagent Inventory' Labsheet where the Lot Number is 'LOT-2025-001', link them to the 'Sample Preparation v2' protocol in the 'QC Lab' Labspace, and add a structured section to the protocol documenting the linked samples."

What happens:

  • Server calls search_labsheet_rows to find matching rows in "Reagent Inventory"
  • Server calls link_labsheet_to_protocol to create traceability links between the rows and the protocol
  • Server calls write_to_protocol with content_type='json' and a structured elements array containing a section header and text descriptions
  • Returns confirmation of linked rows and updated protocol content

Example 4: Browse storage locations and fetch a manifest

User prompt: "Show me all storage locations in my workspace, then look up the manifest with barcode 'PLT-00142'."

What happens:

  • Server calls list_locations to return all root-level storage locations (freezers, rooms, cabinets)
  • Server calls get_manifest with the barcode to fetch the plate/container details including all wells or slots
  • Returns the full manifest layout with sample positions

Example 5: Navigate ELN structure and read documentation

User prompt: "List all Labspaces, then show me the protocols in the 'Genomics' Labspace, and read the full content of the 'DNA Extraction SOP' protocol."

What happens:

  • Server calls list_labspaces to discover available Labspaces
  • Server calls list_protocols with location "Genomics" to list all protocols
  • Server calls get_protocol by name to fetch the full protocol content
  • Returns the complete protocol text with formatting

Available Tools

Read-Only Tools (16)

ToolDescription
list_labsheetsList all Labsheets in the workspace
get_labsheet_schemaGet column definitions for a Labsheet
search_labsheet_rowsSearch and filter Labsheet rows
get_labsheet_rowFetch a single row by UUID
list_labsheet_foldersList folders or Labsheets within a folder
list_labspacesList all ELN Labspaces
list_experimentsList experiments in a location
get_experimentFetch full experiment content
list_protocolsList protocols in a location
get_protocolFetch full protocol content
list_documentationsList documentation entries in a location
get_documentationFetch full documentation content
list_locationsList root-level storage locations
get_manifestFetch a manifest by hrid, uuid, or barcode
list_labflow_samplesList sample UUIDs for a Labflow
get_image_thumbnailDownload a row's image thumbnail

Write Tools (11)

ToolDestructiveDescription
add_labsheet_rowsNoAdd new rows to a Labsheet
update_labsheet_rowsYesOverwrite existing row values
create_experiment_stubNoCreate an empty experiment
write_to_experimentYesAppend/prepend content to an experiment
create_protocol_stubNoCreate an empty protocol
write_to_protocolYesWrite text, structured JSON, or images to a protocol
create_documentation_stubNoCreate an empty documentation entry
write_to_documentationYesAppend/prepend content to documentation
link_labsheet_to_experimentNoLink Labsheet rows to an experiment
link_labsheet_to_protocolNoLink Labsheet rows to a protocol
link_labsheet_to_documentationNoLink Labsheet rows to documentation

Privacy Policy

This MCP server processes only the data necessary to execute requested operations against your Scispot workspace. No conversation data is collected or stored.

For complete privacy information, see our privacy policy: https://www.scispot.com/legal/privacy-policy

Support

Source: README.md at commit 303e3aa

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.0LatestSep 16, 2026

Score

75% 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
  • License10 pts

    Declare a license in the repository or the registry entry.