---
updatedAt: 2026-09-08T14:57:09.000Z
agentTools:
projectIndex: https://developerdocs.elabnext.com/llms.txt
---
# Connect other MCP apps to SciSure Research
Use this guide when your AI application, agent environment, or developer harness is not listed on the guide hub. Menu names and configuration formats vary, but a compatible application can connect directly to the SciSure Research MCP endpoint using Streamable HTTP and OAuth.
## Requirements for connecting to SciSure MCP
**SciSure MCP requires a Private Cloud or On-premises SciSure Research environment.** It is not available on the shared Cloud.
The language model does not connect to SciSure by itself. The application around the model must provide a compatible remote MCP client and an OAuth sign-in flow.
* **Remote MCP** — Support for adding a remote MCP server by HTTPS URL—not only launching local servers with commands or `stdio`.
* **Streamable HTTP** — Native support for the current MCP HTTP transport. The application may label this simply as “HTTP” or “Remote.”
* **OAuth sign-in** — OAuth 2.1 discovery and browser authorization, or a user-defined OAuth client with a callback URL.
* **SciSure access** — Your tenant address, a SciSure Research account, and permission to create an OAuth client if manual registration is required.
**The connection in plain language**
**Your AI application** — The MCP host → **One MCP connection** — A client managed by the host → **SciSure Research** — The remote MCP server
> ❗️ When this guide does not apply
>
> If the application supports only local `stdio` servers, OpenAPI integrations, or plain REST tools, this direct guide does not apply. Ask the vendor whether native remote MCP with Streamable HTTP and OAuth is supported.
## 1. Find the application’s MCP support
Look in the application’s documentation or settings before entering any credentials. The feature may be available only in a developer mode or on certain plans.
* Search for **MCP servers**, **custom connectors**, **integrations**, **tools**, or **developer mode**.
* Confirm that it accepts a remote server URL beginning with `https://`.
* Confirm support for **Streamable HTTP** and OAuth authorization in a browser.
* For a cloud-hosted application, confirm it can reach your SciSure tenant from the public internet or through your organization’s allowlisting rules.
> 📘 Remote MCP is the decisive feature
>
> A product may support MCP but only for local command-based servers. The decisive feature for this tutorial is support for a **remote authenticated MCP server**.
## 2. Add the SciSure MCP endpoint
Open the application’s MCP, connector, or tools settings and add a new remote server. Use the closest matching field names in the application.
**SciSure Research MCP endpoint:** `https:///api/v1/mcp`
| Field | Value |
| ---------------------- | ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| Name or label | **SciSure MCP** — This is the name users see in the application. |
| Server URL or endpoint | `https:///api/v1/mcp` — Replace `` with the base URL you use to sign in to your SciSure Research environment (for example `acme.elabnext.com`). Your instance also publishes its configuration at `/.well-known/oauth-authorization-server`. |
| Transport | **Streamable HTTP** — Choose “HTTP” or “Remote” only when that is the application’s label for native Streamable HTTP. |
| Authentication | **OAuth or OAuth 2.1** — Use automatic discovery when available. |
| Connection ID | `SciSure-MCP` — Use a stable unique value if the application asks for one. |
| Headers or API token | **Leave blank** — Do not substitute an API key for the OAuth flow. |
> ❗️ Replace the placeholder
>
> Do not enter the angle brackets literally. For an instance at `acme.elabnext.com`, the endpoint becomes `https://acme.elabnext.com/api/v1/mcp`.
### If the application uses a configuration file
Configuration schemas are application-specific. The following shows the common shape only; keep the field names required by your application.
**Illustrative MCP configuration**
```json
{
"mcpServers": {
"scisure": {
"url": "https:///api/v1/mcp"
}
}
}
```
## 3. Let the application discover authentication
Select **Connect**, **Verify**, **Register**, or **Sign in**. A compatible client contacts the SciSure endpoint and discovers that OAuth authorization is required.
### Automatic path — A browser sign-in opens
The application can register or identify itself automatically.
1. Continue directly to step 5.
2. Sign in only on your own SciSure tenant domain.
### Manual path — Client credentials are requested
The application expects a user-defined OAuth client.
1. Copy its callback or redirect URL exactly.
2. Complete step 4 before returning to the application.
> 📘 Prefer automatic discovery
>
> If the application asks for an authorization URL or token URL, first look for an automatic discovery option. The SciSure MCP endpoint publishes the authentication information a compatible client should use.
## 4. Register the application in SciSure Research
Complete this step only when the application displays a callback URL and asks you for a Client ID and Client Secret. Skip it when automatic sign-in already opened.
* Keep the application open and copy its **callback URL** or **redirect URI**.
* In SciSure Research, open **Group Settings → OAuth2 Clients** and add an application.
* Use a recognizable application name, such as **My AI App — SciSure MCP**.
* Create a unique Client ID, for example `My-AI-App-SciSure-MCP`.
* Paste the callback URL exactly. Do not add or remove a slash, port, path, or character.
* Select only the read scopes required for the intended work, then create the OAuth client.
* Copy the generated Client Secret and return to the AI application.
* Enter the Client ID and Client Secret. If a token endpoint authentication method is requested, choose `client_secret_post`.
> ❗️ Keep the Client Secret private
>
> The Client Secret is sensitive. Never publish it in documentation, screenshots, messages, prompts, configuration committed to source control, or a shared knowledge base.
> 📘 Start with minimal scopes
>
> Available scopes depend on your SciSure configuration. Start with the minimum read-only scopes the application needs. Access is also limited by the permissions of the SciSure user who signs in.
## 5. Sign in and approve the connection
Save or reconnect the MCP server, then start the OAuth flow. The application should open your browser and redirect you to SciSure Research.
* Confirm the address bar shows your own SciSure Research instance domain before entering credentials.
* Sign in with the SciSure Research account whose access the AI application may use.
* Review the requested scopes and approve the connection.
* Allow the browser to return to the AI application or its registered callback page.
* Confirm the connection status changes to **Connected**, **Authenticated**, or a similar success state.
> 👍 What the token grants
>
> The OAuth token represents both the approved scopes and the signed-in user’s SciSure permissions. Connecting an application does not give it unrestricted access to the tenant.
## 6. Enable SciSure tools and test a read request
Some applications connect the server but keep its tools disabled until you enable them for a conversation, agent, workspace, or model.
* Enable the **SciSure MCP** server or its individual tools.
* Start a new conversation if the current one was opened before the connection was added.
* Choose a model that supports tool use.
* Try a simple read-only request and approve the tool call if the application asks.
**Example test prompt**
```text
List my most recent experiments in SciSure Research.
```
A successful result normally shows a SciSure tool invocation followed by data the signed-in user is allowed to read. Exact tool names and approval prompts vary by application.
> 👍 Connected
>
> You are connected when the application lists SciSure tools, can invoke an authorized tool, and returns SciSure Research data without another authentication error.
## Common compatibility and connection issues
Because this is a generic guide, start by matching the symptom to the capability the application may be missing.
The application asks for a command, arguments, or an executable
That screen is for a local `stdio` MCP server. Look for a separate remote-server or URL-based connection option. If none exists, the application cannot use this direct guide.
The transport list offers SSE but not Streamable HTTP
SSE usually refers to the legacy HTTP+SSE transport. Choose native Streamable HTTP when available. If the application supports only the legacy transport, ask the vendor about current remote MCP support.
The endpoint cannot be reached
Confirm the URL is exactly `https:///api/v1/mcp`. A cloud-hosted application must be able to reach the tenant from its own infrastructure; a URL that works only inside your local network is not sufficient.
The application reports an OAuth or discovery error
Confirm authentication is set to OAuth rather than API key, bearer token, or none. Re-enter the tenant endpoint and retry discovery. If the application requires manually entered authorization endpoints instead of supporting discovery, consult its documentation or contact SciSure.
The redirect URI is rejected
Copy the callback URL from the application again and compare it character by character with the redirect URI registered in SciSure Research. Scheme, hostname, port, path, capitalization, and trailing slash must match.
Sign-in succeeds but the application still shows disconnected
Save the connection, restart or refresh the application, and reconnect. For desktop applications, confirm the browser was allowed to open the local callback address and that a firewall did not block it.
The connection works but no SciSure tools appear
Enable the server for the current conversation or agent, select a tool-capable model, then start a new conversation. If tools remain missing, reconnect after confirming the corresponding read scopes are enabled on the SciSure OAuth client.