Skip to main content
The Scispot MCP Server connects AI assistants to your Scispot workspace. You can ask questions, retrieve lab data, and perform supported actions in natural language.
The Scispot MCP Server is in private beta. Contact your Customer Success representative to request access before you connect a client.

​
Choose MCP or the REST API

Use the MCP Server when you want an AI assistant to work with Scispot conversationally. Use the REST API when you build a programmatic integration or automation.

​
Before you begin

You need:
  • Scispot MCP beta access
  • A Super Admin Scispot account or an account with Dry Lab access
  • An MCP-compatible AI client
The MCP Server uses https://mcp.scispot.io.

​
Security and permissions

The MCP Server respects your existing Scispot permissions. You can access only the data and actions that your Scispot account allows. Web connectors use OAuth. The user will be required to authenticate with their Scispot account.

​
Connect Claude.ai

Use Claude.ai’s custom connector flow to connect through OAuth. The user will be required to authenticate with their Scispot account.
1

Open custom connectors

In Claude.ai, open Settings and then Connectors. Select Add custom connector.
2

Search for Scispot.io

Search for “Scispot.io” in the connector search bar.
3

Connect to the Scispot MCP Server

Click the “Connect to Claude” button.
4

Authorize Scispot

Complete the Authentication flow by logging in with your Scispot account.
Test the connection with a read-only request such as: “List my Scispot Labsheets.”

​
Connect Claude Code

Claude Code supports remote MCP servers over HTTP. Use the interactive MCP setup flow and configure the Scispot server as an HTTP MCP server.
1

Start MCP setup

Run claude mcp add --transport http scispot-mcp https://mcp.scispot.io/ in your terminal.
2

Open Claude Code

Run Claude Code with the claude command.
3

Check your mcp connections

Enter /mcp to check your MCP connections.
4

Authenticate Scispot mcp

Authorize the Scispot MCP Server by selecting the “scispot-mcp” connection. Select Authenticate and login with your Scispot account.
5

Verify the connection

Start or restart Claude Code. Ask it to list your Scispot Labsheets to confirm that it can discover the server tools.
Test the connection with a read-only request such as: “List my Scispot Labsheets.”

​
Connect another MCP-compatible client

You can connect other clients that support remote HTTP MCP servers. The exact labels and configuration experience vary by client.
  1. Add a remote MCP server or connector in your client.
  2. Set Connection URL to https://mcp.scispot.io.
  3. Choose OAuth when your client supports the Scispot OAuth flow.
  4. When prompted, login with your Scispot account.
  5. Confirm the connection with a read-only request before you perform a write operation.
Contact Customer Success if your client cannot complete the OAuth flow or does not support custom HTTP headers.

​
What you can do

The MCP Server provides 33 tools across these areas: The tools that change data require the same permissions as the equivalent action in Scispot.

​
Use write actions safely

Start with read-only requests. Review the data and planned action before you approve a write request. For important records, ask the AI to summarize the proposed changes before it creates or updates data. Review the resulting record in Scispot after the action completes. For regulated workflows, make sure your use of the AI client and its data handling meets your organization’s validation, review, and approval requirements.

​
Troubleshooting

​
You cannot add the connector

Confirm that Customer Success enabled MCP beta access for your workspace. Verify that you entered https://mcp.scispot.io exactly.

​
Authentication fails

Contact Customer Success at cs@scispot.io if you cannot authenticate.

​
You cannot see data or perform an action

The MCP Server uses your Scispot permissions. Confirm that you can complete the same action in Scispot with your account.

​
The AI proposes an unexpected change

Do not approve the action. Ask the AI to explain the proposed change, then verify the target records in Scispot before you continue.