All-in-MCP
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| APAPER | No | Enable APaper academic tools module | false |
| GITHUB_REPO_MCP | No | Enable GitHub repository tools module | false |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": true
} |
| prompts | {
"listChanged": false
} |
| resources | {
"subscribe": false,
"listChanged": false
} |
| experimental | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| apaper_search_iacr_papersA | Search academic papers from IACR ePrint Archive Args: query: Search query string (e.g., 'cryptography', 'secret sharing') max_results: Maximum number of papers to return (default: 10) fetch_details: Whether to fetch detailed information for each paper (default: True) year_min: Minimum publication year (revised after) year_max: Maximum publication year (revised before) |
| apaper_download_iacr_paperB | Download PDF of an IACR ePrint paper Args: paper_id: IACR paper ID (e.g., '2009/101') save_path: Directory to save the PDF (default: './downloads') |
| apaper_search_dblp_papersA | Search DBLP computer science bibliography database for papers Args: query: Search query string (supports boolean 'and'/'or' operators) max_results: Maximum number of papers to return (default: 10) year_from: Lower bound for publication year (optional) year_to: Upper bound for publication year (optional) venue_filter: Case-insensitive substring filter for venues (e.g., 'ICLR', 'NeurIPS') include_bibtex: Whether to include BibTeX entries in results (default: False) |
| apaper_search_google_scholar_papersA | Search academic papers from Google Scholar Args: query: Search query string (e.g., 'machine learning', 'neural networks') max_results: Maximum number of papers to return (default: 10) year_low: Minimum publication year (optional) year_high: Maximum publication year (optional) |
| github-repo-mcp_getRepoAllDirectoriesD | – |
| github-repo-mcp_getRepoDirectoriesD | – |
| github-repo-mcp_getRepoFileD | – |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 7 tools
The tools are split into two distinct domains (academic papers and GitHub), but within the GitHub group, three tools lack descriptions and are ambiguously named (e.g., getRepoAllDirectories vs getRepoDirectories). The apaper tools are well-described and distinct.
Tool names follow two different conventions: snake_case with 'apaper_' prefix for academic tools, and camelCase with 'github-repo-mcp_' prefix for GitHub tools. This inconsistency makes it harder for an agent to predict naming patterns.
The total of 7 tools is reasonable, but the server tries to cover two unrelated domains with only a few tools each. The academic part (~4 tools) is appropriately scoped, while the GitHub part (3 tools) feels marginal for a repository toolset.
The academic paper tools cover search and download, which is decent. However, the GitHub tools only provide read operations (get directories and file) with no support for listing repositories, searching code, or any write actions, leaving significant gaps for typical repository interactions.