Connect Legend to an AI assistant

Connect an assistant to Legend to read your account, inspect positions and fills, and prepare an order for review in Legend. Your assistant uses the same account permissions and market identifiers as the Trading API.

Choose a connection

These connections use mainnet accounts. They have no paper or testnet mode. Client plans and organization policies can also limit installation.

Set up Claude

1. In Claude, open Customize → Connectors. Select Add custom connector. Some versions show this under Settings → Connectors.

2. Name the connector Legend and enter this server URL:

   Copy

   https://app.legend.trade/api/connectors/mcp
   

3. Use OAuth and Claude's published client identity when those settings are shown. Legend supports Claude's hosted identity; it does not accept arbitrary client registrations.

4. Connect, sign in to Legend, and review the account and requested permissions on the Legend consent page.

5. Start a new chat and ask the assistant to check your account identity before you use other tools.

On a Team or Enterprise plan, an organization owner may need to add the connector before members can connect their own accounts. A custom connector in Yours is not proof that it is available in the public directory.

Add the Legend plugin

The plugin adds workflows for account checks, fill and order review, and order preparation. It uses the same server URL as the connector.

1. Open the Legend plugin repository.
2. In Claude, open Customize → Plugins → Add → Add marketplace and enter many-legends/legend-ai-plugin.
3. Install Legend, open its Connectors tab, and connect your account through OAuth.

You can also upload a ZIP of the plugins/legend folder through Upload plugin. The ZIP must contain .claude-plugin/plugin.json at its root, or inside one top-level plugin folder.

The source repository is public. This does not mean that Anthropic has listed or verified the plugin. Live Claude Code authentication has not yet been verified; the repository records the supported setup and current limits.

Set up ChatGPT

For an account that can add custom remote MCP servers:

1. Open Plugins, select Add, and choose Add custom MCP server. The control can depend on your plan or organization settings.
2. Name the connection Legend and use https://app.legend.trade/api/connectors/mcp.
3. Select OAuth, connect, and complete Legend's sign-in and consent flow.
4. Create the connection as a plugin if ChatGPT offers that option, then select it in a new chat.
5. Ask for an account check to confirm which Legend account is connected.

Do not select an unrelated public plugin with a similar name. If the custom-server control is unavailable, ask your organization owner or contact support. A working custom connection does not establish a public directory listing.

Set up Muse

The current Muse integration uses Legend's REST API with an account-scoped API key. It does not use the Claude or ChatGPT OAuth setup.

1. Sign in to Legend and open Settings → Trading.

2. Create a dedicated API key. Turn off Allow trading for account reads. Enable it only if you intend to use supported execution operations.

3. In Muse's secure connector setup, use these values:

   Field	Value
   API URL	https://app.legend.trade
   OpenAPI URL	https://app.legend.trade/api/trading/v1/openapi.json
   Authentication	API key
   Key transport	Authorization header, Bearer
   Read-only test path	/api/trading/v1/account

4. Enter the key directly in the credential field. Do not paste it into a chat message.

5. Run the account test. It sends GET /api/trading/v1/account, reads the authorized account, and changes nothing.

6. Confirm the returned username and mainnet network before you use any other capability.

The dedicated key determines the account. Neither the assistant nor the caller can substitute another wallet. Muse directory review, business verification, and reviewer access are separate from this user setup.

First requests

Use fresh tool calls after installation or reconnection. For example:

• “Show my Legend username, network, and available-to-trade estimate.”
• “Show my open positions and open orders. Use the open-order filter.”
• “Show my latest three fills and their fees.”

The username must match the account you intended to connect. The available-to-trade value is an estimate; it is not the withdrawable amount or a promise that an order of that size will be accepted. See account balances.

What the connection can do

The default MCP endpoint provides six account and history tools plus order preparation:

Use status=open to check open orders. Follow pagination when has_more is true; a recent history page is not a complete account record.

The default endpoint does not place, change, or cancel orders. It does not move funds, start copy trading, or provide news search or market-research tools. An assistant can have other data sources, but it must not present their output as a Legend tool result.

Review a proposed order

Ask for a proposal only when you have chosen the market, side, base-asset size, exact limit price, and reduce-only setting. The tool supports perpetual GTC limit orders.

1. The assistant calls prepare_order and returns a Legend review link. No order is placed and no margin is reserved.
2. Open the link. Check the market, account, side, size, price, and order settings in Legend's Advanced trade form.
3. Review current funds, leverage, and market conditions. Submit the order through Legend if you want to proceed.

Proposal links expire after 15 minutes. If a link has expired, request a fresh proposal. Opening one from a non-mainnet account mode is blocked. See tools and order review.

Execution access and fees

An additional MCP resource, https://app.legend.trade/api/connectors/trading/mcp, supports permitted execution operations. It requires a trading scope and a trading-enabled underlying key. It is not the default setup above. Host policies can restrict it, and a custom connector does not establish directory approval for execution.

The MCP server does not add a separate Legend-site confirmation to every execution call. A host can provide its own approval controls. If you want each order reviewed in Legend, use the default endpoint and prepare_order.

Executed trades remain subject to Legend's fees, venue limits, funding, and margin requirements. A proposal does not reserve a price or waive those costs. See API rate limits and connector permissions.

Fix a connection problem

Revoke an associated API key in Settings → Trading to stop future API and MCP requests using that credential. This does not close positions or cancel existing orders.

Contact Legend support with the client name, error, and request ID. Never include a key, token, password, or wallet secret.