# What is MCP? (/docs/what-is-mcp)



The **Model Context Protocol (MCP)** is an open standard for connecting AI
applications to external tools and data through one uniform interface. Think of it as a **USB-C port for AI**: instead of every
app inventing its own integration, any MCP-compatible client can plug into any
MCP server and immediately use what it offers. The protocol is documented at
[modelcontextprotocol.io](https://modelcontextprotocol.io).

The Delta Exchange MCP server is one such server. It exposes Delta's market data,
your account data and trading as MCP tools, so any compatible AI client can use
it in plain language.

## The three pieces [#the-three-pieces]

An MCP setup is always three parts:

1. **Client (host):** the AI application you already use, such as Claude Desktop,
   Cursor, or Claude Code. It holds the model and decides when to call a tool.
2. **Server:** a small program that advertises a set of tools and answers calls.
   Here that is `delta-exchange-mcp`.
3. **Upstream resource:** whatever the server talks to. Here that is Delta
   Exchange's REST API.

```mermaid
flowchart LR
  subgraph local["Your machine"]
    direction TB
    client["AI client<br/>(Claude Desktop, Cursor, Claude Code)"]
    server["delta-exchange-mcp<br/>local subprocess<br/>reads keys from local env"]
  end
  api["Delta Exchange API<br/>(market + account data)"]
  client -- "MCP over stdio<br/>tool calls + results" --> server
  server -- "HTTPS, HMAC-signed<br/>bounded by your key permission" --> api
  api -- "JSON" --> server
```

The client and server speak MCP to each other; the server speaks Delta's normal
HTTPS API to Delta. Your credentials are used only on that last hop, from your
machine to Delta. They never reach the model.

## Tools, and who decides to call them [#tools-and-who-decides-to-call-them]

A server advertises **tools**: named operations with typed parameters, like
`get_ticker(symbol)` or `get_positions(...)`. You almost never name a tool
yourself. You ask a question in plain language ("what's BTC funding right now?"),
the model picks the right tool and arguments, the server runs it, and the model
reads the result back and answers you.

That is why the same Delta server works identically across every client: the
tools are the contract, and each client wires them to its own model.

<Callout title="You stay in plain language">
  The tool names and parameters in the [Tool Reference](/docs/tools) are there for
  when you build agents or want to know exactly what runs. For everyday use, you
  just ask.
</Callout>

## How this server connects [#how-this-server-connects]

The Delta Exchange server runs locally:

* It runs as a **subprocess on your own machine** and talks to your client over
  stdio. It is not a hosted service.
* Your API key and secret are read from your **local environment** at launch and
  used only to sign requests sent directly to Delta's API.
* They **never** pass through the AI model or any Delta server beyond the normal
  trading API.

See [Security](/docs/security) for the full data-flow and key model.

## Why MCP for trading [#why-mcp-for-trading]

* **Ask, don't integrate.** Get live market and account data in plain language,
  with no glue code, SDK wiring, or dashboards to build.
* **Write once, use everywhere.** One server works across every MCP client, so a
  prompt that works in Claude Desktop works in Cursor or Claude Code too.
* **No key, no account.** With no credentials every tool is a read-only `GET`
  against public market data. A key registers the account and trading tools, and
  the key's own permission decides what they may do. The server never has a
  withdrawal path.
* **Keys stay local.** Credentials are held by whatever installed the server —
  the bundle's own settings, your editor's secret storage, or your client config
  — and used only on your machine. Nothing sensitive flows to the model.
* **Composable.** Drop the same tools into an agent, a notebook, or a scheduled
  job for monitoring, P\&L, and reconciliation.

## Supported clients [#supported-clients]

The server works with any MCP-compatible client, including **Claude Desktop,
Codex, Claude Code, Cursor, OpenClaw, Antigravity, Grok Build**, and more.
Per-client setup is in the [Quickstart](/docs).

<Cards>
  <Card title="Quickstart" href="/docs" description="Install and connect your client in two minutes." />

  <Card title="Tool Reference" href="/docs/tools" description="Every tool, its parameters, and examples." />
</Cards>

<Callout type="warn" title="Not investment advice">
  Output is generated by an AI model and can be inaccurate, incomplete, or
  non-deterministic. It is **not investment advice**. Trading crypto derivatives
  involves substantial risk. Delta Exchange is registered with the Financial
  Intelligence Unit (FIU), Govt. of India.
</Callout>