> ## Documentation Index > Fetch the complete documentation index at: https://docs.zyf.ai/llms.txt > Use this file to discover all available pages before exploring further. # Use Zyfai with AI > Connect the hosted Zyfai MCP server to Claude, ChatGPT, Cursor, Claude Code, or another Streamable HTTP MCP client. Use Zyfai from an AI assistant to discover yield opportunities, compare strategies, inspect your portfolio, track earnings, and prepare supported account actions in natural language. > [!NOTE] > > **Hosted MCP endpoint:** `https://mcp.zyf.ai/mcp`\ > **Official MCP Registry ID:** `io.github.ondefy/zyfai` ## Choose a client | Client | Availability | Best for | | - | - | - | | **Claude** | Connector support on supported Claude plans and clients | The simplest conversational Zyfai experience | | **Cursor** | Desktop | Developers and technical users | | **Claude Code** | Desktop terminal | Developers working from the command line | | **Grok and Grok Bot** | Grok connectors and Grok Bot | Background, repeat, and multi-step agent workflows | | **ChatGPT** | Limited Zyfai preview; currently desktop-only | Testing the Zyfai ChatGPT app before public distribution | | **Other MCP clients** | Any client supporting remote Streamable HTTP | Custom agents and integrations | > [!WARNING] > > Availability and menu labels are controlled by each AI client and can vary by plan, workspace, device, and client version. The current Zyfai ChatGPT app is not yet publicly installable. Agents that open [zyf.ai/skill.md](https://zyf.ai/skill.md) should fetch this page and follow it in the same conversation. Do not only return the link. ## Setup Identify which client the user wants. Distinguish **Claude** from **Claude Code**, and **Grok** from **Grok Bot**. Reuse an existing authenticated Zyfai connection. Otherwise follow only the matching section below. Reading this page does not install a connector. If setup needs the user, give the steps and wait for authentication before verifying access. Remote MCP is one Streamable HTTP endpoint: `https://mcp.zyf.ai/mcp`. Official registry ID: `io.github.ondefy/zyfai`. The harness manages OAuth against Zyfai's authorization server on `https://api.zyf.ai`. Do not invent a custom OAuth flow, and do not ask for a seed phrase, private key, or token in chat. Supported execution chains are Ethereum, Base, and Arbitrum. ## What you can ask Zyfai The available tools depend on whether the client has an authenticated Zyfai session. * Discover and compare conservative or aggressive yield opportunities * Review supported chains, assets, protocols, pools, APY, TVL, and risk information * Inspect your Zyfai portfolio and active positions * Review earnings, history, and rebalancing information * Prepare supported deposits and other account actions when enabled Connecting the MCP server does not transfer assets, expose a private key, or give the AI custody of your wallet. Personal data and account actions require authentication. Any wallet transaction that requires your signature remains subject to your explicit approval. ## Claude Use this for Claude on the web, desktop, and mobile. Claude Code is a separate client, below. 1. Open **Customize** in the left sidebar. 2. Open the **Connectors** tab. 3. Add a custom connector. Claude opens an **Add custom connector** dialog (`modal=add-custom-connector` on the connectors page). 4. Name it **Zyfai**. 5. Set the remote MCP URL to `https://mcp.zyf.ai/mcp`. That field is the HTTPS address where the server accepts MCP requests. 6. Select **Continue**. 7. Complete Zyfai sign-in when Claude asks. 8. On **Tool permissions**, set **Read-only tools** to **Always allow**. Leave **Write/delete tools** on ask-each-time. That write group includes deposit, withdraw, and settings changes, and Claude applies one choice to the whole group. 9. Start a new conversation and make sure the Zyfai connector is enabled. The Customize entry, tab names, and button label can vary by plan and client version. A link that includes `claude.ai/customize/connectors/yours/` plus an id is private to that account. Do not reuse someone else's id. If **Add custom connector** is missing, the account plan or workspace may not allow custom connectors. > [!TIP] > > Start with: **“Using Zyfai, show me conservative USDC opportunities on Base and explain the differences.”** ## Cursor Add the hosted server to your Cursor MCP configuration: ```json theme={null} { "mcpServers": { "zyfai": { "url": "https://mcp.zyf.ai/mcp", "transport": "http" } } } ``` Reload MCP servers in Cursor, confirm that **zyfai** is connected, and open a new agent conversation. ## Claude Code Run this command in a terminal outside an active Claude Code session: ```bash theme={null} claude mcp add --transport http zyfai https://mcp.zyf.ai/mcp ``` Then start Claude Code and verify the server: ```bash theme={null} claude mcp list ``` ## Grok and Grok Bot Grok supports custom MCP connectors. Connect Zyfai once, then use it from Grok conversations and supported Grok Bot workflows. 1. Open [grok.com/connectors](https://grok.com/connectors). 2. Select **New Connector**. 3. Select **Custom**. 4. Name the connector **Zyfai** and enter `https://mcp.zyf.ai/mcp`. 5. Complete authentication if requested. 6. In a Grok conversation, ask Grok to use the Zyfai connector. 7. In Grok Bot, attach the installed connector with `@` when needed. > [!TIP] > > Grok Bot is the better fit for longer-running or repeat workflows. Grok web also works for ad hoc conversations, although tool-heavy requests can take longer to complete. ## ChatGPT Zyfai currently has a limited-preview ChatGPT app. The present private installation is marked **Desktop only** and is available only to accounts or workspaces that have been granted access. Public installation and general mobile availability are not yet available. This page will be updated with the public installation link when distribution is enabled. Do not use the ChatGPT preview to execute deposits or other writes. If you already have access: 1. Open the Zyfai app page in ChatGPT on desktop. 2. Select **Add app**. 3. Start a new chat and invoke Zyfai from the app or tools menu. 4. Complete authentication when ChatGPT requests it. > [!NOTE] > > Not seeing an Add button on mobile is expected for the current private preview. ## Other MCP clients Use the production endpoint with a client that supports remote **Streamable HTTP**: ```text theme={null} https://mcp.zyf.ai/mcp ``` A generic configuration looks like this: ```json theme={null} { "mcpServers": { "zyfai": { "url": "https://mcp.zyf.ai/mcp" } } } ``` Client-specific fields vary. Use Streamable HTTP rather than an STDIO command when the client supports remote MCP servers directly. ## Try these prompts ### Discover opportunities > Using Zyfai, show me conservative USDC opportunities on Base. Compare APY, TVL, protocol, and risk. ### Change the comparison > Now compare those with the aggressive strategy and explain the additional risk rather than recommending purely by APY. ### Review your account > Show my current Zyfai positions and earnings. Do not prepare any transaction. ### Prepare a deposit > Help me prepare a 1 USDC deposit on Base using the conservative strategy. Explain each step and ask before anything requiring a wallet signature. ## Authentication and approvals Zyfai separates general discovery from personal account access. * Discovery tools can retrieve public opportunity and protocol information. * Portfolio, position, earnings, and history tools require an authenticated user session. * Supported write flows may return a Zyfai signing URL or ask the connected client to continue authentication. * The assistant cannot see your seed phrase or private key. * Never paste a seed phrase, private key, or raw wallet credential into a chat. * Review the chain, asset, amount, strategy, destination, and wallet request before signing. ## First connection checklist This guide is self-contained. You do not need a prompt from a previous chat. 1. Reuse an authenticated connection or complete the matching client setup above. Let the harness manage MCP initialization, OAuth, and credential storage. If the server returns HTTP 401 with `WWW-Authenticate`, complete that sign-in before calling tools. 2. Discover tools with `tools/list`. Use the exact tool names and schemas the connection exposes. 3. Call `find_opportunities` for conservative USDC on Base. 4. When the user wants their own account, call `get_portfolio`. An empty portfolio is a valid result. `get_account` and `get_positions` are the other authenticated reads. 5. Report that the connection was verified only after a read succeeds with no tool error. If no Zyfai tools are available after setup, report that verification is blocked. Do not claim success, and do not bypass the connector with raw HTTP. ## Deposits and other writes Do not move funds unless the user asks. Connecting Zyfai is not permission to deposit, withdraw, or change strategy. `prepare_deposit` returns an `actionId` and a `signingUrl`. The user opens that link in a normal browser and signs on the Zyfai deposit page. Do not call `window.ethereum` or send a transaction from inside the chat, a plugin iframe, or an MCP App widget. Omit `spendToken` when the wallet already holds the collateral on `chainId`. The page transfers that token. Set `spendToken` (a contract address, a collateral symbol, or `ETH`) and optional `spendChainId` to prepare a preswap when the wallet holds a different token. `amount` is then in that token's least units. The page performs the preswap and registers the collateral that arrives. That preswap uses the execution API default slippage of 200 basis points (maximum 500). The signing page does not take a custom `slippageBps`. Direct SDK calls can pass `slippageBps` to `sendDeposit` or `sendSwapDeposit`. Do not ask for a seed phrase or private key. Return `signingUrl` to the user and ask them to open it in their browser. End the turn; do not call `wait_for_deposit_handover`, `get_deposit_status`, or any other tool in that same turn. After they have seen the link, call `wait_for_deposit_handover` with the `actionId` (it blocks until signing completes and, by default, until custody credit). Alternatively poll `get_deposit_status` with the `actionId`. If the signing page did not register the transaction, call `register_deposit` with the transaction hash the user confirms. Withdrawals and settings changes use the authenticated write tools the server lists (`withdraw`, `register_withdraw`, `update_settings`, and `set_strategy` when write tools are enabled). Session keys cannot send funds to an arbitrary address. Withdrawals return to the owner's account. **Strategy changes.** To change yield strategy (for example to `yieldmaxxing`), call `set_strategy` or `update_settings` with `strategy` only. The server uses the SDK to persist the strategy and **auto-select protocols** for that tier on all managed assets (or on one asset if you pass `asset`). Do not guess or pass protocol IDs unless you are doing advanced manual protocol tuning without a strategy change. Do not pass `strategy` and `protocols` in the same `update_settings` call. ## Adopt this guide as a skill Reading this URL supplies instructions for the current task. It does not install a skill for later chats. If the user asks to make it reusable, use the harness's documented skill installation and confirm the installed skill can be discovered. For a harness that accepts standalone `SKILL.md` files, save this guide with the frontmatter below, then the title and body. Record the source URL `https://docs.zyf.ai/docs/sdk/mcp-server.md` and the retrieval date. Recheck the source before refreshing a saved copy. Do not treat an installed skill as a frozen API contract. ```yaml theme={null} --- name: zyfai-for-agents description: >- Connect Zyfai MCP, discover yield opportunities, inspect a portfolio, prepare a supported deposit, and wait for deposit handover after signing. Use for Zyfai setup, connection verification, or disconnecting. --- ``` The short entry agents paste from social posts is [https://zyf.ai/skill.md](https://zyf.ai/skill.md). Keep that bootstrap, and keep this page as the maintained reference. Programmatic SDK integration stays on the [agent quickstart](https://docs.zyf.ai/docs/sdk/agent-quickstart.md). ## Troubleshooting ### The client cannot connect * Confirm the URL is exactly `https://mcp.zyf.ai/mcp`. * Confirm the client supports remote Streamable HTTP MCP servers. * Remove a trailing space or duplicated path from the URL. * Check the [Zyfai MCP health endpoint](https://mcp.zyf.ai/health). ### Tools are missing * Start a new conversation after connecting the server. * Confirm Zyfai is enabled for that conversation. * Reload or refresh the client's MCP connections. * Complete authentication if you are requesting portfolio or account-specific tools. ### Claude or ChatGPT shows an authentication prompt Complete the Zyfai authentication flow in the window opened by the client, then return to the conversation. Do not copy wallet secrets into the chat. ### HTTP 401 or insufficient scope Reconnect through the client's Zyfai sign-in and approve the requested access. Do not paste tokens into chat. A successful `tools/list` does not prove every later call is authorized. ### ChatGPT says Desktop only That is the expected status of the current private preview. Use ChatGPT on desktop, or use Claude or another supported MCP client until public ChatGPT distribution is available. ### The assistant prepares the wrong strategy or amount State the asset, chain, amount, and strategy explicitly. Before signing, verify all four values in the Zyfai confirmation flow. ## Build with Zyfai For application-level integrations, use the [Zyfai SDK quickstart](https://docs.zyf.ai/docs/sdk/getting-started.md). To inspect or self-host the MCP server, see [github.com/ondefy/zyfai-mcp-server](https://github.com/ondefy/zyfai-mcp-server). This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.