M
MCP Directory CURATED DIRECTORY
911 MCP servers indexed
中文
← Back to directory
COMPARE UP TO 4 SERVERS

Compare MCP servers

Compare scores, permissions, risks, and fit in one decision-focused table.

DimensionGoogle Ads MCP ServerOfficial MCP server for interacting with the Google Ads APIBioMCPOne binary. One grammar. Evidence from the biomedical sources you already trust.
FMRS56 / 100 · C75 / 100 · B
Reliability10 / 2010 / 20
Security and permissions10 / 2016 / 20
Maintenance12 / 2018 / 20
Documentation12 / 2017 / 20
Setup experience12 / 2014 / 20
Best for
  • Marketers
  • Data analysts
  • Developers using AI assistants to manage Google Ads accounts
  • Teams needing automated advertising reporting and analysis
  • Biomedical researchers
  • Clinicians
  • AI agents that need efficient access to biomedical literature and data analysis
Not for
  • Users without a Google Ads account or a valid developer token
  • Users with test-only tokens unable to access production accounts
  • Users requiring modifications to ad budgets or bids (server only provides query and metadata capabilities)
  • Fully offline environments (requires access to Google Ads API)
  • Users needing to write to upstream databases (read-only)
  • Users requiring direct access to closed datasets (e.g., COSMIC is not directly integrated)
  • Users expecting all advanced features without API keys
Required permissions
  • Requires Google Ads API access token, typically via OAuth 2.0
  • Requires a developer token with at least Explorer access
  • Requires Google Ads API enabled in your Google Cloud project
  • Credentials must include the adwords scope
  • Requires internet access to query public biomedical APIs
  • Optional API keys (NCBI, Semantic Scholar, OpenFDA, etc.) to improve rate limits or unlock features
  • Local read/write access for skills, cache, and local study data (e.g., `~/.local/share/biomcp`)
Risks and side effects
  • The server exposes your advertising data to the connected AI agent or LLM
  • API calls may contain sensitive business data
  • If credentials are leaked, unauthorized access could occur
  • Quota and rate limits may cause service interruptions if exceeded
  • Upstream API rate limits may affect performance
  • Some data sources (e.g., KEGG) have licensing terms that restrict non-academic use
  • Features requiring API keys (e.g., OncoKB) may be incomplete without them
  • Local binary installations need regular updates for compatibility
Supported clientsAntigravity CLI, Antigravity Code Assist, Claude Code, Cursor, VS Code with CopilotClaude Desktop, Claude Code, Codex, Other MCP stdio clients
Tools311