call-for-papers-mcp
MCP ServerFreeCall for papers MCP
Capabilities5 decomposed
call-for-papers discovery via mcp protocol
Medium confidenceExposes academic conference and journal call-for-papers (CFP) data through the Model Context Protocol, allowing Claude and other MCP-compatible clients to query, filter, and retrieve structured CFP metadata without direct API calls. Implements MCP resource and tool handlers that translate natural language queries into CFP database lookups, returning standardized JSON with submission deadlines, conference dates, and venue details.
Bridges academic CFP discovery into Claude's native tool ecosystem via MCP, eliminating context-switching between research and AI assistant; implements standardized MCP resource handlers for CFP metadata rather than requiring custom API wrappers or manual data entry
Tighter integration with Claude than standalone CFP websites or email alerts, and more discoverable than manual CFP aggregator browsing because queries happen within the assistant's reasoning loop
structured cfp metadata extraction and normalization
Medium confidenceParses and normalizes heterogeneous call-for-papers data from upstream sources into a consistent schema with standardized field mappings (deadline, conference date, venue, research areas, submission requirements). Uses schema validation to ensure all returned CFP records conform to a predictable structure, enabling reliable downstream filtering and ranking by MCP tools.
Implements schema-driven normalization specifically for academic CFP data, handling domain-specific fields like research areas, review types (single/double-blind), and tiered deadlines rather than generic data transformation
More reliable than manual CFP aggregation because schema validation catches incomplete or malformed records; more flexible than rigid database schemas because normalization rules can be updated without code changes
deadline-aware cfp filtering and ranking
Medium confidenceImplements temporal and relevance-based filtering logic that ranks CFPs by submission deadline proximity, conference date, and match to user research interests. Uses date arithmetic and keyword matching against research area tags to surface the most actionable calls first, enabling researchers to prioritize submissions by urgency and fit.
Combines temporal urgency (deadline proximity) with semantic relevance (research area matching) in a single ranking function, surfacing both high-impact opportunities and time-sensitive submissions rather than treating them separately
More actionable than simple chronological sorting because it weights deadline urgency; more relevant than keyword-only search because it factors in temporal context and user research interests
mcp tool and resource handler implementation
Medium confidenceImplements the MCP server specification with tool handlers for querying CFPs and resource handlers for exposing CFP metadata as discoverable resources. Uses MCP's request-response protocol to translate Claude's natural language tool calls into structured CFP queries, with proper error handling and response formatting that conforms to MCP's JSON-RPC message structure.
Implements MCP as a first-class integration pattern rather than a wrapper around existing APIs, meaning CFP discovery is a native capability in Claude's tool ecosystem with proper schema definitions and error handling
More seamless than REST API wrappers because MCP tools are discoverable and callable directly by Claude; more maintainable than custom Claude plugins because MCP is a standardized protocol with tooling support
multi-source cfp aggregation and deduplication
Medium confidenceAggregates call-for-papers data from multiple upstream sources (e.g., WikiCFP, OpenReview, conference websites) and deduplicates records based on conference name, deadline, and venue matching. Uses fuzzy matching or exact field comparison to identify duplicate CFPs across sources, returning a unified view of available calls without redundant entries.
Implements source-aware deduplication that preserves source attribution, allowing users to see which aggregators have the most current information for a given conference rather than hiding source provenance
More comprehensive than single-source CFP tools because it covers multiple aggregators; more reliable than manual aggregation because deduplication is automated and configurable
Capabilities are decomposed by AI analysis. Each maps to specific user intents and improves with match feedback.
Related Artifactssharing capabilities
Artifacts that share capabilities with call-for-papers-mcp, ranked by overlap. Discovered automatically through the match graph.
scholarmcp
MCP server: scholarmcp
paper-search-mcp
MCP server: paper-search-mcp
@seacolour/openalex-mcp-server-tool
MCP server for querying OpenAlex papers
arxiv-mcp-server
A Model Context Protocol server for searching and analyzing arXiv papers
Paper Search
Search and download academic papers from arXiv, PubMed, bioRxiv, medRxiv, Google Scholar, Semantic Scholar, and IACR. Fetch PDFs and extract full text to accelerate literature reviews. Get consistent metadata for easier filtering, citation, and analysis.
arxiv-paper
MCP server: arxiv-paper
Best For
- ✓academic researchers and PhD students managing paper submission pipelines
- ✓AI agents that need to autonomously discover publication venues
- ✓research teams building custom submission workflow tools
- ✓researchers building custom submission tracking systems
- ✓research groups standardizing CFP data across multiple aggregator sources
- ✓AI agents that need predictable, schema-validated data for downstream decision-making
- ✓individual researchers managing multiple paper submissions across venues
- ✓research groups coordinating submissions and allocating effort by deadline
Known Limitations
- ⚠CFP data freshness depends on upstream source updates — no real-time scraping guarantee
- ⚠Query filtering limited to whatever metadata fields the upstream CFP source provides
- ⚠No built-in deduplication across multiple CFP aggregators if multiple sources are indexed
- ⚠Normalization quality depends on upstream source data completeness — missing fields in source data cannot be inferred
- ⚠Custom or non-standard submission requirements may be lost during normalization to a fixed schema
- ⚠No automatic detection of duplicate CFPs across multiple sources
Requirements
Input / Output
UnfragileRank
UnfragileRank is computed from adoption signals, documentation quality, ecosystem connectivity, match graph feedback, and freshness. No artifact can pay for a higher rank.
Repository Details
About
Call for papers MCP
Categories
Alternatives to call-for-papers-mcp
Search the Supabase docs for up-to-date guidance and troubleshoot errors quickly. Manage organizations, projects, databases, and Edge Functions, including migrations, SQL, logs, advisors, keys, and type generation, in one flow. Create and manage development branches to iterate safely, confirm costs
Compare →AI-optimized web search and content extraction via Tavily MCP.
Compare →Scrape websites and extract structured data via Firecrawl MCP.
Compare →Are you the builder of call-for-papers-mcp?
Claim this artifact to get a verified badge, access match analytics, see which intents users search for, and manage your listing.
Get the weekly brief
New tools, rising stars, and what's actually worth your time. No spam.
Data Sources
Looking for something else?
Search →