Machine-readable docs
MCP server
The docs are also served over the Model Context Protocol (MCP) athttps://docs.saucerswap.finance/mcp, giving agents tools to search and read this documentation. No wallet connection or SaucerSwap REST API key is required.
Agent Plugins bundle (experimental)
The SaucerSwap docs bundle packages this endpoint in the Agent Plugins 1.0.0 format. Use it with a client that supports Agent Plugins MCP components and thestreamable-http transport.
1
Download the bundle
Download
plugin.json and mcp.json into the same directory, or copy plugins/saucerswap-docs from the docs repository. No build step is needed.2
Load it in your client
Inspect both files, then use your client’s Agent Plugins installation flow to load the
saucerswap-docs directory and enable its MCP server. Installation and permissions are client-specific; check the compatible clients directory.3
Check the connection
Ask your agent: “Search the SaucerSwap docs for token association requirements and cite the relevant pages.” Confirm that it uses the docs server and returns documentation links.
This is experimental packaging support, not a universal installation command. If your client does not support this format or transport, use direct MCP setup below. Choose one setup method to avoid duplicate connections.
Direct MCP setup
- Claude Code
- Cursor
- VS Code
Rules file for coding agents
Copy this block into your agent rules file (CLAUDE.md, .cursor/rules, AGENTS.md, or equivalent). It encodes the canonical endpoints and the mistakes agents most often make on Hedera.
Agents should treat prices, fees, and rate limits as live data: fetch them from the APIs or contracts at run time rather than hard-coding values from documentation.
Next steps
Developer quickstart
The first three calls, ready to paste into an agent session.
API reference
Every endpoint across both APIs with auth models.
Contract deployments
Verify every ID in the rules file above.
TypeScript bot client
A server-side pattern for V3 order book bots.