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.

DimensionQuickBooks Online MCP ServerAccess QuickBooks Online data and accounting operations through MCP.BioMCPOne binary. One grammar. Evidence from the biomedical sources you already trust.
FMRS32 / 100 · D75 / 100 · B
Reliability4 / 2010 / 20
Security and permissions7 / 2016 / 20
Maintenance6 / 2018 / 20
Documentation8 / 2017 / 20
Setup experience7 / 2014 / 20
Best for
  • Developers integrating QuickBooks Online data or accounting operations
  • Local integrations using Claude Code or another MCP-compatible client
  • Teams needing sandbox testing or production company access
  • Biomedical researchers
  • Clinicians
  • AI agents that need efficient access to biomedical literature and data analysis
Not for
  • Users who do not use QuickBooks Online
  • Users unable to register an Intuit app and complete OAuth authorization
  • Teams seeking a hosted service without a local process or credential configuration
  • 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 Intuit OAuth 2.0 app credentials
  • Requires access to a QuickBooks Online company and its Realm ID
  • Depending on enabled tools, may require permission to read, create, update, and delete accounting data
  • 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
  • Write, update, and delete tools can change or void accounting records
  • Refresh tokens rotate automatically and are written back to a configuration file
  • Initial production OAuth authorization requires a public HTTPS callback
  • The source contains conflicting license information: Apache-2.0 in repository metadata and MIT in the README
  • 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 clientsClaude CodeClaude Desktop, Claude Code, Codex, Other MCP stdio clients
Tools10011