Adops MCP vs Moxie Docs MCP
A side-by-side look at the Adops MCP and Moxie Docs MCP MCP servers: transport, auth, tools, quality signals, and the config to install either one in Claude, Cursor, Windsurf or VS Code.
Verdict: choose Adops MCP for marketing work; choose Moxie Docs MCP for knowledge & memory as a local process. You can also run both side by side in one mcpServers block.
Which MCP server should you choose?
Choose Adops MCP when
- You need dedicated capabilities in the Marketing domain.
- You have the keys it needs:
ADOPS_DATA_DIR. - You want tools like
ad_demo_seed, ad_csv_import, ads_export_recommendations.
Choose Moxie Docs MCP when
- You need dedicated capabilities in the Knowledge & Memory domain.
- You prefer a local stdio subprocess transport.
- Its auth model fits you: API key required.
- You want tools like
moxie.get_ai_context, moxie.get_doc_impact, moxie.get_api_context.
Feature & specification comparison
Rows where the two servers differ are marked.
| Spec | ||
|---|---|---|
| Category | Marketing | Knowledge & Memory |
| Quality signal | 43/100 · Fair | 80/100 · Excellent |
| Install command | Not confirmed yet | Confirmed |
| Transport | — | Local subprocess (stdio) |
| Auth | Not declared | API key required |
| Pricing | Not declared | Freemium |
| Required env vars | ADOPS_DATA_DIR | None listed |
| Verified owner | Community listing | Verified |
| GitHub stars | 0 | 2 |
| Directory activity | 0 views 0 installs 0 upvotes | 36 views 25 installs 4 upvotes |
| Tools | 17 | 12 |
| Full listing | View Adops MCP | View Moxie Docs MCP |
Tools & capabilities
Adops MCP tools 17
ad_demo_seedSeed a realistic cross-platform demo portfolio (8 campaigns, 30 days of metrics) to try AdOps before importing real dataad_csv_importImport a Google Ads or Meta Ads CSV export** — every other tool operates on this dataads_export_recommendationsExport budget_analyze recommendations** as Google Ads Editor CSV, Meta Ads Manager CSV, JSON, or Markdown — one bulk-paste and your ad dashboard reflects the AI's planplatform_connectRegister a data source connection manually (alternative to CSV import, for scripted workflows)campaign_listList and filter campaigns across all imported platformscampaign_createAdd a campaign manually (useful for what-if planning)campaign_updateUpdate campaign settings in local storage (budget, status, bidding, schedule)campaign_pause_resumeBatch pause or resume up to 50 campaignsads_reportGenerate unified cross-platform performance reportbudget_analyzeAnalyze budget allocation, produce scaling/pausing recommendationsbudget_reallocateTransfer budget between campaigns across platformsaudience_insightsDemographic / geographic / device breakdowns- +5 more on the listing page
Moxie Docs MCP tools 12
moxie.get_ai_contextCompact pre-edit briefing: repo status, verified commands, top conventions, open gaps, team notes. Read this first.moxie.get_doc_impactGiven the paths you're about to change (and any you're deleting), returns the conventions, gaps, and existing docs whose evidence overlaps them - and flags net-new/undocumented surfaces.moxie.get_api_contextGiven paths you're about to touch, returns structured context for any API endpoints they map to: method, path, schema, and known consumers/features.moxie.review_changeSelf-review a change before opening the PR; returns a severity-ranked verdict (clean / warnings / must-fix) covering convention breaches, stale docs, undocumented surface, and broken references.moxie.get_conventionsDiscovered coding conventions, grouped by category, with confidence scores, agent guidance, and source-file citations.moxie.search_docsSemantic + keyword search over generated docs, conventions, gaps, and AI context.moxie.get_doc_gapsUnresolved documentation gaps with severity and the paths they concern.moxie.get_documentation_opportunitiesRecommended doc work: missing docs, drift repairs, and PR templates.moxie.get_documentation_patternsHow the repository organizes and maintains its docs (where new docs belong).moxie.list_docsPaginated, section-grouped table of contents of every generated doc.moxie.propose_doc_updateAdd or update a doc as part of your current change; returns the target path + Markdown to write into your branch.moxie.propose_doc_removalRemove a Moxie-tracked doc your change makes obsolete; returns the path to delete in your branch.
Ready-to-paste client configs
Paste either block (or both) into your client config, e.g. claude_desktop_config.json or ~/.cursor/mcp.json. We only show a config when the install command is confirmed.
Adops MCP
No confirmed install command for Adops MCP yet — follow the setup steps linked from its listing page rather than a guessed package name.
Moxie Docs MCP
{
"mcpServers": {
"moxie-docs-mcp": {
"command": "npx",
"args": [
"-y",
"moxie-docs"
]
}
}
}
Frequently asked questions
Adops MCP is categorized under Marketing and uses an install path we have not confirmed yet. Moxie Docs MCP belongs to Knowledge & Memory and uses a local stdio subprocess. Pick Adops MCP for marketing work and Moxie Docs MCP for knowledge & memory.
Copy the mcpServers block from the config section on this page into your client's config (for example claude_desktop_config.json or ~/.cursor/mcp.json), then fully restart the client. Adops MCP has no confirmed install command yet — follow its own setup instructions.
Adops MCP has no declared pricing — check the project's own site. Moxie Docs MCP is listed as freemium — a free tier with paid plans. Auth: api key required. If a server needs environment variables such as API keys, define them under the env key in your client's MCP config.
Yes. MCP clients support multiple servers: add adops-mcp and moxie-docs-mcp as separate keys in the same mcpServers object, and your assistant will call tools from either one.
On AllMCPs, Adops MCP has a quality signal of 43/100 (Fair) with 0 views, 0 installs and 0 GitHub stars. Moxie Docs MCP has 80/100 (Excellent) with 36 views, 25 installs and 2 GitHub stars.