| FMRS | 49 / 100 · D | 75 / 100 · B |
|---|
| Reliability | 7 / 20 | 10 / 20 |
|---|
| Security and permissions | 4 / 20 | 16 / 20 |
|---|
| Maintenance | 9 / 20 | 18 / 20 |
|---|
| Documentation | 16 / 20 | 17 / 20 |
|---|
| Setup experience | 13 / 20 | 14 / 20 |
|---|
| Best for | - IT service desk staff and administrators with access to a ServiceNow instance
- ServiceNow admins/developers who want conversational control over change management, catalog building, or knowledge base work
- Teams wanting to automate agile project tracking (stories/epics/tasks) inside ServiceNow via Claude
| - Biomedical researchers
- Clinicians
- AI agents that need efficient access to biomedical literature and data analysis
|
|---|
| Not for | - Users without a ServiceNow instance or valid credentials
- Scenarios requiring strictly read-only access — the default 'full' tool package grants full create/update/delete permissions
- Enterprises needing official ServiceNow vendor support or SLAs (this is a third-party community project, not an official ServiceNow product)
| - 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 | - ServiceNow instance URL and an account with read/write access to relevant tables (incident, change_request, sc_cat_item, kb_knowledge, sys_user, sys_user_group, sys_script_include, workflow, sys_update_set, etc.)
- Basic auth username/password, OR OAuth client ID/secret, OR an API key (one authentication method)
- Local filesystem access to read the .env file storing credentials
| - 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 default 'full' tool package grants create, update, and even delete access across incidents, changes, catalog, knowledge base, and users/groups — misuse could modify or destroy production data
- Credentials are stored in plaintext in the .env file or Claude Desktop config, creating exposure risk
- Tools like approve_change, reject_change, publish_changeset, and publish_article directly affect live ServiceNow processes and visibility, and should be granted carefully
- The SSE server listens on 0.0.0.0 by default, which could allow unauthorized access without proper network isolation
| - 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 clients | Claude Desktop | Claude Desktop, Claude Code, Codex, Other MCP stdio clients |
|---|
| Tools | 76 | 11 |
|---|