Hosted MCP server/Other

Jean by Melad Labs MCP server

Hosted at jeanslabs.vercel.app·Streamable HTTP

Jean by Melad Labs gives an agent a molecular biology bench: cloning, primer and CRISPR design, Sanger verification, qPCR, alignment and phylogenetics. Calculations run in the browser and the service is free, but it is invitation-only. A personal key from /connect is carried in the address as /mcp?key=bi_... or as Authorization: Bearer. Listing tools works without a key, while tool calls need one. The docs describe a Streamable HTTP server and narrowed /mcp/<scope> and /mcp/discover variants.

jeanslabs.vercel.app Streamable HTTP Personal key in the URL (/mcp?key=bi_...) or Authorization: Bearer Server not checked yet Reviewed 2026-11-16
About

Where it fits

Biologists and bioinformatics developers who want reproducible cloning, primer and sequence calculations inside an agent.

  • Design primers or CRISPR guides.
  • Verify Sanger results and run qPCR calculations.
  • Align sequences or build a phylogeny.

A remote MCP server advertises tools to your client. The provider controls the tools, the data they can reach, and the permissions they need. Read the provider's docs before you use it with private data.

Install

Connect Jean with your personal key

Get a personal key at the provider's /connect page with Google or an invitation code. Tools/list works without a key; tool calls do not. The key can also be sent as Authorization: Bearer.

  1. Get a personal key

    Open /connect and sign in with Google or an invitation code. Copy the bi_ key.

  2. Add the keyed URL

    The key goes in the address so the client carries it to tool calls.

    claude mcp add --transport http jean-by-melad-labs "https://jean.meladlabs.workers.dev/mcp?key=bi_..."

Follow the provider's setup steps above, then connect the server in your client. The provider controls the endpoint, required credentials, and permissions.

Connection

Endpoint and configuration

Endpoint
https://jeanslabs.vercel.app/mcp
Host
jeanslabs.vercel.app · /mcp
Transport
Streamable HTTP
Authentication
Personal key in the URL (/mcp?key=bi_...) or Authorization: Bearer
Server name
jean-by-melad-labs
Listing type
Community or directory listing

The installer uses the server name jean-by-melad-labs. If you add the endpoint by hand, keep the same name so the guide and your config match.

Verification

Check the connection

After you add the server, confirm that the client can see its tools and that one small request returns what the provider describes.

  1. 1
    Open the tool list.

    Restart the client or start a new session. Confirm that jean-by-melad-labs appears and that the tools match the provider documentation.

  2. 2
    Run one small request.

    Start with: Design primers or CRISPR guides. Check the result before you give the server more access.

  3. 3
    Check permissions.

    Review the OAuth scopes or API-key permissions, then remove the server and revoke its token when you no longer need it.

Server not checked yet

We checked the provider's page, not the MCP connection itself. No MCP sign-in or tool call was attempted. A provider page is linked but was not included in the automated check. Open it before setup.

Troubleshooting

Common failure modes

These are the problems to check first. If the provider changes its endpoint or authentication flow, use its documentation as the source of truth.

  • Authentication returns 401 or 403. Check the key, its environment variable, and the permissions attached to it.
  • The key works in the provider dashboard but not in the client. Confirm the client sends it in the header the provider expects.
  • Your client does not support Streamable HTTP. Use a client that does, and confirm the provider's current endpoint and transport in its docs.
Safety

Before you connect

Remote means provider access
  • The provider can see the requests and data your agent sends through the server.
  • Review OAuth scopes and API-key permissions. Start read-only if the provider offers it.
  • Use project scope for repository-specific servers; use global scope for personal tools.
  • Remove the server and revoke its token when you stop using it.
Review path

Check the connection before a real task

These guides cover the decisions that a provider description cannot answer: endpoint ownership, scopes, tool access, and a read-only test.

Reference

Provider documentation

Setup requirements, available tools, and rate limits live with the provider. Use the source link as the authority for this server.

Jean by Melad Labs documentationhttps://jeanslabs.vercel.app/docs/api/mcpGitHub repositoryhttps://github.com/genmnz/jean-by-melad-labs