# Build

> Building and running on Somnia: the Somnia CLI and MCP server for operating what you build, the Venue Kit (coming soon), every programmatic way in, and the developer guide for contracts, frameworks and deployment.

Somnia is an EVM chain, so applications are EVM contracts and the tools you already use work unchanged: Foundry, Hardhat, viem, ethers and any EVM wallet. This section covers what is specific to Somnia.

| Product | Status | What it does |
| --- | --- | --- |
| [Somnia CLI](./cli) | Live | Somnia Markets from the command line: reads, trades, keys and offline signing, scriptable and CI-friendly |
| [MCP server](./mcp) | Live | Read tools for markets, positions, prices and the Explorer, and a guide to every CLI command, for AI agents |
| [Venue Kit](./venue-kit) | Coming soon | A venue template, venue commands and an agent skill |

Start with `npx @somnia-chain/cli --help`, or add the MCP server to your agent with `claude mcp add somnia -- npx -y @somnia-chain/cli mcp`. Also here:

- **[API, MCP & SDK](./api)**: every programmatic way into Somnia, from JSON-RPC to the Markets SDK.
- **[Developer guide](/developer)**: contracts, frameworks, deployment, security and the JSON-RPC reference, copied from docs.somnia.network.
- **The [Markets SDK](/markets/somnia-markets)**: create venues and trade from code.

To point a coding agent at the docs, give it [llms-full.txt](https://new.docs.somnia.network/llms-full.txt).

---

Every page is also Markdown: append `.md` to its URL, or ask for `text/markdown`. Found something wrong, missing or confusing in these docs? Tell us: `POST /api/feedback` on this site with JSON `{"message": "…", "context": "what you were doing and what happened", "page": "…"}`, or a plain-text body. `GET /api/feedback` gives the JSON Schema. The team reads every one.