- Give AI agents wallet capabilities with the Swig MCP server
- Make the docs AI-friendly by exposing the docs themselves as an MCP server
Path 1: AI agents that can use Swig
Use this path when you want an agent to create wallets, manage authorities, configure RPC, or execute transactions.- Start with Getting Started with Swig MCP
- Use Swig MCP Server for tool, transport, and deployment details
Path 2: AI apps that need Swig docs as context
Use this path when you want your assistant, IDE, or internal tooling to ingest the Swig docs directly.- Start with Swig Docs MCP Support
- Use the generated MCP server to expose the docs to your AI tooling
Good AI use cases for Swig
- agent-driven wallet creation and account setup
- chat-to-action experiences for users
- role-scoped agent permissions
- multi-agent workflows with limited authorities
- AI copilots that answer product questions using your docs
Where to go next
Wallet Agents
Connect AI agents to Swig wallet operations
MCP Server Reference
Review tools, permissions, and deployment details
Docs MCP
Expose the Swig docs themselves to LLM tooling
Products & SDKs
Understand where AI fits across the platform