# Connect to Claude Desktop Source: https://docs.shuriken.trade/agent-kit/connect-claude Step-by-step guide to connect your Shuriken Agent Key to Claude Desktop. This guide gets Claude Desktop connected to Shuriken in about 2 minutes. Once set up, you can ask Claude to scan your alpha, research tokens, check your portfolio, and trade - all from a conversation. **Time required:** About 2 minutes. ## Prerequisites * [Claude Desktop](https://claude.ai/download) installed (available for macOS and Windows) * [Node.js](https://nodejs.org) installed (required for the `mcp-remote` bridge) * A Shuriken Agent Key ([create one here](/agent-kit/create-agent-key) if you haven't already) ## Step-by-step setup If you just created your key, copy it from the setup screen. It starts with `sk_`. If you already closed that screen, you'll need to [create a new key](/agent-kit/create-agent-key) - keys are only shown once. Claude Desktop stores its MCP config in a file called `claude_desktop_config.json`. **Option A: Through Claude Desktop settings** 1. Open Claude Desktop 2. Click the **Claude** menu in your system menu bar (top of screen on macOS, top of window on Windows) 3. Select **Settings** 4. Go to the **Developer** tab 5. Click **Edit Config** This opens the config file directly. **Option B: Open the file manually** ``` ~/Library/Application Support/Claude/claude_desktop_config.json ``` Open Finder, press `Cmd+Shift+G`, and paste the path above. ``` %APPDATA%\Claude\claude_desktop_config.json ``` Press `Win+R`, paste the path above, and hit Enter. If the file doesn't exist, create it. The full path is usually: `C:\Users\YOUR_USERNAME\AppData\Roaming\Claude\claude_desktop_config.json` Paste the following into your config file. Replace `YOUR_AGENT_KEY` with the key you copied in step 1. **Why `mcp-remote`?** Claude Desktop supports remote MCP servers through its built-in Connectors feature (Settings > Connectors), but that requires OAuth authentication. Since Shuriken uses API key authentication via custom headers, the `mcp-remote` bridge is needed to pass those headers through `claude_desktop_config.json`. **Node.js required.** The config below uses `npx` to run the `mcp-remote` bridge. If you don't have [Node.js](https://nodejs.org) installed, this step will fail silently. **If the file is empty or doesn't exist**, paste this entire block: ```json claude_desktop_config.json theme={null} { "mcpServers": { "Shuriken": { "command": "npx", "args": [ "-y", "mcp-remote", "https://api.shuriken.trade/mcp", "--header", "Authorization: AgentKey YOUR_AGENT_KEY" ] } } } ``` ```json claude_desktop_config.json theme={null} { "mcpServers": { "Shuriken": { "command": "cmd", "args": [ "/c", "npx", "-y", "mcp-remote", "https://api.shuriken.trade/mcp", "--header", "Authorization: AgentKey YOUR_AGENT_KEY" ] } } } ``` Windows can't execute `npx` directly as a process β€” it's a `.cmd` script, not a real executable. The `cmd /c` wrapper is the official workaround. This is a known Claude Desktop limitation, not specific to Shuriken. **If your config already has other MCP servers or preferences**, add the `"Shuriken"` block inside the existing `"mcpServers"` object. Keep any other configuration (like `preferences`) as-is: ```json claude_desktop_config.json theme={null} { "mcpServers": { "your-existing-server": { "...": "..." }, "Shuriken": { "command": "npx", "args": [ "-y", "mcp-remote", "https://api.shuriken.trade/mcp", "--header", "Authorization: AgentKey YOUR_AGENT_KEY" ] } }, "preferences": { "...your existing preferences...": "..." } } ``` ```json claude_desktop_config.json theme={null} { "mcpServers": { "your-existing-server": { "...": "..." }, "Shuriken": { "command": "cmd", "args": [ "/c", "npx", "-y", "mcp-remote", "https://api.shuriken.trade/mcp", "--header", "Authorization: AgentKey YOUR_AGENT_KEY" ] } }, "preferences": { "...your existing preferences...": "..." } } ``` Make sure there's a comma between each server entry. Missing commas are the most common cause of connection failures. Save the file, then **completely quit and relaunch Claude Desktop**. The MCP connection won't activate until you restart. On macOS, make sure to quit from the menu bar (Claude > Quit Claude), not just close the window. After restarting, look for an **MCP tools indicator** (a small hammer icon) in the bottom-right corner of the chat input box. Click it to see the available Shuriken tools. Try a test prompt: ``` What tokens were called in my Discord today? ``` ``` What's my SOL balance? ``` Claude will ask for your approval before using each tool for the first time. Click **Allow** to let it proceed. If you see results, you're all set. Claude is now connected to Shuriken. ## Troubleshooting * Make sure you saved the config file * Make sure you fully quit and restarted Claude Desktop * Check for JSON syntax errors (missing commas, mismatched brackets) * Verify that Node.js is installed by running `node --version` in your terminal * Check Claude's logs for errors: * **macOS:** `~/Library/Logs/Claude/mcp.log` * **Windows:** `%APPDATA%\Claude\logs\mcp.log` * Double-check that your Agent Key is correct (starts with `sk_`) * Make sure you included the `AgentKey ` prefix before the key (with a space) * Check that the key hasn't been revoked on the [Agent Keys dashboard](https://app.shuriken.trade/agents) This usually means Windows can't find `npx` as a direct executable. Make sure your config uses the `cmd /c` wrapper: ```json theme={null} "command": "cmd", "args": ["/c", "npx", "mcp-remote", ...] ``` Also verify that Node.js is installed and `npx` is available in your PATH by running `npx --version` in Command Prompt. The first time Claude Desktop starts with this config, `npx` downloads the `mcp-remote` package in the background. This can take 10-30 seconds with no visible feedback. Subsequent launches will be fast since the package is cached. This is normal. Claude Desktop asks you to approve tool usage for safety. You can click **Allow for this chat** to approve all tool calls in the current conversation. # Connect to Claude Code Source: https://docs.shuriken.trade/agent-kit/connect-claude-code Step-by-step guide to connect your Shuriken Agent Key to Claude Code. This guide gets Claude Code connected to Shuriken in about a minute. Once set up, you can ask Claude to scan your alpha, research tokens, check your portfolio, and trade - all from the terminal. **Time required:** About 1 minute. ## Prerequisites * [Claude Code](https://docs.anthropic.com/en/docs/agents-and-tools/claude-code/overview) installed * A Shuriken Agent Key ([create one here](/agent-kit/create-agent-key) if you haven't already) ## Step-by-step setup If you just created your key, copy it from the setup screen. It starts with `sk_`. If you already closed that screen, you'll need to [create a new key](/agent-kit/create-agent-key) - keys are only shown once. Claude Code supports native HTTP transport, so no bridge or extra dependencies are needed. This works the same on macOS, Windows, and Linux. **Option A: CLI command (recommended)** Run this in your terminal, replacing `YOUR_AGENT_KEY` with the key you copied in step 1: ```bash theme={null} claude mcp add --transport http Shuriken https://api.shuriken.trade/mcp \ --header "Authorization: AgentKey YOUR_AGENT_KEY" ``` **Option B: Edit `.mcp.json` manually** Add the following to your `.mcp.json` file (in your project root or `~/.claude/.mcp.json` for global access). Replace `YOUR_AGENT_KEY` with your key. **If the file is empty or doesn't exist**, paste this entire block: ```json .mcp.json theme={null} { "mcpServers": { "Shuriken": { "type": "http", "url": "https://api.shuriken.trade/mcp", "headers": { "Authorization": "AgentKey YOUR_AGENT_KEY" } } } } ``` **If you already have other MCP servers**, add the `"Shuriken"` block inside the existing `"mcpServers"` object: ```json .mcp.json theme={null} { "mcpServers": { "your-existing-server": { "...": "..." }, "Shuriken": { "type": "http", "url": "https://api.shuriken.trade/mcp", "headers": { "Authorization": "AgentKey YOUR_AGENT_KEY" } } } } ``` Make sure there's a comma between each server entry. Missing commas are the most common cause of connection failures. Start a new Claude Code session and try one of these prompts: ``` What tokens were called in my Discord today? ``` ``` What's my SOL balance? ``` Claude will ask for your approval before using each tool for the first time. Type **y** to let it proceed. If you see results, you're all set. Claude Code is now connected to Shuriken. ## Troubleshooting * If you used the CLI command, start a new Claude Code session for the changes to take effect * If you edited `.mcp.json` manually, check for JSON syntax errors (missing commas, mismatched brackets) * Make sure the file is in the right location (project root for project-level, `~/.claude/.mcp.json` for global) * Run `claude mcp list` to see if Shuriken is registered * Double-check that your Agent Key is correct (starts with `sk_`) * Make sure you included the `AgentKey ` prefix before the key (with a space) * Check that the key hasn't been revoked on the [Agent Keys dashboard](https://app.shuriken.trade/agents) # Connect to Cursor Source: https://docs.shuriken.trade/agent-kit/connect-cursor Step-by-step guide to connect your Shuriken Agent Key to Cursor. This guide gets Cursor connected to Shuriken in about 2 minutes. Once set up, you can ask your AI to scan alpha, research tokens, check your portfolio, and trade - all from the chat panel. **Time required:** About 2 minutes. ## Prerequisites * [Cursor](https://cursor.com) installed on your computer with a **Pro plan or higher** (MCP requires Agent mode, which is not available on the free plan) * A Shuriken Agent Key ([create one here](/agent-kit/create-agent-key) if you haven't already) ## Step-by-step setup If you just created your key, copy it from the setup screen. It starts with `sk_`. If you already closed that screen, you'll need to [create a new key](/agent-kit/create-agent-key) - keys are only shown once. You need to edit a file called `mcp.json`. This is where Cursor stores its MCP server connections. **Option A: Use the Command Palette (recommended)** 1. Open Cursor 2. Press `Ctrl+Shift+P` (Windows/Linux) or `Cmd+Shift+P` (macOS) 3. Type **MCP** and select **"Cursor Settings: Open MCP Settings"** 4. This opens your `mcp.json` file **Option B: Open the file manually** The file lives in your home directory: ``` C:\Users\YOUR_USERNAME\.cursor\mcp.json ``` Replace `YOUR_USERNAME` with your Windows username. Quick way to get there: press `Win+R`, type `%USERPROFILE%\.cursor` and hit Enter. Look for `mcp.json`. If it doesn't exist, create it. ``` ~/.cursor/mcp.json ``` Open Finder, press `Cmd+Shift+G`, and paste the path above. ``` ~/.cursor/mcp.json ``` Paste the following into your `mcp.json` file. Replace `YOUR_AGENT_KEY` with the key you copied in step 1. **If the file is empty or doesn't exist**, paste this entire block: ```json mcp.json theme={null} { "mcpServers": { "Shuriken": { "url": "https://api.shuriken.trade/mcp", "headers": { "Authorization": "AgentKey YOUR_AGENT_KEY" } } } } ``` **If you already have other MCP servers**, add the `"Shuriken"` block inside the existing `"mcpServers"` object: ```json mcp.json theme={null} { "mcpServers": { "your-existing-server": { "...": "..." }, "Shuriken": { "url": "https://api.shuriken.trade/mcp", "headers": { "Authorization": "AgentKey YOUR_AGENT_KEY" } } } } ``` Make sure there's a comma between each server entry. Missing commas are the most common cause of connection failures. Save the file, then **completely quit and reopen Cursor**. The MCP connection won't activate until you restart. Open a new chat in Cursor (the Composer or Agent panel) and try one of these prompts: ``` What tokens were called in my Discord today? ``` ``` What's my SOL balance? ``` If Shuriken is connected, you'll see the agent use Shuriken tools to answer your question. The tool names will show up in the chat (like `get_recent_calls` or `get_balances`). If you see results, you're all set. Your AI agent is now connected to Shuriken. ## Troubleshooting * Make sure you saved the `mcp.json` file * Make sure you fully quit and restarted Cursor (not just closed the window) * Check that there are no syntax errors in your JSON (missing commas, extra commas, mismatched brackets) * Try opening the Command Palette (`Ctrl+Shift+P`) and searching for "MCP" - you should see Shuriken listed * Double-check that your Agent Key is correct (starts with `sk_`) * Make sure you included the `AgentKey ` prefix before the key (with a space) * Check that the key hasn't been revoked on the [Agent Keys dashboard](https://app.shuriken.trade/agents) Common mistakes: * Missing comma between server entries * Trailing comma after the last entry * Using single quotes instead of double quotes * Missing closing brackets Paste your `mcp.json` into [jsonlint.com](https://jsonlint.com) to check for syntax errors. The file might not exist yet. Create a new file called `mcp.json` in the `.cursor` folder inside your home directory and paste the full config block from step 3. ## Multiple Agent Keys You can connect multiple Shuriken Agent Keys to Cursor at the same time - for example, one read-only key for research and one with trading enabled. Give each one a different name: ```json mcp.json theme={null} { "mcpServers": { "shuriken-research": { "url": "https://api.shuriken.trade/mcp", "headers": { "Authorization": "AgentKey sk_YOUR_READ_ONLY_KEY" } }, "shuriken-trading": { "url": "https://api.shuriken.trade/mcp", "headers": { "Authorization": "AgentKey sk_YOUR_TRADING_KEY" } } } } ``` When using multiple keys, each one appears as a separate MCP server in Cursor. The AI will have access to all tools from all connected keys. # Connect to OpenClaw Source: https://docs.shuriken.trade/agent-kit/connect-openclaw Step-by-step guide to connect your Shuriken Agent Key to OpenClaw. This guide gets your OpenClaw agent connected to Shuriken in about 2 minutes. Once set up, your agent can monitor your alpha groups, research tokens, check your portfolio, and execute trades - all through WhatsApp, Telegram, Discord, or the built-in Control UI. **Time required:** About 2 minutes. ## Prerequisites * [OpenClaw](https://openclaw.ai) installed and running (`openclaw gateway status` should show it's active) * A Shuriken Agent Key ([create one here](/agent-kit/create-agent-key) if you haven't already) ## Step-by-step setup If you just created your key, copy it from the setup screen. It starts with `sk_`. If you already closed that screen, you'll need to [create a new key](/agent-kit/create-agent-key) - keys are only shown once. OpenClaw stores its config in a JSON5 file called `openclaw.json`. **Option A: Use the CLI (recommended)** ```bash theme={null} openclaw configure ``` **Option B: Use the Control UI** Open [http://127.0.0.1:18789](http://127.0.0.1:18789) in your browser and go to the **Config** tab. **Option C: Edit the file directly** ``` %USERPROFILE%\.openclaw\openclaw.json ``` ``` ~/.openclaw/openclaw.json ``` Add the following `mcpServers` block to your `openclaw.json`. Replace `YOUR_AGENT_KEY` with the key you copied in step 1. **If you don't have any MCP servers yet**, add this to your config: ```json5 openclaw.json theme={null} { // ...your existing config... mcpServers: { Shuriken: { url: "https://api.shuriken.trade/mcp", headers: { Authorization: "AgentKey YOUR_AGENT_KEY" } } } } ``` **If you already have MCP servers**, add the `shuriken` block inside the existing `mcpServers` object: ```json5 openclaw.json theme={null} { mcpServers: { "your-existing-server": { // ... }, Shuriken: { url: "https://api.shuriken.trade/mcp", headers: { Authorization: "AgentKey YOUR_AGENT_KEY" } } } } ``` OpenClaw uses JSON5 format, so you don't need to quote keys or worry about trailing commas. But standard JSON also works. OpenClaw watches the config file and applies changes automatically - no restart needed in most cases. If the tools don't appear, restart the gateway: ```bash theme={null} openclaw gateway restart ``` Open the Control UI at [http://127.0.0.1:18789](http://127.0.0.1:18789) or message your agent through any connected channel (WhatsApp, Telegram, Discord, etc.) and try: ``` What tokens were called in my Discord today? ``` ``` What's my SOL balance? ``` If you see results from Shuriken, you're all set. Your OpenClaw agent is now connected. ## Troubleshooting OpenClaw strictly validates its config. If the gateway won't start after your changes: ```bash theme={null} openclaw doctor --fix ``` This will diagnose and suggest repairs. Common issues: unknown keys, malformed types, or invalid JSON5 syntax. * Make sure the `mcpServers` block is at the root level of your config (not nested inside another section) * Check that your Agent Key is correct (starts with `sk_`) * Make sure you included the `AgentKey ` prefix before the key (with a space) * Try restarting the gateway: `openclaw gateway restart` * Double-check your Agent Key hasn't been revoked on the [Agent Keys dashboard](https://app.shuriken.trade/agents) * Make sure the key has the permissions needed for the tool you're trying to use (see [Permissions](/agent-kit/permissions)) # Other MCP Clients Source: https://docs.shuriken.trade/agent-kit/connect-other Connect Shuriken to any MCP-compatible AI tool using the generic setup guide. Shuriken's Agent Kit works with any AI tool that supports MCP. If your tool isn't listed in our dedicated guides, you'll be connected in a few minutes using the setup below. ## What you need 1. **An MCP-compatible AI tool** - check your tool's documentation for MCP support 2. **A Shuriken Agent Key** - [create one here](/agent-kit/create-agent-key) if you haven't already ## Connection details Shuriken uses a **remote HTTP MCP server**. This means your AI tool connects to Shuriken over the internet - no local installation, no `npx` commands, no Node.js required. Here are the details you'll need: | Field | Value | | ------------------ | -------------------------------- | | **Server URL** | `https://api.shuriken.trade/mcp` | | **Transport type** | HTTP (Streamable HTTP) | | **Authentication** | Header-based | | **Header name** | `Authorization` | | **Header value** | `AgentKey YOUR_AGENT_KEY` | Replace `YOUR_AGENT_KEY` with your actual key (starts with `sk_`). ## Generic JSON config Most MCP clients use a JSON config file. The exact format varies, but here are the two most common patterns: ### Pattern 1: `url` + `headers` Used by **Cursor**, **Claude Desktop**, and most MCP clients. ```json theme={null} { "mcpServers": { "Shuriken": { "url": "https://api.shuriken.trade/mcp", "headers": { "Authorization": "AgentKey YOUR_AGENT_KEY" } } } } ``` ### Pattern 2: `serverUrl` + `headers` Used by **Windsurf** and some other clients. ```json theme={null} { "mcpServers": { "Shuriken": { "serverUrl": "https://api.shuriken.trade/mcp", "headers": { "Authorization": "AgentKey YOUR_AGENT_KEY" } } } } ``` Not sure which pattern your tool uses? Try Pattern 1 first. If it doesn't work, try Pattern 2. The only difference is `"url"` vs `"serverUrl"`. ## Config file locations For reference, here's where common tools store their MCP config: | Tool | Config file location | | ---------------------------- | ----------------------------------------------------------------- | | **Cursor** | `~/.cursor/mcp.json` | | **Claude Desktop (macOS)** | `~/Library/Application Support/Claude/claude_desktop_config.json` | | **Claude Desktop (Windows)** | `%APPDATA%\Claude\claude_desktop_config.json` | | **Windsurf** | `~/.codeium/windsurf/mcp_config.json` | | **Claude Code** | `.mcp.json` (project root or `~/.claude/.mcp.json` global) | | **OpenClaw** | `~/.openclaw/openclaw.json` (under `mcpServers` key) | ## Verify the connection After adding the config and restarting your tool, try one of these test prompts: ``` What tokens were called in my Discord today? ``` ``` What's my SOL balance? ``` If your agent responds with real data from Shuriken, the connection is working. ## Available tools Once connected, your agent will have access to these tools (depending on your key's [permissions](/agent-kit/permissions)): | Tool | Permission required | What it does | | --------------------- | ------------------- | ------------------------------------------- | | `get_wallets` | Read Wallets | List your wallet addresses | | `get_balances` | Read Balances | View token balances with USD values | | `get_positions` | Read Balances | View all holdings with PnL data | | `get_token_position` | Read Balances | Check a specific token position | | `get_alpha_sources` | Read Alpha | See your connected Discord/Telegram sources | | `get_recent_calls` | Read Alpha | Recent token mentions from your groups | | `get_global_calls` | Read Alpha | Trending KOL mentions from X | | `get_token_mentions` | Read Alpha | Detailed mention history for a token | | `search_tokens` | Read Tokens | Search tokens by name or symbol | | `get_token_info` | Read Tokens | Token metadata and market data | | `get_token_stats` | Read Tokens | Volume, txn counts, price changes | | `plan_trade` | Get Quotes | Get a trade quote (no execution) | | `execute_trade` | Execute Trades | Submit a trade for execution | | `get_task_status` | Execute Trades | Check trade status | | `get_agent_key_usage` | Always available | Check your key's usage and remaining limits | If a tool doesn't appear in your client, your Agent Key might not have the required permission. Check your key's permissions on the [Agent Keys dashboard](https://app.shuriken.trade/agents) or [create a new key](/agent-kit/create-agent-key) with the right access. ## Need help? If your MCP client isn't listed here and you're having trouble connecting, reach out on our [Telegram support](https://t.me/ShurikenSupportBot). # Connect to Windsurf Source: https://docs.shuriken.trade/agent-kit/connect-windsurf Step-by-step guide to connect your Shuriken Agent Key to Windsurf. This guide gets Windsurf connected to Shuriken in about 2 minutes. Once set up, you can ask Cascade to scan alpha, research tokens, check your portfolio, and trade - all from the chat panel. **Time required:** About 2 minutes. ## Prerequisites * [Windsurf](https://windsurf.com) installed on your computer * A Shuriken Agent Key ([create one here](/agent-kit/create-agent-key) if you haven't already) ## Step-by-step setup If you just created your key, copy it from the setup screen. It starts with `sk_`. If you already closed that screen, you'll need to [create a new key](/agent-kit/create-agent-key) - keys are only shown once. Windsurf stores its MCP config in a file called `mcp_config.json`. Windsurf uses a **different config file and format** than Cursor and Claude Desktop. Don't copy configs from those tools directly - the key name for the URL field is different. **Option A: Use the Command Palette (recommended)** 1. Open Windsurf 2. Press `Ctrl+Shift+P` (Windows/Linux) or `Cmd+Shift+P` (macOS) 3. Type **MCP** and select **"Windsurf: Configure MCP Servers"** 4. This opens your `mcp_config.json` file **Option B: Through the Cascade panel** 1. Open the Cascade AI panel 2. Click the **MCPs** icon 3. Click **Configure** **Option C: Open the file manually** ``` %USERPROFILE%\.codeium\windsurf\mcp_config.json ``` Press `Win+R`, paste `%USERPROFILE%\.codeium\windsurf` and hit Enter. Look for `mcp_config.json`. If it doesn't exist, create it. ``` ~/.codeium/windsurf/mcp_config.json ``` ``` ~/.codeium/windsurf/mcp_config.json ``` Paste the following into your `mcp_config.json` file. Replace `YOUR_AGENT_KEY` with the key you copied in step 1. **If the file is empty or doesn't exist**, paste this entire block: ```json mcp_config.json theme={null} { "mcpServers": { "Shuriken": { "serverUrl": "https://api.shuriken.trade/mcp", "headers": { "Authorization": "AgentKey YOUR_AGENT_KEY" } } } } ``` **If you already have other MCP servers**, add the `"Shuriken"` block inside the existing `"mcpServers"` object: ```json mcp_config.json theme={null} { "mcpServers": { "your-existing-server": { "...": "..." }, "Shuriken": { "serverUrl": "https://api.shuriken.trade/mcp", "headers": { "Authorization": "AgentKey YOUR_AGENT_KEY" } } } } ``` **Important:** Windsurf uses `"serverUrl"` (not `"url"`). If you copy config from the Cursor or Claude Desktop guides, make sure to change `"url"` to `"serverUrl"` or the connection will fail silently. Save the file. In Windsurf, you can either: * **Restart Windsurf** completely, or * Click the **refresh button** next to the MCPs section in the Cascade panel Unlike Cursor and Claude Desktop, Windsurf can sometimes pick up config changes without a full restart. But if it doesn't work, restart to be safe. Open a chat in the Cascade panel and try one of these prompts: ``` What tokens were called in my Discord today? ``` ``` What's my SOL balance? ``` If Shuriken is connected, Cascade will use Shuriken tools to answer your question. If you see results, you're all set. Windsurf is now connected to Shuriken. ## Troubleshooting * Make sure you saved the `mcp_config.json` file * Try clicking the refresh button in the Cascade panel * If that doesn't work, fully restart Windsurf * Check that there are no JSON syntax errors * Double-check that your Agent Key is correct (starts with `sk_`) * Make sure you're using `"serverUrl"` (not `"url"`) * Make sure you included the `AgentKey ` prefix before the key (with a space) * Check that the key hasn't been revoked on the [Agent Keys dashboard](https://app.shuriken.trade/agents) Windsurf uses `"serverUrl"` while Cursor and Claude Desktop use `"url"`. Change the field name: ``` "url": "https://..." <-- Cursor / Claude Desktop "serverUrl": "https://..." <-- Windsurf ``` # Create an Agent Key Source: https://docs.shuriken.trade/agent-kit/create-agent-key Pick a preset, name your agent, and you're done in 30 seconds. No code, no server, no monthly fee. An Agent Key connects your AI tool to your Shuriken account. It controls exactly what the AI is allowed to do - from reading token prices to executing trades - and every limit is enforced server-side before the agent ever starts. Pick a preset template and you're done in 30 seconds. Or build a custom key with the exact permissions you need. Think of it like giving someone a key to your house, except you get to choose which rooms they can enter. ## Create a preset key Templates are pre-configured keys designed for common use cases. Pick one, give it a name, and you're done in 30 seconds.