> ## Documentation Index
> Fetch the complete documentation index at: /docs/llms.txt
> Use this file to discover all available pages before exploring further.

> ## Agent Instructions
> To use Maglev from an agent, connect the MCP server at https://trymaglev.com/mcp. Parts catalog tools need no key. Make tools (make_start, check_manufacturability, get_quotes, place_order) need a Maglev key; see https://trymaglev.com/docs/quickstart.
> Never place an order without showing the person the exact final total and getting their explicit approval.

# Maglev MCP server for AI agents

> Connect any MCP client to https://trymaglev.com/mcp over streamable HTTP: 16 tools for custom-part quotes and orders plus a searchable hardware parts catalog.

The Maglev MCP server lets any agent that speaks the Model Context Protocol make custom parts and search off-the-shelf hardware. It runs at one URL over streamable HTTP, so there is nothing to install.

| | |
| - | - |
| Endpoint | `https://trymaglev.com/mcp` |
| Transport | Streamable HTTP (JSON-RPC over POST) |
| Auth | `Authorization: Bearer mgl_…` for Make tools. Parts tools work without a key |
| Tools | 16: four Make tools and twelve Parts tools. See [all tools](/docs/mcp/tools.md) |

## Connect a client

> [tab] Claude Code
>
> ```bash theme={null}
> claude mcp add --scope user --transport http maglev https://trymaglev.com/mcp \
>   --header "Authorization: Bearer YOUR_MAGLEV_KEY"
> ```
>
> Or run the one-command setup in the [quickstart](/docs/quickstart.md), which signs you in and adds this for you.

> [tab] Codex
>
> Add to `~/.codex/config.toml`:
>
> ```toml theme={null}
> [mcp_servers.maglev]
> url = "https://trymaglev.com/mcp"
> http_headers = { Authorization = "Bearer YOUR_MAGLEV_KEY" }
> ```

> [tab] Any HTTP client
>
> Send JSON-RPC to the endpoint. For example, list the tools:
>
> ```bash theme={null}
> curl -X POST https://trymaglev.com/mcp \
>   -H "Content-Type: application/json" \
>   -H "Accept: application/json, text/event-stream" \
>   -d '{"jsonrpc":"2.0","id":1,"method":"tools/list"}'
> ```

Get a key from the [dashboard](https://trymaglev.com/dashboard#keys). See [Authentication](/docs/authentication.md).

## The make flow

For custom parts from CAD, an agent calls the four Make tools in order:

**1. make\_start**

Takes the local file names and returns one upload command per file for the agent to run with its shell tool, plus how each file will be routed.

**2. check\_manufacturability**

Runs each file through its manufacturer's design check in parallel. Returns blockers and warnings per file and an overall `ready_to_quote`.

**3. get\_quotes**

Asks every shop that makes each file's process, in parallel. Returns every offer in one shape. Show them all to the person; do not pick a winner.

**4. place\_order**

First call without `approved_total_usd` returns the final total and charges nothing. Call again with the exact total only after the person approves it.

> [!WARNING]
>
> `place_order` with an approved total can become a real paid order. For sheet metal at RMFG it is charged to Maglev's card on file. Always show the person the exact total first and quote their approval in `approval_note`.

The same flow over HTTP is in [Make parts from CAD](/docs/how-to/make-parts-from-cad.md).


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.