Bio Lm TypeScript MCP Server

It is generated with Stainless.

Installation

Building

Because it's not published yet, clone the repo and build it:

git clone [email protected]:BioLM/biolm-models-mcp.git
cd biolm-models-mcp
./scripts/bootstrap
./scripts/build

Running

# set env vars as needed
export BIOLMAI_TOKEN="My API Key"
export BIO_LM_ACCESS_TOKEN="My Access Token"
node ./packages/mcp-server/dist/index.js

[!NOTE] Once this package is published to npm, this will become: npx -y @biolm/biolm-models-mcp

Via MCP Client

Build the project as mentioned above.

There is a partial list of existing clients at modelcontextprotocol.io. If you already have a client, consult their documentation to install the MCP server.

For clients with a configuration JSON, it might look something like this:

{
  "mcpServers": {
    "biolm_biolm_models_api": {
      "command": "node",
      "args": ["/path/to/local/biolm-models-mcp/packages/mcp-server"],
      "env": {
        "BIOLMAI_TOKEN": "My API Key",
        "BIO_LM_ACCESS_TOKEN": "My Access Token"
      }
    }
  }
}

Code Mode

This MCP server is built on the "Code Mode" tool scheme. In this MCP Server, your agent will write code against the TypeScript SDK, which will then be executed in an isolated sandbox. To accomplish this, the server will expose two tools to your agent:

• The first tool is a docs search tool, which can be used to generically query for documentation about your API/SDK.

• The second tool is a code tool, where the agent can write code against the TypeScript SDK. The code will be executed in a sandbox environment without web or filesystem access. Then, anything the code returns or prints will be returned to the agent as the result of the tool call.

Using this scheme, agents are capable of performing very complex tasks deterministically and repeatably.

Running remotely

Launching the client with --transport=http launches the server as a remote server using Streamable HTTP transport. The --port setting can choose the port it will run on, and the --socket setting allows it to run on a Unix socket.

Authorization can be provided via the Authorization header using the Bearer scheme.

Additionally, authorization can be provided via the following headers: | Header | Equivalent client option | Security scheme | | ----------------- | ------------------------ | --------------- | | x-biolmai-token | apiKey | tokenAuth |

A configuration JSON for this server might look like this, assuming the server is hosted at http://localhost:3000:

{
  "mcpServers": {
    "biolm_biolm_models_api": {
      "url": "http://localhost:3000",
      "headers": {
        "Authorization": "Bearer <auth value>"
      }
    }
  }
}