Use BiOS from Devin

Autonomous software engineer by Cognition

Works today

Devin supports MCP servers through its settings, including custom stdio servers. Once connected, Devin can fold BiOS into its sessions: prepare a dataset, kick off training, watch the run, and deploy the artifact.

Before you start

You need a BiOS API key. In your dashboard, open API Keys, click Create API Key, pick a permission preset, and copy the sk_live_ key. It is shown only once.

Node.js 18 or newer must be installed; the server runs with npx, so there is nothing else to install.

Setup

1
Open MCP settings in Devin
In the Devin web app, open Settings and find the MCP section (listed under integrations). Choose the option to add a custom MCP server.
2
Configure the BiOS server
Give it the name usfbios, transport stdio, and this command and environment. If Devin asks for a JSON config, use the standard block:
json
```
{
  "mcpServers": {
    "usfbios": {
      "command": "npx",
      "args": ["-y", "@usfbios/mcp-server"],
      "env": {
        "USFBIOS_API_KEY": "sk_live_your_api_key"
      }
    }
  }
}
```
Devin runs the server inside its own workspace, so Node.js is already available there.
3
Enable it and put it to work
Turn the server on for your sessions, then hand Devin a task that spans code and training, for example: "Clean up the eval dataset in data/, upload it to BiOS, and fine-tune Llama 3.1 8B with LoRA. Report the loss curve when it finishes."

Check that it works

The MCP section in Devin settings lists usfbios as connected.
In a session, ask Devin to check your BiOS wallet balance and confirm it reports your credits.

Try these prompts

“Search for Llama models under 13B parameters and recommend a GPU for LoRA fine-tuning”

“Upload ~/data/support-qa.jsonl and start an SFT job on Llama 3.1 8B with LoRA”

“What is the status of my running training jobs? Show the loss curve for the latest one”

“Deploy my finished fine-tune and give me the endpoint URL”

Your assistant has 38 BiOS tools in total. The tool reference documents each one.

Troubleshooting

Devin cannot reach the BiOS API from its workspace

Devin machines need outbound HTTPS access to api.usbios.ai. If your organization restricts Devin egress, allow that host.

The server never starts, or logs show "npx: command not found"

The MCP server runs on Node.js. Install Node 18 or newer from nodejs.org, restart your client, and try again. Run npx -y @usfbios/mcp-server in a terminal to confirm it starts (it waits for input; press Ctrl+C to exit).

Tools appear but every call fails with an authentication error

Check that USFBIOS_API_KEY is set to a key that starts with sk_live_ and has not expired. Keys are shown only once at creation, so if in doubt create a fresh one under Dashboard, then API Keys.

A tool call fails with a permission error

Your key may be scoped too narrowly. Ask the assistant to call introspect_api_key to see exactly which scopes the key has, then create a key with the preset you need (Read Only, Training, or Full Access).

Frequently asked questions

Devin works autonomously. How do I keep it from overspending?

Create a scoped API key with only the permissions the task needs, and keep a spending cap on your BiOS wallet. Devin can check the balance with get_wallet_balance before it launches jobs; every training job also runs a preflight cost estimate.

Does the exact settings path matter?

Cognition moves settings around as Devin evolves, but the config shape (command, args, env) is standard MCP and stays the same. Search Devin settings for "MCP" if the menu changed.