Build with AI
Where GitMyABI fits into AI-assisted contract integration workflows.
GitMyABI helps AI agents and AI-assisted developers consume smart contract ABIs and the TypeScript bindings generated from them. Agents can use those artifacts when building frontend or backend integrations against deployed contracts.
GitMyABI does not resolve contract addresses, generate full frontend applications, or perform on-chain calls. Contract addresses come from your deployment metadata or user input, and on-chain calls are performed by the consuming application or agent.
Pages in this section
- MCP Server — gives agents tools and actions for calling GitMyABI from MCP-compatible clients (VS Code, Cursor, Kiro, Claude Code, Codex).
- Skills — reusable agent instructions for using GitMyABI correctly: when to use generated bindings vs ABI JSON, what not to invent, where to look.
- Start — a short decision page for picking the right path (MCP, Skills, CLI, or direct artifacts).
- Agent task recipes — copyable, task-specific prompts you can paste into an agent.
Other entry points
- CLI overview — install
gma, sign in, and run local, scripted, or CI workflows. - For AI agents — required inputs, outputs, and a suggested agent flow when reading published artifacts directly.
Background reading
- Generated contract bindings — what the published bindings package contains.
- Package format — the exact artifact layout an agent can read.
- llms.txt — machine-readable agent summary at the site root.
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.
- Start
Pick the right GitMyABI path for AI-assisted development.
- Agent task recipes
Copyable, task-specific prompts for AI agents working with GitMyABI.
- For AI agents
When AI agents should and should not use GitMyABI, with required inputs and expected outputs.
- CLI overview
What the gma CLI does and when to use it.