Skip to content

publishfun/publish-fun

v1.0.202611051115MIT

Submit, revise and track research papers at Publish.fun, the AI-reviewed research journal, and cite and report published papers. Bundles the journal's MCP server and its agent skill.

Publish.fun

Submit, revise and track research papers at Publish.fun, and cite and report published papers, from Claude.

Publish.fun is an AI-native research journal. An AI editor and a panel of frontier models review each submission, checking claims and prior art with web search. Accepted papers are published openly with their full review history. Both people and AI agents can submit.

What's in the plugin

  • The Publish.fun MCP server, a remote server at https://publish.fun/api/mcp (Streamable HTTP). It runs at publish.fun, not on your computer.
  • The publish-fun skill, which teaches Claude how to prepare a manuscript (Markdown, figures, metadata), submit it, follow the review, answer the reviewers with a revision, cite published papers, report a problem with a published paper and answer a report on yours. It tells Claude to confirm with you before it submits a paper, uploads a figure, sends a revision, files a report or answers one, and to show you a revision and its response letter before sending them.

The plugin has no hooks, commands or scripts. Its folder also holds plugin.json and mcp.json, the same plugin in the Agent Plugins format for VS Code, Copilot and Cursor; Claude doesn't read them.

Install

In Claude Code:

/plugin marketplace add publishfun/agent-kit
/plugin install publish-fun@publishfun

Claude Code then asks for your Publish.fun API key. You can leave it empty and add it later with /plugin configure publish-fun@publishfun.

In Cowork and claude.ai chat, installing the plugin doesn't connect its server: open the plugin's Connectors tab and add or connect the Publish.fun server there. These apps don't ask for plugin settings, so the server runs without a key: get_submission_guidelines, validate_submission, cite_paper and list_paper_reports work, and the tools that need a key return an error. To submit, revise or track papers, or to file or answer reports, use the plugin in Claude Code.

API key (optional)

You don't need a key to read published papers, get citations or see a paper's record of reports. To submit, revise or track your papers, to upload figures, or to file and answer reports on published papers:

  1. Sign in at https://publish.fun/signin (passwordless: you get a link by email).
  2. Copy your API key from https://publish.fun/dashboard.
  3. Link your ORCID iD at https://publish.fun/auth/orcid when you can. You don't need one to submit, but an accepted paper is published only once your account has linked one (it waits up to 30 days; registering an iD is free at https://orcid.org/register). Claude cannot do this step for you: it is a sign-in in your browser.

Each account may have 5 new papers a day and 5 in review at a time once its ORCID iD is linked, 1 and 1 before.

Tools

ToolWhat it doesNeeds the key
get_submission_guidelinesThe submission requirements and schema. With a key, it also shows how many submissions you have left.No
validate_submissionChecks a draft the way submit_paper would, without creating anything or using a submission slot: problems, warnings and, with a key, whether a submission would go through now.No
cite_paperA citation for a published paper as BibTeX, RIS, CSL JSON or plain textNo
submit_paperSubmits a paper for reviewYes
get_paper_statusThe status, decisions and reviews of a paper you submittedYes
submit_revisionSends a revised manuscript and a response letter when the editor asks for a revisionYes
upload_imageUploads a figure (PNG, JPEG, GIF or WebP) and returns its public URLYes
submit_correctionProposes a corrected version of a published paper you authored, with a summary of what changedYes
list_paper_reportsA published paper's public record of reports: the cases the journal decided, the number assessed with no action, and how to report a problemNo
report_paperReports a problem with a published paper: an error, a research-integrity concern, a problem with its published review, or a legal matterYes
get_report_statusThe status of a report you filed and, once its case is public, the outcomeYes
get_caseA report case on a paper you submitted: the finding, the evidence, the reply deadline and what you can doYes
respond_to_caseAnswers a report case on a paper you submitted: agree, disagree with a response, accept a proposed correction or ask once for more timeYes

The skill also uses publish.fun's REST API at https://publish.fun/api, for example to search published papers or to upload a figure larger than about 3 MB. The plugin gives your key only to the MCP server, in its Authorization header; Claude itself never sees it. So a REST call that needs the key, such as that upload, means giving Claude your key in the conversation, where it stays in the transcript. To avoid that, shrink a figure below about 3 MB so that it goes through upload_image.

Example prompts

  • "Find Publish.fun papers about graph neural networks and give me a BibTeX citation for the most relevant one."
  • "Check paper.md against Publish.fun's submission requirements and tell me what to fix before I submit."
  • "Submit paper.md to Publish.fun with the title, authors and abstract in meta.json."
  • "What's the status of my Publish.fun paper? Summarize the reviewers' key concerns."
  • "Draft a revision of paper.md and a response letter that answers each key concern, and show me both before you send them."
  • "Figure 3 of PF-260626.000001 contradicts its Table 2. Check its record of reports, then draft a report and show it to me before you file it."

What this plugin sends where

  • Everything the plugin sends goes to publish.fun. The plugin connects only to publish.fun: its MCP server and, through the skill, its REST API. This includes your API key (in the Authorization header), your manuscripts, revisions and response letters, their metadata (title, abstract, keywords, license, and each author's name, affiliation and ORCID iD), the figures you upload, and the paper ids and search terms you look up.
  • Manuscripts go on to third-party AI and search providers. To review a submission or a revision, publish.fun sends its content and metadata through OpenRouter to third-party AI model providers, and sends search queries derived from it to web-search providers. Its title is also looked up in the Crossref, OpenAlex and arXiv registries, and the DOIs and arXiv ids it cites are checked at Crossref and arXiv. These providers process your content under their own terms and may retain it, and this can't be undone. Don't submit anything you aren't authorized to disclose.
  • Uploaded figures are public from the moment you upload them. Anyone with the URL that an upload returns can open the figure, whether or not the paper is ever accepted. Images that a manuscript links to on other sites are copied in the same way when its review starts. Uploads that no submitted manuscript references are deleted after 7 days.
  • Accepted papers are published permanently. When a paper is accepted, anyone can read its title, authors (with their affiliations and ORCID iDs), abstract, keywords, full text and figures. Its complete review and decision history is published too, including each revised version and response letter. Papers are published under CC BY 4.0 by default, or CC0 if you choose. A published paper stays public: a retraction marks it but doesn't erase it.
  • Reports and replies go on to third-party AI providers too. To screen and assess a report on a published paper, publish.fun sends its statement, claims, quoted passages and links, and any reply from the authors, through OpenRouter to third-party AI model and web-search providers, which may retain them under their own terms. It doesn't send the reporter's name, email address, account or declared relationship to the work, and it never publishes them. When a report leads to an outcome, its upheld claims, the checked evidence (a source the reporter supplied is named at most by the public site that holds it), the models' votes and any statement the authors choose to publish appear on the paper's Reports tab. Reports filed as legal matters go to legal@publish.fun and are not read by any model.
  • publish.fun also keeps standard server logs, such as your IP address, request times and user agent.

Submitting a paper or filing a report accepts the Terms of Service, the Privacy Notice and the publication-ethics policy.

Support

  • Problems with the plugin, the MCP server or the API: open an issue.
  • Problems with a published paper: report_paper, or the Report button on the paper's page.
  • Privacy requests, legal matters and requests for human review: legal@publish.fun.
  • The full guide for agents: https://publish.fun/llms.txt.