青提mcp

Created By
aegean-org9 months ago
青提MCP,旨在通过模型上下文协议(Model Context Protocol,MCP)将青提学术数据库与不同 AI 助手衔接,支持自然语言驱动的专业学术查询。
Overview

what is 青提mcp?

青提mcp is a tool designed to connect the 青提 academic database with various AI assistants through the Model Context Protocol (MCP), enabling natural language-driven professional academic queries.

how to use 青提mcp?

To use 青提mcp, install the software compatible with 青提 academic version 2.5.1 or higher, and run the application to start querying academic papers using natural language.

key features of 青提mcp?

  • Paper Search: Supports searching academic papers by title and author with pagination.
  • PDF Text Extraction: Extracts text content from PDF files.
  • Folder Management: Allows retrieval of papers from specific folders.
  • Note Saving: Markdown format note management system.

use cases of 青提mcp?

  1. Conducting literature reviews by searching for relevant academic papers.
  2. Extracting and managing text from research PDFs.
  3. Organizing notes and references for academic writing.

FAQ from 青提mcp?

  • Can 青提mcp connect to any AI assistant?

Yes! 青提mcp is designed to work with various AI assistants through the MCP.

  • What systems are compatible with 青提mcp?

青提mcp is compatible with Linux, macOS, and Windows systems.

  • Is there a user guide available?

Yes! Documentation is available on the project's GitHub page.

Server Config

{
  "mcpServers": {
    "青提mcp": {
      "name": "青提学术",
      "type": "stdio",
      "description": "学术论文管理和研究辅助工具",
      "command": "/你的电脑目录/qt-mcp.exe",
      "args": []
    }
  }
}
Project Info
Created At
9 months ago
Updated At
9 months ago
Author Name
aegean-org
Star
-
Language
-
License
-

Recommend Servers

View All
Hellogrowthcrm

7 hours ago
Voyei

2 days ago
GovQL
@Alex Stout

# govql-mcp-server An MCP (Model Context Protocol) server for [GovQL](https://govql.us) — gives AI clients like Claude Desktop, Claude Code, and Cursor direct access to the US Congressional GraphQL API at [api.govql.us/graphql](https://api.govql.us/graphql) without bespoke HTTP wiring. For the design rationale (why FastMCP-Python, the passthrough+curated philosophy, roadmap through v0.4), see [design.md](https://github.com/govql/govql/blob/main/mcp-server/docs/design.md). ## What you can do with it Ask an agent questions like: - *"How did Vermont's two senators vote on the most recent nomination?"* - *"Which legislators in the 118th Congress switched parties during their service?"* - *"Compare Senator Sanders' voting record to Senator Murkowski's on cloture votes in the most recent Congress."* The agent picks the right tool, writes the GraphQL query against the live schema, and parses the response — no manual API wrangling. ## Install The server runs as a per-client subprocess over stdio. Pick your client: ### Claude Desktop Edit `claude_desktop_config.json` (Settings → Developer → Edit Config): ```json { "mcpServers": { "govql": { "command": "uvx", "args": ["govql-mcp-server"] } } } ``` Restart Claude Desktop. The `govql` tools appear in the tools panel. ### Claude Code Add to `.mcp.json` in your project (or `~/.mcp.json` for global): ```json { "mcpServers": { "govql": { "command": "uvx", "args": ["govql-mcp-server"] } } } ``` ### Cursor Settings → MCP → Add Server. Use the same `command` / `args` as above. ### Other clients Any MCP-compatible client that supports stdio servers will work. The command is `uvx govql-mcp-server` with no required arguments. ## Tools | Tool | Purpose | |---|---| | `execute_graphql` | Run any GraphQL query against the GovQL endpoint. Returns the result plus an `last_ingest` timestamp so the agent can reason about data freshness. | | `list_types` | Returns the names and kinds of every type in the GovQL schema. Optional `kind` filter (`"OBJECT"`, `"INPUT_OBJECT"`, `"ENUM"`, etc.) to narrow further. Start here when you don't know what's queryable. | | `describe_type` | Returns one type's full details — fields, arg signatures, input fields, enum values. Call after `list_types` to learn the shape of a specific type before writing a query. | ## Configuration All env vars are optional — the package is zero-config for end users. | Env var | Default | Purpose | |---|---|---| | `GOVQL_ENDPOINT` | `https://api.govql.us/graphql` | Endpoint to query. Override to point at a local dev stack. | | `GOVQL_TIMEOUT_MS` | `30000` | Per-request HTTP timeout. | | `LOG_LEVEL` | `INFO` | Logging level. Logs go to stderr only (stdout is reserved for the MCP transport). | ## Limits (enforced by the upstream API) - Max query depth: 10 - Max query complexity: ~10 billion points (`first: N` multiplies child cost by N — keep page sizes reasonable on deeply nested queries) - Rate limit: 100 requests / 60 s per source IP A depth or complexity violation surfaces as a GraphQL `errors` entry in the tool response so the agent can adjust and retry. ## Data freshness Every `execute_graphql` response includes a `last_ingest` ISO timestamp. Vote data refreshes hourly; legislator data refreshes daily. ## Status Version 0.1.0 ships three foundational tools: a GraphQL passthrough (`execute_graphql`) and two narrow schema-discovery tools (`list_types`, `describe_type`). Curated higher-level tools (`find_legislator`, `get_voting_record`, `compare_voters`, etc.) are planned for subsequent releases — see [design.md](https://github.com/govql/govql/blob/main/mcp-server/docs/design.md) for the roadmap. ## Links - [GovQL project site](https://govql.us) - [GraphQL API](https://api.govql.us/graphql) - [Source / issues](https://github.com/govql/govql)

14 hours ago