Moxie Docs MCP vs TikTok Trends MCP
A side-by-side look at the Moxie Docs MCP and TikTok Trends MCP MCP servers: transport, auth, tools, quality signals, and the config to install either one in Claude, Cursor, Windsurf or VS Code.
Verdict: choose Moxie Docs MCP for knowledge & memory work as a local process; choose TikTok Trends MCP for social media over a hosted endpoint. You can also run both side by side in one mcpServers block.
Which MCP server should you choose?
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.
Choose TikTok Trends MCP when
- You need dedicated capabilities in the Social Media domain.
- You prefer a remote HTTP/SSE transport.
- You have the keys it needs:
TRENDSMCP_API_KEY. - You want tools like
get_time_series, get_growth, get_top_trends.
Feature & specification comparison
Rows where the two servers differ are marked.
| Spec | ||
|---|---|---|
| Category | Knowledge & Memory | Social Media |
| Quality signal | 80/100 · Excellent | 49/100 · Fair |
| Install command | Confirmed | Confirmed |
| Transport | Local subprocess (stdio) | Remote HTTP/SSE |
| Auth | API key required | Not declared |
| Pricing | Freemium | Not declared |
| Required env vars | None listed | TRENDSMCP_API_KEY |
| Verified owner | Verified | Community listing |
| GitHub stars | 2 | 1 |
| Directory activity | 36 views 25 installs 4 upvotes | 1 views 0 installs 0 upvotes |
| Tools | 12 | 3 |
| Full listing | View Moxie Docs MCP | View TikTok Trends MCP |
Tools & capabilities
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.
TikTok Trends MCP tools 3
get_time_seriesWeekly (or daily) history for **one** `source` + `keyword`. Same name on MCP and REST (`mode: "get_time_series"`). REST also accepts `get_trends` as an alias.get_growthPoint-to-point percent change. Several windows in one call still count as **one** request for that source + keyword.get_top_trendsLive ranked list. **No keyword.** On MCP, `type` is required and must match the feed name **exactly** (including capitals). On REST, omit `type` only if you intend to pull every feed (billed per feed).
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.
Moxie Docs MCP
{
"mcpServers": {
"moxie-docs-mcp": {
"command": "npx",
"args": [
"-y",
"moxie-docs"
]
}
}
}
TikTok Trends MCP
{
"mcpServers": {
"tiktok-trends-mcp": {
"url": "https://api.trendsmcp.ai/mcp"
}
}
}
Frequently asked questions
Moxie Docs MCP is categorized under Knowledge & Memory and uses a local stdio subprocess. TikTok Trends MCP belongs to Social Media and uses a remote HTTP/SSE transport. Pick Moxie Docs MCP for knowledge & memory work and TikTok Trends MCP for social media.
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.
Moxie Docs MCP is listed as freemium — a free tier with paid plans. Auth: api key required. TikTok Trends MCP has no declared pricing — check the project's own site. 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 moxie-docs-mcp and tiktok-trends-mcp as separate keys in the same mcpServers object, and your assistant will call tools from either one.
On AllMCPs, Moxie Docs MCP has a quality signal of 80/100 (Excellent) with 36 views, 25 installs and 2 GitHub stars. TikTok Trends MCP has 49/100 (Fair) with 1 views, 0 installs and 1 GitHub stars.