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
- An MCP-compatible AI tool - check your tool’s documentation for MCP support
- 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:
| 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 |
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:
Used by Cursor, Claude Desktop, and most MCP clients.
{
"mcpServers": {
"shuriken": {
"url": "https://api.shuriken.trade/mcp",
"headers": {
"Authorization": "AgentKey YOUR_AGENT_KEY"
}
}
}
}
{
"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 |
| 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?
| 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 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. 