Cory LaNou
MCP Server Goes Pro: New Tiers and Tools for Teams
Overview
Our MCP server has been running in beta since November 2025. The feedback has been solid. Developers are using it daily to audit code, find examples, and get best practice recommendations. Now we're adding what teams have been asking for: shared accounts, new tools, and pricing that makes sense for organizations.
Target Audience
This article is for Go developers and engineering managers who want their teams to have consistent access to Gopher Guides training materials through their AI assistants. If you're evaluating AI-assisted development tools for your organization, this is relevant.
What Changed
Three things: new pricing tiers, two new tools, and team management.
The individual Pro tier stays at $29 per month. Unlimited queries across all tools.
Teams get their own tier at $199 per month for 10 seats. Everyone on the team shares the same quota pool with individual usage tracking. One bill. One admin dashboard. No more passing around API keys or wondering who used how many queries.
Enterprise is $499 per month for 50 seats. Same features as Team, plus SSO integration and priority support.
New Tools
We added two tools based on what developers kept asking for.
explain_idiom does what it sounds like. Ask about "comma ok" or "functional options" or "accept interfaces return structs" and it pulls explanations and code examples from our training materials. Not a generic AI explanation. Actual content from our courses with the context of when and why you'd use each pattern.
Try asking your AI assistant: "Use explain_idiom to explain the comma ok idiom in Go." You'll get working examples and the reasoning behind the pattern.
suggest_refactor analyzes Go code and suggests improvements based on our training best practices. This is especially useful for AI-generated code. You paste in what Copilot or Claude wrote, and suggest_refactor tells you what an experienced Go developer would change.
The tool focuses on idiomatic patterns. It catches things like returning interface types when you should return concrete types. Using interface{} instead of the modern any. Missing error wrapping. Over-engineered abstractions. The stuff that separates "this compiles" from "this is production-ready Go."
Why Team Accounts
The number one feature request was team billing. Engineering managers don't want individual expense reports for every developer. They want one invoice with clear usage data.
Team accounts solve this. You create an organization, invite members by email, and everyone gets access to all tools under one subscription. The admin dashboard shows who's using what, so you can see if the investment is paying off.
Members can have different roles. Owners manage billing and can delete the organization. Admins can invite and remove members. Members just use the tools.
How Pricing Works Now
| Tier | Price | Seats | Queries |
|---|---|---|---|
| Free | $0 | 1 | 500/month |
| Training | $0 | 1 | 2,500/month |
| Pro | $29/month | 1 | Unlimited |
| Team | $199/month | 10 | Shared unlimited |
| Enterprise | $499/month | 50 | Shared unlimited |
Free tier is for trying things out. If you've purchased any Gopher Guides training, you automatically get the Training tier with 5x the queries. Pro is for individual developers who want unlimited access. Team and Enterprise are for organizations.
The math is simple. At $199 for 10 seats, you're paying $19.90 per developer per month. Less than half the individual Pro price. Enterprise at $499 for 50 seats comes out to $9.98 per developer. Volume pricing without having to negotiate contracts.
Getting Started with Teams
If you're the one setting this up, here's the process.
First, sign up for a Pro account if you don't have one. Then upgrade to Team from the billing dashboard. You'll create an organization name and get admin access.
Invite team members by email. They get a link to join. If they already have Gopher Guides accounts, their individual API keys continue working under the team quota. If not, they create accounts during the invite flow.
Each team member can create their own API keys or share a team key. Usage rolls up to the organization level either way.
The Tools We Have Now
With the two new tools, the MCP server now offers five capabilities:
- audit_code: Review Go code against best practices
- best_practices: Get recommendations for specific topics
- get_example: Search training materials for code patterns
- review_pr: Analyze diffs against best practices
- explain_idiom: Get explanations of Go idioms (new)
- suggest_refactor: Get refactoring suggestions (new)
All tools work with Claude, Claude Code, and other MCP-compatible assistants. Configure once, use everywhere.
What's Next
We're working on SSO integration for Enterprise accounts. SAML 2.0 support for Okta, Azure AD, and OneLogin. That should ship in the next few weeks.
After that, we're looking at PR review automation. A GitHub App that runs suggest_refactor on every PR and posts comments. Same expertise, applied automatically at code review time.
The Bottom Line
If you're using the free tier and it's working for you, nothing changes. Keep using it.
If you've been hitting the 500 query limit regularly, Pro at $29 gives you unlimited access.
If you're an engineering manager who wants your whole team to have access, Team at $199 for 10 people saves money compared to buying individual subscriptions.
The goal is the same as when we launched the beta: make expert Go knowledge available at the point of use. We're just making it easier for teams to get that access.
