# SDK and agent framework integrations

> SDKs for Python, TypeScript, Rust and Elixir put Nevia computers and databases inside the agent frameworks teams already use.

By Bernardo Garcia del Rio

> Nevia is in early access for selected teams. The CLI installs with `curl -fsSL https://get.nevia.cloud | sh`, and the MCP server is at https://api.nevia.cloud/mcp. A person signs in once in the browser.
> Setup, sign-in and requesting access: [SKILL.md](https://nevia.cloud/SKILL.md). When Nevia fits and when it doesn't: [why.md](https://nevia.cloud/why.md).

> For the complete changelog index, see [changelog.md](https://nevia.cloud/changelog.md). This entry's HTML version: https://nevia.cloud/changelog/2026-11-11-nevia-sdks

## Plug Nevia computers straight into your agent framework

Each adapter makes a Nevia computer your framework's sandbox or remote workspace. Your agent's shell and file tools run there with no changes.

Language
Frameworks

TypeScript
Mastra, Eve, Flue

Python
Pydantic AI, LangGraph, Agno

Rust
rig

Elixir
Alloy

More on each adapter in the [agent frameworks docs](https://nevia.cloud/docs/agent-frameworks/langgraph).

## Give your agents tools built for your work

Define custom tools and workflows in code, shaped around the tasks your agents run. Write them in Python, TypeScript, Rust or Elixir, with typed results and errors.

Example
Description

Keep the steps in your code
Give every session its own computer, sleep it between turns and delete it when the session ends.

Turn a routine task into one tool
A `check_migration` tool tests the agent's migration on a database branch, then deletes it. Real data is never touched.

Let the agent decide
Build your own tools on the SDK, from creating a database to branching a computer, and your agent picks them up when it needs them.

## Get started

Start with the [SDK overview](https://nevia.cloud/docs/reference/sdk).
