protocol-skill-use-sky — Ekubo Protocol MCP Resource
protocol-skill-use-sky
is one of 17 resources on the
Ekubo Protocol
MCP server. Connect the server and your client can attach it as context.
by client
How to attach protocol-skill-use-sky from your client
- Claude Code Ekubo Protocol Resource/protocol-skill-use-sky run in your project directory
- Claude Desktop Ekubo Protocol Resource/protocol-skill-use-sky ~/Library/Application Support/Claude/claude_desktop_config.json
- Cursor Ekubo Protocol Resource/protocol-skill-use-sky ~/.cursor/mcp.json
- VS Code Ekubo Protocol Resource/protocol-skill-use-sky .vscode/mcp.json
- Zed Ekubo Protocol Resource/protocol-skill-use-sky ~/.config/zed/settings.json
- Windsurf Ekubo Protocol Resource/protocol-skill-use-sky ~/.codeium/windsurf/mcp_config.json
- Cline Ekubo Protocol Resource/protocol-skill-use-sky ~/Library/Application Support/Code/User/globalStorage/saoudrizwan.claude-dev/settings/cline_mcp_settings.json
- Gemini CLI Ekubo Protocol Resource/protocol-skill-use-sky ~/.gemini/settings.json
- Grok Ekubo Protocol Resource/protocol-skill-use-sky .mcp.json (in your project root)
- ChatGPT Ekubo Protocol Resource/protocol-skill-use-sky Settings → Connectors → Advanced → Developer mode
- Claude.ai Ekubo Protocol Resource/protocol-skill-use-sky Settings → Connectors → Add custom connector
- LangChain Ekubo Protocol Resource/protocol-skill-use-sky pip install langchain-mcp-adapters
Other resources on this server
- ekubo-agent-workflow
- protocol-skill-use-morpho
- protocol-skill-use-morpho-discovery
- protocol-skill-use-sky-discovery
- protocol-skill-use-lido
- protocol-skill-use-lido-discovery
- protocol-skill-use-merkl
- protocol-skill-use-merkl-discovery
- protocol-skill-use-aerodrome
- protocol-skill-use-aerodrome-discovery
- ekubo-lp-position-workflow
- ekubo-quoter-contract
- ekubo-execution-plan
- ekubo-api-openapi
- ekubo-ve33-workflow
- ekubo-evm-contract-directory
Read from the server itself, by connecting to it and calling resources/list on 11 November 2026.
A listing does not declare its resources, so asking is the only way to know them, and this
is what the server actually offers rather than what its listing claims. Names only are
stored; connect the server for each resource's type and contents.