Start
Pick the right GitMyABI path for AI-assisted development.
Build with AI
Use this page to choose the right GitMyABI path for AI-assisted development. Pick one or combine several — they are designed to work together.
Choose your path
- Use MCP Server if your IDE or agent supports MCP and should call GitMyABI tools.
- Use Skills if you want to teach an agent the rules for using GitMyABI correctly.
- Use the CLI if you want terminal, CI, or scripted workflows.
- Use generated TypeScript bindings if your app needs typed contract calls.
- Use ABI JSON if you want a lighter integration without generated types.
What agents still need
- Contract address.
- Network or chain ID.
- Deployment metadata or user-provided input.
- Package name and version, or the build detail page output where relevant.
What GitMyABI does not do
- Does not invent contract addresses.
- Does not generate complete frontend applications.
- Does not perform on-chain calls for the consuming app.
Related
- MCP Server
Connect MCP-compatible AI clients (VS Code, Cursor, Kiro, Claude Code, Codex) to GitMyABI.
- Skills
Reusable agent instructions for using GitMyABI correctly.
- Agent task recipes
Copyable, task-specific prompts for AI agents working with GitMyABI.
- CLI overview
What the gma CLI does and when to use it.
- Generated contract bindings
TypeScript packages produced from contract ABIs for typed integration.
- Use generated bindings in a frontend
Consume a published bindings package from a frontend application.