Codebase context
Repo-aware search, file discovery, and project context so AI coding tools can check the actual system before suggesting changes.
The Made by AiMe MCP Bundle starts with the two context layers most teams need first: code intelligence and safe database visibility. Add the rest of the stack when your assistant needs docs, git history, API testing, security checks, or workspace context.
Choose the MCP layer that matches the job: repo context, database visibility, git history, API checks, workspace access, or security review support.
Repo-aware search, file discovery, and project context so AI coding tools can check the actual system before suggesting changes.
Schema inspection and database-aware context for assistants that need to reason about tables, fields, and relationships.
Use commit history and working tree context to understand why code changed, not just what the current file says.
Give agents a practical path to validate backend behavior with requests and assertions instead of stopping at vague confidence.
Connect AI work to Gmail, Calendar, Drive, and Sheets when the task moves beyond the repo into operations.
Keep reviews grounded with dependency, secret, and policy checks when speed starts to create risk.
Start narrow with the paid Starter Bundle, or buy individual MCP products where a standalone Gumroad listing is available. Full-stack pricing stays marked as TBD until the full bundle checkout is locked.
| Plan | Monthly price | Included MCP tools | Best fit | Checkout |
|---|---|---|---|---|
| Starter Bundle | $49/mo | Code Intel + DB Suite | AI coding work that needs repo context and database visibility first. | Buy on Gumroad |
| Code Intelligence | $19/mo | Code search, project context, repo-aware AI assistance. | Developers who only need the codebase layer. | View listing |
| Google Workspace MCP | $29/mo | Gmail, Calendar, Drive, and Sheets context. | Operators connecting AI assistants to day-to-day business systems. | View listing |
| DevSecOps MCP | $49/mo | Security, dependency, and policy checks. | Teams that want safer review loops as AI changes more code. | Listing TBD |
| Full MCP Bundle | TBD | Starter plus docs, git, API testing, workspace, and security layers. | Operators past experimentation who want a broader AI operating layer. | Checkout pending |
Starter keeps the first purchase focused: code context plus database context. That is enough to make AI coding assistants materially less blind without asking buyers to adopt the whole stack at once.
Each MCP server is intended to run locally after setup. Use the validated setup instructions provided with the bundle, then restart your MCP client so the tools appear.
Use the checkout link and keep your license details handy.
Paste the server entry into Claude Desktop, Cursor, or Windsurf.
Ask your assistant to list available MCP tools, then run a small repo or schema check.
Short answers for buyers deciding whether this is the right starting point.
No. This route is the dedicated MCP Bundle page, with MCP-specific features, pricing, and checkout links.
The setup flow is intended for Claude Desktop, Cursor, Windsurf, and other MCP-compatible clients once the validated instructions are provided.
Yes. The listed MCP servers are designed to run locally after setup, with any required credentials supplied through environment variables.
The public checkout path that is live today is the Starter Bundle. Full-stack pricing should stay unset until the complete product and checkout path are locked.