Skip to main content

Documentation Index

Fetch the complete documentation index at: https://docs.shuriken.trade/llms.txt

Use this file to discover all available pages before exploring further.

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 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:
FieldValue
Server URLhttps://api.shuriken.trade/mcp
Transport typeHTTP (Streamable HTTP)
AuthenticationHeader-based
Header nameAuthorization
Header valueAgentKey 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. 
{
  "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. 
{
  "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:
ToolConfig 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):
ToolPermission requiredWhat it does
get_walletsRead WalletsList your wallet addresses
get_balancesRead BalancesView token balances with USD values
get_positionsRead BalancesView all holdings with PnL data
get_token_positionRead BalancesCheck a specific token position
get_alpha_sourcesRead AlphaSee your connected Discord/Telegram sources
get_recent_callsRead AlphaRecent token mentions from your groups
get_global_callsRead AlphaTrending KOL mentions from X
get_token_mentionsRead AlphaDetailed mention history for a token
search_tokensRead TokensSearch tokens by name or symbol
get_token_infoRead TokensToken metadata and market data
get_token_statsRead TokensVolume, txn counts, price changes
plan_tradeGet QuotesGet a trade quote (no execution)
execute_tradeExecute TradesSubmit a trade for execution
get_task_statusExecute TradesCheck trade status
get_agent_key_usageAlways availableCheck 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 or create a new 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.