Campus Data MCP
Related Servers
Alternatives to Campus Data MCP
No user-submitted related servers found.
Related Servers
- FlicenseNot gradedqualityCmaintenanceEnables AI assistants to access authenticated academic databases via browser sessions, eliminating re-login and password exposure.16-
- AlicenseCqualityCmaintenanceEnables direct access to CSMAR financial databases through Claude Code. Supports 240+ databases including financial statements, stock trading data, and company information with intelligent login management and 11 MCP tools.1114 npm10MIT
- FlicenseNot gradedqualityBmaintenanceProvides CSMAR metadata discovery, query feasibility probing, and local materialization for agent workflows, with caching and rate-limit management.15 PyPI14-
- FlicenseNot gradedqualityAmaintenanceEnables AI agents to search and retrieve academic literature from Web of Science and CNKI, with support for institutional login/SSO. Can be deployed locally on Windows or as a remote Linux server.-
- AlicenseAqualityBmaintenanceEnables AI to search, filter, and process CNKI academic literature through natural language, including structured search, metadata retrieval, full-text reading, citation export, and PDF/CAJ download.96GPL 3.0
- FlicenseAqualityCmaintenanceEnables AI agents to search, read, and cite Chinese academic papers from CNKI using HUST single sign-on, with support for full-text retrieval, BibTeX export, and PDF download.72-
TDQS
Scored across 9 tools
Each tool targets a distinct operation (open/close lifecycle, inspect, login, search, act, scroll, export, downloads) and descriptions explicitly delimit boundaries, e.g. 'Prefer campus_export for the final export click'. Minor overlap remains since campus_act can click controls while campus_scroll and campus_export are specialized clicks, but the docs clarify the intended routing.
All tools share a consistent campus_ prefix with snake_case, giving a predictable set. Slight deviation: most are verb-based (open, inspect, search, act, scroll, export, close) but campus_school_login and campus_downloads are compound noun phrases rather than simple verbs.
Nine tools is well-scoped for a browser-automation/data-export server, with each tool earning its place across lifecycle, inspection, interaction, and export concerns. No obvious redundancy in count.
The surface covers the full session lifecycle (open, inspect, interact, export, download receipts, close) with provenance handling. A possible gap is an explicit text-entry tool for arbitrary catalogue fields, though campus_act may cover typing/filters, and login fields are deliberately manual.